UCyborg

The link on Aero Glass download page works. The .exe inside is dated 2.10.2016. http://www.glass8.eu/files/AeroGlassGUI.7z

Nothing wrong with Aero Glass. I figured it out, it's faulty RAM.

I thought about that myself. Could it be related to graphics drivers? I have AMD Radeon R2, latest drivers. It's strange, because without Aero Glass, it runs fine. Edit: There weren't any problems with previous Windows build, and that laptop is setup almost like my desktop PC with 64-bit Windows, except there is different hardware and I run less software on it than on the desktop. It's good to know that the problem isn't in Aero Glass. Guess I'll have to live without it on that laptop unless I figure something out someday.

Welp, 32-bit now crashed on resume from sleep (black screen, empty minidump), had to reset the system. Worst thing about it, it can take varying amount of time before it happens and it's impossible to give steps on how to reproduce. Really curious what's the deal with getting 32-bit to work right. Last time I checked, 64-bit portability problems were a thing, not the other way around.

@daveo76 Your settings seem correct. Can you also check HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\DWM for CustomThemeAtlas, just in case it got there? Then log off and back on. If you still get Failed to load custom theme atlas file error, then I really don't know what else to suggest. I get this error if I specify custom theme atlas file that doesn't exists, it shouldn't appear unless Aero Glass is told to load it. @bigmuscle DWM along with Aero Glass Build #692 is running stable for 3 hours now on my 32-bit installation, no issues so far. Maybe it was a temporary glitch back then, plus there was a windows update today. Also, not sure if this has anything to do with it, but I usually minimize then hide the debug window with Process Hacker, at the time those crashes occurred, I just had it minimized. Will let you know If I encounter any more issues.

Now I removed the ColorizationColorCaption, but can't reproduce crash from before, text is still corrupted and theme atlas setting works. It's indeed a combination of custom theme atlas along with text glow. If you're unlucky, you get a crash instead of just corrupted text in ribbon windows. And another related bug, having custom theme loaded doesn't try to apply any glow to ribbon windows.

Interesting, CustomThemeAtlas is effective now and I got corrupted text but Explorer doesn't crash. The only thing I changed from previous test, I added ColorizationColorCaption setting in registry.

@daveo76 I've managed to reproduce your crash with Explorer, I think it happens when you have CustomThemeAtlas set under DWM settings key in registry (HKEY_CURRENT_USER\Software\Microsoft\Windows\DWM). This setting doesn't seem to be effective with UxThemeSignatureBypass64.dll loaded, just crashes Explorer. But when it's not set, loading custom themes work and Explorer doesn't crash. CustomThemeAtlas setting is meant to be used when you don't want to replace whole theme. So the way it is now, if you want whole custom themes, that setting must be deleted or if you want just custom theme atlases, the DLLs shouldn't be injected. Either way, a slight inconvenience since you can't make a switch without a reboot. @NoelC Saw screenshot of that bug before, I'll see if I can try to reproduce it as I haven't seen it on my machine.

If UxStyle works for you, then you probably shouldn't inject UxThemeSignatureBypass DLLs, as they accomplish the same thing, they just do it differently, you either choose UxStyle or UxThemeSignatureBypass DLLs. AFAIK UxThemesignatureBypass DLLs also make title captions for ribbon windows the same color as captions of normal windows, if you set the color in registry. From what I can see, if you'd like to use those DLLs instead of UxStyle, you shouldn't have put path to UxThemeSignatureBypass32.dll in the same AppInit_DLLs as the 64-bit version, but in the 32-bit part of registry, I have it like this: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows] "AppInit_DLLs"="C:\\AeroGlass\\UxThemeSignatureBypass64.dll C:\\AeroGlass\\ModernFrame-x64-Debug.dll" "LoadAppInit_DLLs"=dword:00000001 "RequireSignedAppInit_DLLs"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Windows] "AppInit_DLLs"="C:\\AeroGlass\\UxThemeSignatureBypass32.dll" "LoadAppInit_DLLs"=dword:00000001 "RequireSignedAppInit_DLLs"=dword:00000000 You can save this as .reg file and import it. Also, the latest Anniversary Update compatible ModernFrame.dll is called ModernFrame-x64-Debug.dll. If you renamed it yourself to ModernFrame.dll, then rename it in the above script. I'd leave its name as it is though so it's always obvious that I don't run the final version.

