ORelio

Both approaches are valid, I think the average user does not care about whether the key is there or not - he does not use the registry editor - so I chose to clean keys when they are unused. Your point of view is just as well, though. Oh, so it was a bug. I thought you removed the ability to disable the log, but don't worry, AGTweaker automatically cleans the file on each startup when the "disable log" box is checked so the file does not grow indefinitely ... (I am decidedly a bit obsessed with cleanliness. lol.)

Glad to see that the registry issue is solved, thanks bigmuscle for the hint and pengipete for the feedback! Yes, AGTweaker deletes useless keys, eg if the UseDirect2DRendering key is missing, D2D is used by default so AGTweaker deletes the key rather than setting it to 1. This is designed to leave in the registry only the necessary keys, ie when you want to use values that are not the default ones EDIT: Released 1.1.6, which includes the key virtualization registry fix.

Thanks for the hint, found the article ! http://msdn.microsoft.com/en-us/library/windows/desktop/aa965884%28v=vs.85%29.aspx But I read this in the article : "Registry virtualization is disabled for the following: [...] - Processes that have requestedExecutionLevel specified in their manifests." AGTweaker contains a manifest, with the following statement : <requestedExecutionLevel level="requireAdministrator" uiAccess="false" /> So Registry Virtualization should be disabled according to the article ... Googling for Wow6432Node, found a stackoverflow question that gave an interesting answer : http://stackoverflow.com/questions/11808462/avoid-registry-wow6432node-redirection - http://msdn.microsoft.com/en-us/library/microsoft.win32.registrykey.openbasekey%28v=vs.100%29.aspx So using RegistryKey.OpenBaseKey(RegistryHive.LocalMachine, RegistryView.Registry64); should bypass the Wow6432Node key virtualization Could someone that did have the Wow6432Node issue try this *TEST* build of AGTweaker ? : AGTweaker-1.1.5b.zip

Ok, as I copied & pasted the regitry path from bigmuscle's post, that's probably due to a compatibility feature of Windows itself for 32-bits apps. ... but as the libraries used are 32-bits only I can't just recompile the app as 64-bits, this would not work

Hmm, first of all, have you tried to use the Aero Glass Preview without AGTweaker ? If so, does it work without AGTweaker ? If not, please report the crash & debug log to bigmuscle (not me) If it works without AGTweaker, try to use the old dialog skipping method and disable the HideCMD workaround. If you cannot shutdown your computer that's because the provided password was incorrect, so explorer.exe could not be restarted under your own credentials and has limited capabilities. Note that the Start With Windows setting need administrator rights to be enabled, and the limited explorer cannot launch admin apps (UAC Prompt is not displayed and the app is launched as normal user) To regain full explorer.exe capabilities, please log off and log back to your windows account. ... I Hope that this has helped you to find the issue.

Oh, I saw this error, but as the issue was gone when restarting, I thought it was specific to my computer. I have an idea of how the issue appears: the application tries to open the DWM registry key for reading, and for writing. If the key does not exist, then it will cause an error while trying to open it for reading, but the next statement creates the key and then the error should disappear on next launch... So if I open the key for writing first and reading next, the issue should disappear. I made the change on the source code so it should be solved on next release

OK so I updated the registry keys to fit the new preview in AGTweaker 1.1.5. Thanks for your work bigbuscle

Glad to see that your problem is solved

Ok, so I'm releasing a new version with a box "Use mouse dialog skipping method (recommended)". If you uncheck it, AGTweaker will use the 1.0.2 dialog skipping method which use keypresses instead of mouse.

Did you enable the HideCMD workaround ?

You have to create it in the C:\ drive

Are you trying to explain that the Metro UI does not work when using the last version of AGTweaker ? Or Metro UI automatically re-open itself after loading Aero ?

Try to change the DeviceFeatureLevel registry key to 9100 (DirectX 9.1) You can do this either with regedit or with the GUI (link in my signature)

I'm using the archive you provided and replacing AGTweaker + Readme.txt for each update, currently. If you want to change something in the installer, just provide the updated one and I'll use it for the next release !

There's already a changelog in the first post but why not

Haha, indeed, funny bug : the "Preview Only!!!" dialog autoskip makes the mouse automatically click on that checkbox, which causes the dialog to appear. Fixed in 1.1.3, sorry for the inconvenience.

Here we are, the update for preview 4 is out As the "Debug Log" registry key is ignored by the new preview, I added an autoclean feature to the GUI.

Found this on the MSDN documentation : typedef enum D3D_FEATURE_LEVEL { D3D_FEATURE_LEVEL_9_1 = 0x9100, D3D_FEATURE_LEVEL_9_2 = 0x9200, D3D_FEATURE_LEVEL_9_3 = 0x9300, D3D_FEATURE_LEVEL_10_0 = 0xa000, D3D_FEATURE_LEVEL_10_1 = 0xa100, D3D_FEATURE_LEVEL_11_0 = 0xb000, D3D_FEATURE_LEVEL_11_1 = 0xb100 } D3D_FEATURE_LEVEL; 9100 seems to be the lowest possible value and B100 the max value. I'll add them as an adjustable setting.

Indeed, I re-read the last posts and when setting the DeviceFeatureLevel registry key to 9300 it works for me too. I'll update the GUI, then. While waiting for the update you may want to change the registry key using this regfile : Windows Registry Editor Version 5.00 [HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\DWM] "DeviceFeatureLevel"=dword:00009300 Save it with notepad as a .reg file, then apply it and preview 4 should work. AGTweaker 1.1 is not designed for this preview, however you still can use it with preview 4. ForceBoundingRectangleRedraw and Disabling Debug Logs are the only broken settings.

I read that the v0.4 didn't work properly so I'm waiting for the next working preview to update the GUI