UCyborg

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.

Actually, you should delete the whole Wow6432Node section. I should've clarified, Wow6432Node is for 32-bit DLLS on 64-bit OSes, 32-bit Windows doesn't have Wow6432Node section, just the regular one, so it's sufficient. And since modern apps are either 32 or 64-bit, not both at the same time, there is never a need for 2 separate DLLs, just the one that matches the bitness of installed OS, so the regular entry will do. This is how installer for final version of Aero Glass works, it detects the bitness and installs appropriate ModernFrame.dll and fills in the AppInit_DLLs value under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows

What's the deal with those wait/busy cursors since only those that are set in Mouse Properties under Cursors tab are actually used? .theme files can also explicitly specify them.

You don't need ModernFrame.dll under Wow6432Node, which is for 32-bit DLLs only.

NoelC: Actually, never mind about RoundRectRadius. I think I've been zooming in those corners for too long. It does affect all corners, either my eyes were playing tricks on me or it was a temporary glitch. I'll just leave the value at 11 as you suggest, it looks just fine under usual everyday conditions.

NoelC: I've played with RoundRectRadius a bit and have to ask, does it effect anything else except the top-right corner of the window? I figured value of 15 looks nicest to me, but there are still some redundant pixels in the remaining 3 corners of the window, bottom-left corner being the worst.

Glitches I've seen with the previous build seem to be gone with the current build. I've only noticed some subtle black flash of a part of a shadow casted by a window when I used Peek at desktop function, but can't reproduce it anymore. And when some window opens, its window frame doesn't get the correct appearance instantly, but after a few ms delay, when the animation finishes, this is only with EnableBlurBlend enabled. So 32-bit builds are actually problematic when it comes to Aero Glass? From my past experience with software in general, bugs usually slip in 64-bit versions. There is quite a lot written on the subject. I was going to suggest put the information about holding CTRL on the website, but you've said you implemented safe-guard that stops it from loading when DWM crashes, which is very welcome addition. Also, you forgot to rename Windows TH2 to Windows RS1 on the Support page. Edit: Glitches are rare, they may still pop-up at random times, it's certainly much of an improvement over previous build. And just another remark, Microsoft still hasn't fixed the bug with Windows Explorer; when the background changes and you have auto-colorization of window frames enabled, the scrollbar jumps on top and a renaming operation is cancelled, if you're just renaming the file at the time. Didn't happen in Windows 8.1.

One thing I've been wondering since Windows 10, why does the default setting TextGlowMode result in caption text being shifted to the right? It happens with Aero Glass whether custom theme atlas is used or not. It worked fine with this theme on WIndows 8.1, no text shifting. I have this disabled, NoelC's RoundedBorders.png doesn't add any glow anyway, and the shifting looks stupid IMO. Text caption color set to white, which looks good most of the time, but if background where caption resides is brighter, black glow would certainly be useful to make the text readable, which is how Windows 7 behaved out of the box if I remember correctly. Or was it the other way around, black text and white glow in the background. I'd leave the color at default, but auto setting isn't smart enough to figure out when it's more appropriate to color caption white instead of black.

Regarding those glitches, they don't seem to be connected to graphics drivers, judging by the fact that they also show up when running with Microsoft Basic Display Adapter.

Try this: http://noel.prodigitalsoftware.com/ForumPosts/Win10/14393/RoundedCorners.zip 14393 instead of 10393. And Win10 part.

With auto-colorization of frames according to desktop background color enabled, the colors also come back when the background changes in addition to when UAC dialog pops up. So there's no workaround for this issue ATM? I'd also like to know, where exactly in registry are those settings related to transparency?