It should work. Do you also have UxThemeSignatureBypass32.dll installed like 64-bit version? I never tried running without it, but it's a good idea that you install it as well. The only other idea I have, it may conflict with something else you have installed you're not aware of. I have Aero Glass, Classic Shell, OldNewExplorer and both DLLs and there aren't any problems. I'd also run command sfc /scannow from Command Prompt, just in case, be sure to run it as Administrator. It checks whether you have any corrupted system files and replaces them with good ones, though this may not be it, given that things run well for you without that DLL.

I caught another kind of crash occuring in dwmcore.dll when peeking at the desktop, the previous one occured in d3d11.dll: https://drive.google.com/open?id=0B2DPRdP0LBDGOWFpN1Z3S094U3M And here's my debug.log, just in case. So this one and the ones in my previous post are all the dumps I have, I hope they help with debugging.

Here's 6 latest minidumps I could gather: https://drive.google.com/open?id=0B2DPRdP0LBDGXzhLSXNJUGJsYk0 There's another oddity for which I'm not sure those dumps would reveal anything, it happens if I just let PC idle at the desktop, screen just stops refreshing after a while, only mouse cursor is fine. Then after I shut it down with the power button and back on, I see empty mini dump file. Maybe it's the same bug that happened when the PC was locked, as DWM surely restarted then. Edit: If I wait for a while, the screen turns off (I have set it to turn off after 10 min of inactivity), then I can wake it up with mouse, but then even the cursor is gone, just blackness. And now it doesn't even respond to shut down button.

Using it now and it's awesome indeed. I actually tried to use it back when November Update was released, couldn't get it to work properly, for some reason I didn't think of just using good old UxThemeSignatureBypass DLLs (even though I've been using them back on Win8.1 with similar Win7 theme) instead of that damned UxStyle Patcher/UxThemePacher that managed to stop my graphics driver at each boot among other things. BTW one can take Win7 cursors and sounds from the theme I linked if desired, though some manual tweaks to .theme files are required since sagorpirbd's themes don't include them. Some more feedback regarding 32-bit #692 build, another more common crashpoint seems to be ntdll.dll, sometimes even if PC is locked and idling.

Actually, sometimes it still crashes in d3d11.dll, but I'm unable to determine the condition that is causing it.

Build #692 32-bit works great! UxThemeSignatureBypass32.dll also works as it should.

Doesn't work, clicking Ignore would produce black screen 99% times, requiring hard reset. And even in 1% of time when it seems to work, computer would hang with another black screen when shutting it down, probably nothing strange given the nature of the error. Edit: If I remove UxThemeSignatureBypass32.dll from AppInit_DLLs, I can click Ignore and it doesn't hang/crash anymore. I found this in Event Viewer: Faulting application name: dwm.exe, version: 10.0.14393.0, time stamp: 0x57899025 Faulting module name: UxThemeSignatureBypass32.dll, version: 1.1.0.0, time stamp: 0x54fc8726 Exception code: 0xc0000005 Fault offset: 0x00005ece Faulting process id: 0x3f4 Faulting application start time: 0x01d2171319b1d076 Faulting application path: C:\WINDOWS\system32\dwm.exe Faulting module path: C:\AeroGlass\UxThemeSignatureBypass32.dll Report Id: 87cf6c68-0a6b-48b5-9551-16d906d0e434 Faulting package full name: Faulting package-relative application ID: Edit2: After few minutes of use, I'm staring at the black screen again. Faulting application name: dwm.exe, version: 10.0.14393.0, time stamp: 0x57899025 Faulting module name: d3d11.dll, version: 10.0.14393.0, time stamp: 0x57898e09 Exception code: 0xc0000005 Fault offset: 0x0002609a Faulting process id: 0x3f0 Faulting application start time: 0x01d21716d93e059f Faulting application path: C:\WINDOWS\system32\dwm.exe Faulting module path: C:\WINDOWS\system32\d3d11.dll Report Id: 30b4cf17-5cf3-4aa5-b718-44c217a0fd3d Faulting package full name: This is the most recent crash, it occurred when I used Aero Peek. I also have another crash log when I had UxThemeSignatureBypass32.dll loaded: Faulting application name: dwm.exe, version: 10.0.14393.0, time stamp: 0x57899025 Faulting module name: DWMGlass.dll, version: 1.5.0.675, time stamp: 0x57e55c92 Exception code: 0x80000003 Fault offset: 0x000e7c7c Faulting process id: 0x1244 Faulting application start time: 0x01d216dea8826712 Faulting application path: C:\WINDOWS\System32\dwm.exe Faulting module path: C:\AeroGlass\DWMGlass.dll Report Id: 9237a6d8-e4f6-47d6-b478-a39103f442c8 Faulting package full name: Faulting package-relative application ID:

