bigmuscle

Your laptop is simply messed up by previously used cracked version, that' all.

No, just AeroHost is not running which means it is not installed correctly.

Yes, it can be fixed by using offical way of installation.

You are using crack, so sorry we cannot help you.

Aero Glass is not disabled on battery anymore - I already changed it. There will be another problem - is there debug.log generated in Aero Glass folder?

Win7 was 7600 => + 400 + 400 = 8400 (which is Windows 8 Release Preview) + 400 + 400 = 9200 (which is Windows 8 RTM) And WinVista was 6000 + 400 + 400 + 400 = 7600 (Win7) According to their trend, they do not care if something is screwed up. Build 10000 will be RTM regardless if it works or not It was mentioned in this forum, but it is my bad that I forgot to put it into the changelog.

And RTM build will be 10000: * Windows 10 - NT version 10.0.10000 * 9200 (Win8) + 400 = 9600 (Win8.1) + 400 = 10000

Sorry to say it, but I don't want any ace's guides here, because they are one big s*it. Every while, there is some user with unsolvable problem which was created just because he applied some of those stupid scripts. Also his guide does not restore Aero Glass effect, maybe it is blurry but it totally bugs your system, because it uses very old preview for Win8.1 which was designed only to make screenshots and it does not implement the effect properly - no occlusion hints, no glass safety zones, everything is rendered twice etc.

It is not official build, it is just a leak which will never be supported by Aero Glass.

Also check your spam folder ;-)

Machine ID is always generated for your HDD where your Windows directory belongs to. However, if used key does not match it, it is checked also against your primary drive.

I don't say it is cause of the problem, but I guess that the AeroRoundClear.msstyles is unsigned theme. Look happens on startup: 1) UxTheme service tries to load this theme, but it fails because its signature does not match. 2) DWM starts up and asks UxTheme for current theme. 3) DWM gets invalid data (NULL or something), because there is no theme in UxTheme. 4) DWM crashes -> if you are lucky, it does not start again; if you are unlucky, it gets restarted and goes back to 2)

Look what theme is specified in registry key HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\ThemeManager DWM loads this theme at first and loading fails, whole DWM crashes.

I tried but without success. Vertical padding for top part works correctly, but width of the frame is not respected at all. Let's wait for the final solution in Win10 RTM - if it is not changed there, I will try to code it myself.

Aero Glass for Win8.1+ v1.3 v1.3.1 New version of Aero Glass for Win8.1 has been released today. This is recommended update for everyone who takes Aero Glass usage seriously. For the complete list of changes see my website (this list is still being updated, because there are many changes and I cannot remember all of them, so it may take some time to recollect them). The symbol patterns are currently hardcoded up to DWM builds 9600.17415, 9841, 9860 and 9879. http://www.glass8.eu

It can be removed from control panel. If Aero Glass is not in the list, it can be because you installed it using some unsupported 3rd script and you must help on your own in such case.

No.

You need to disable auto-colorization at first (e.g. in control panel).

I'm adding information to this topic too - my utility UxThemeSignatureBypass is Windows 10 Build 9879 compatible now. Check my website for download.

Uploaded new version to be compatible with Windows 10. Tested on the build 9879.

It is also important not to mix several versions of dbghelp.dll and symsrv.dll together, because they are incompatible between themselves. It means that if someone changes one of the files to the wrong version then only local symbols will be loaded and symbol server connection will not work (without reporting any error).

Of course, there may always be some bug, but because the code is just took from MSDN, I've been using it for ages and never had any problems with it, I don't think that any problems could be caused by the bug. Connection is the most common cause of all problems - if symbol downloading fails, the file download.error will be created in Symbols folder. The other common problem is user's incorrect setup - many users install Aero Glass into non-writeable location (regardless what's written in the guide) and, of course, symbols downloading will fail in such case. btw, symbols downloading sometimes fails even in Visual Studio.

Provide the verbose debug log then.

If you are not copyright holder for your downloads, you are not allowed to publish them here.

It seems that the problem is same like why my UxThemeSignatureBypass does not work on Win10 - required UxTheme function is just marked to be delayed. Has anyone any experience how to hook the delayed functions correctly? Simply patching Import Address Table does not work, because the first call to delayed function calls DelayLoadHelper which restores the original IAT.