I'm getting some minor visual glitches, eg. when browsing files, sometimes black rectangle shows up briefly somewhere above explorer window, 1/4 of a second or less. Black rectangle also shows up 99% of the time when I open hidden icons in the notification area. It goes through the middle of the rectangle that reveals the icons. It disappears as soon as I move the mouse over the rectangle containing the icons. I wanted to try it out on my laptop, which has AMD graphics card instead of NVIDIA, but I have x86 Windows there... I thought about the drivers since NVIDIA's are a bit glitchy these days. Other than that, thank you for the new build. Looking forward to the final version! And thanks for your theme atlas with rounded corners, NoelC! Regarding auto start, it seems to work fine on my end. The scheduled task is setup just how the Aero Glass installer of the previous version set it up. I'm a single user though and don't have password protected account, if this has something to do with it. Edit: It seems those glitches can show in any program, just opened Notepad++ on the second monitor, not sure what I did, but at one point, there was one black rectangle flashing in the lower-left corner of the editor area and another above the start menu icon (on the second monitor). Glitches are not specific to particular monitor. They also don't show up on screenshots.

It's just a code snippet written in C. You'd need the whole thing and Visual Studio to compile it. I haven't dug into theme related specifics so that's all I can say.

While you can run without symbol files and turn off Glow Effect, there are still small graphical glitches. Judging by the errors, I think Microsoft hasn't uploaded new symbols yet. I assume it would work if we had the symbols, but for custom theme atlas files, they or the associated layout files will need to be updated again to work with the new update.

I'm pretty sure I saw a bunch of HTTP_ERROR_NOT_FOUND errors in console window that shows symbol download progress, so maybe the problem is that Microsoft hasn't uploaded new symbol files yet? I also put updated support DLLs in Aero Glass folder (symsrv.dll, dbghelp.dll) from the latest Debugging Tools for Windows, though that didn't make any difference, but it might be a good idea to use the latest versions.

Yup, it's completely unusable now. It makes Windows stop the graphics driver and there are some errors retrieving symbol files. It happened on both my NVIDIA and AMD machine, initially thought there is driver incompatibility with Anniversary Update, so I rolled back to previous build, only to find out 105 GB of minidump files in Aero Glass folder! So I removed Aero Glass and reinstalled Anniversary Update and everything seems fine, had to reinstall some programs though as they didn't survive the migration, still, took less time than reinstalling everything.

Is that the only way ATM? I remember manually downloading symbol files worked just fine on Win 8.1, but here it says "mismatched or not found" for each .pdb file I try to download.

AeroGlass for build 10130 doesn't work well for me on build 10162. Soon after it starts, all effects disappear and I end up with lame white window borders everywhere. Happens almost every time any window gains or loses focus. Actually, if I start it and wait about half minute, then switch to another window, it will happen immediately, but if I start it and immediately and try switching windows, it will happen after few tries. Log also complains about missing symbols and DWM incompatibility. I couldn't obtain updated symbols. Oh well, I'm sure things will resolve when the final build is released.

Good to know it only happens because the application uses that API function in a way it probably shouldn't. Well, if somebody encounters something similar in some other application, at least we know why it happens. I played with Compatibility Administrator a bit and applied WinXPSP3VersionLie shim to Alcohol.exe and guess what, that made menus look different, kinda oldschool and fixed the text. Looks like it checks operating system version then according to that information uses different APIs and/or uses some in a different way to draw stuff. And since Windows XP doesn't have DrawThemeTextEx function, it doesn't attempt to use it.

I can't seem to figure how to make Alt-Tab window look like it looks on Windows 7. Currently using aero7 V2 theme. I've tried SetWindowCompositionAttribute app, specified TaskSwitcherWnd for window class, but it doesn't change anything. The window is always flat blue without any transparency applied, the exact same color I picked when installing Windows on the dialog that also asks for computer name. Any idea how to enable transparency for it?

Yes, I do. I took it from main site and Process Hacker 2 also confirms it's loaded with basically every process (32-bit version for x86 processeses and 64-bit version for x86_64 processes). It might just be something funky with Alcohol 120%, but it's still strange. Oh and, if you change caption color while Alcohol 120% is running, only window title color change, but after restart of the program, the affected text will get that same color too.