I'm aware of reputation the power-saving features in Windows have, fortunately, there haven't been any significant problems related to them on my configuration. I just got used to those 15 seconds from boot logo to login screen. if I remember correctly, that's approximately how long Windows 7 took to cold-start few years back on this machine. Things have gotten a bit slower in that regard with later Windows versions. Either way, I doubt this glitch is related directly to power-saving features. There must be some strange condition occurring on my PC (it's very rare) that sometimes make Aero Glass unable to initialize properly when DWM starts. Note that logging in via Remote Desktop starts a new DWM instance. Strangely, the log file isn't even touched, so I assume if even those messages that regularly show up in the log don't appear, I doubt anything would appear with verbose logging enabled either.

Did it ever happen to anyone that when turning on PC (after default hybrid shutdown), Aero Glass wouldn't work properly? DWMGlass.dll is injected, window frames have glass effect, but custom theme atlas isn't loaded and neither there are new entries in debug.log for the current session. I logged off and back in and it works now. Also had it happen once when logging in via Remote Desktop, reconnecting fixed it.

The only very rare, basically impossible to reliably reproduce glitch I've noticed with these builds (including #668), sometimes closing a window would leave portions of it on the screen until some action made the whole thing refresh. This is all without GlassSafetyZoneMode setting in registry, if this even has anything to do with it due to the said glitch not showing up regularly.

#668 runs very well on my machine, haven't caught any visual glitch yet, RAM usage hovers around 80-90 MB, CPU usage seems normal, around 0.3% maximum when not doing anything, jumps to about 3% when moving mouse around. I have an aging AMD Phenom II x4 920, 4 GB RAM and NVIDIA GeForce GTX 750 Ti (driver version 368.81). I also haven't been able to reproduce those visual glitches from last time when working in Word 2016 (modal dialog border going fully transparent).

Current user: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\DWM System-wide: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\DWM Settings under HKEY_CURRENT_USER override system-wide settings. About disabling Aero Glass, open Task Scheduler, find the Aero Glass task, end it then disable it, afterward, you can just close the dwm.exe console window. For non-debug builds, the process is the same, except you have to end Desktop Window Manager with Task Manager since you don't have the console window.

I noticed that logging in via Remote Desktop is another way to spawn ModernFrame's debug window that belongs to Explorer. Another window belonging to ApplicationFrameHost.exe is usually spawned when actually launching Modern apps. Or it spawns by itself eventually as already pointed out few posts above. The appearance of debug window belonging to ApplicationFrameHost.exe seems to be expected behavior since that process supposedly hosts those frames. But what's Explorer's role in this? It is considered a Modern app by Process Hacker. Maybe some sort of bridge so everything is integrated together, Explorer being part of the shell on Windows?

Actually, it might depend on other opened applications at the time. Can't tell what exactly triggers it.

The bug with fully transparent borders, it shows up for me frequently, pretty much all the time, when opening modal dialogs in Micrososft Word (2016). It disappears as soon as something visually changes in it.

Here came a new Windows update KB3176938, and once again, Aero Glass is confused about new dwmcore.dll, and fails to download symbols. Cancelling DWM incompatibility error dialog and letting it work with current knowledge seems to be working at first glance.