SkyySX

To curb the error-message that you have to cancel or what are you referring to? We already know the current build of Glass8 works fine on 1909, there's just this error message you have to click away because the build isn't whitelisted.

Hmm okay, well barring any unforeseen bugs it doesn't seem like BM will have lots to do this time around which is nice! Hopefully DWM and Explorer stop changing radically from this point on.

I'm wondering about one thing, once the final consumer update for Windows 10 1909 will roll out, will AeroGlass still have this error at launch that you click away? I understand this currently happens because 1909 is not written into the "is supported" build-list. Although since Microsoft changed the Windows Update process this time around, if you get the update through Windows Update your Windows will still identify itself as 1903 just with a newer sub-build, in this case 1903 Build 18363. You'll only get the 1909 identifier if you come from an Insider Ring or installed clean from a 1909 ISO. So with this change, will Aero Glass see Windows 10 1903 Build 18363 as "safe"?

Oh nice, share it with us when you're done with it

Okay I get it now and tested it in a VM. Yeah AeroGlass seems to work perfectly on 1909 with the Symbols downloaded but the small nag where I have to press "Cancel" at each boot is enough to annoy me to not install 1909 yet on my main machine at home I'll wait till we get a new build of AeroGlass, seems like all BigMuscle has to do is to add 1909 to the supported list anyway

So wait are there problems on 1909 for some users now or not? Whenever a smaller Windows update came through my symbols always auto-updated and I never got an error message.

Well now I'm a bit anxious since it was reported that it should work after the 1909 update with the correct symbols right

I see, would I also have to do that if symbols always downloaded automatically in the past?

Nice! Did the symbols update automatically with a License Key? Any issues or annoyances like having to click "Retry" each boot?

Since 1909 is now out and more of a Service Pack type of patch, will we still need a new Aero Glass version for it?

Oh you meant the many Desktop icons! Well they are all neatly organized so it doesn't look bad in my opinion Though have you looked into Stardock Fences? It costs 12€ but has many great features for Desktop icons: https://www.stardock.com/products/fences/ You can also set it to hide Desktop icons until you click on the desktop, then they appear. I've been using it for a few years and like it, what you didn't see, my desktop is full of icons too, they are just hidden

Great that you could fix it! And why shouldn't I like your Desktop? I think it looks great! Mine isn't all that different

Good luck fixing the issue! And thank you very much for the font! Now I'm quite curious how your desktop overall looks

I would assume that AeroGlass failed to download the new symbol files for the update, this script here might help you: Also may I ask what font you use? I quite like the look of it!

Just place it in the AeroGlass folder and reboot.

Oh thank you! We all here should do something like a MSFN Windows 10 Modding Wiki so all this info gets in one place!

Hmm I can't check right now but if I had to guess maybe in C:\Windows\System32\Shell32.dll, look there for a start!

Thanks, yeah the pnidui.dll threw me off, I was searching for them in the .mun files

Hey sorry to bug you but I upgraded to 1903 now and could you maybe tell me which files inside SystemResources I have to edit for the TrayIcons? Thanks in advance!

Sadly I couldn't enjoy this one yet as my Windows User Account self-destructed when I updated from 1809 to 1903 yesterday, I had a recovery-image of 1809 so for now I'm back on that

Thank you very much @bigmuscle, much appreciated!

Sorry I just double-checked and yeah the correct location in the registry is indeed SideBySide, I copied the key from a tutorial yesterday that had it wrong. Although I'm stumped why it doesn't seem to work for others. You could also try to modify the manifest inside Firefox.exe directly with ResourceHacker, I can provide instructions for that too if people are interested.

That's odd, I uploaded my manifest file just to make sure so try it with that one maybe. Also did you reboot after making the change in the registry? firefox.exe.manifest

Oh sure no problem! 1: - Go to the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion - Make a new DWORD value there called PreferExternalManifest and give it the decimal value 1 - Reboot your system 2: - Go to your Firefox folder and create a text file with the name firefox.exe.manifest - Add the following content into the file and save: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> <assemblyIdentity version="1.0.0.0" processorArchitecture="*" name="Firefox" type="win32" /> <description>Firefox</description> <dependency> <dependentAssembly> <assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="*" publicKeyToken="6595b64144ccf1df" language="*" /> </dependentAssembly> </dependency> <ms_asmv3:trustInfo xmlns:ms_asmv3="urn:schemas-microsoft-com:asm.v3"> <ms_asmv3:security> <ms_asmv3:requestedPrivileges> <ms_asmv3:requestedExecutionLevel level="asInvoker" uiAccess="false" /> </ms_asmv3:requestedPrivileges> </ms_asmv3:security> </ms_asmv3:trustInfo> <ms_asmv3:application xmlns:ms_asmv3="urn:schemas-microsoft-com:asm.v3"> <ms_asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings"> <dpiAware>True/PM</dpiAware> <dpiAwareness xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">PerMonitorV2,PerMonitor</dpiAwareness> </ms_asmv3:windowsSettings> </ms_asmv3:application> <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1"> <application> <supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/> <supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}"/> <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/> </application> </compatibility> </assembly> - Start Firefox normally and you should have glass on the tool-bar and fixed navigation buttons All this basically makes Firefox "forget" that it has a Windows 10 UI and makes it load the Windows 7 UI instead.

I just wanted to say that Firefox 68 still works fine with Glass8 and even with Hardware Acceleration and WebRenderer enabled by using the manifest trick instead of UserChrome.css code.