UCyborg

New theme patcher (download) appeared a month ago. It doesn't modify system files, uses a reliable way to load itself (AppVerifier infrastructure), works with SecureBoot and enables applying themes with custom visual styles with Settings app (checkbox for enabling it to work with SystemSettings.exe). One ceveat - one'll probably have to add fake signature to custom visual style file to be used before Windows will accept it, there's a button for that in the installer. BTW, someone brought up *.deskthemepack files a while back...it doesn't seem possible to pack custom visual style file inside, the system seems to be picky about the path where *.msstyles files are allowed to be loaded from.

Did you turn off Let Windows track app launches to improve Start and search results in Settings app->Privacy->General? It's needed for recent items to appear. It shouldn't have any effect on pinned items though... Either way, I recommend updating to the latest version of StartisBack++.

Some programs' GUI, like LatencyMon, flicker like crazy when the desktop background changes if Automatically pick an accent color from my background option is enabled. Same programs don't exhibit issues on Windows 8 under equal circumstances. Also the taskbar is bugged and the icons randomly blink. I haven't figured out a pattern, but I often notice it when opening some program's save/open file dialog. Using Windows 10 1809 Build 17763.615. Last time I tried 1903 in a VM, nothing was improved in that regard.

Just a minor inconsistency in version numbering between installer and the actual DLL. Either way, it's a full blown fresh new release build compatible with Win10 1903. :)

Aero Glass never defaults to clear transparency unless someone or something changed its settings or in some cases when it doesn't have all necessary information it needs, hence the incompatibility message. Running GUI config utility as admin to change current user's settings is about the same as running web browser as admin every time you want to change its settings. Besides, you're already changing other compositor settings not specific to Aero Glass extension, which are stored in the same location, as regular user either through Control Panel or Settings app.

http://letmegooglethat.com/?q=aero+glass+machine+id

It was likely the highlighted one. I have XP x64 install with same NVIDIA driver version, though a different GPU (GeForce GTX 750 Ti) and this one just makes the browser crash in xul.dll. Also, just having hardware acceleration enabled in Preferences makes the experience beyond awful. Moving the browser to the secondary screen just makes the whole browser stutter; videos stutter, animations stutter, heck, even mouse cursor gets laggy. Same issue with Firefox 52. And to top it off, having browser opened for longer time and invoking other applications utilizing hardware acceleration quickly makes the browser memory usage increase rapidly, then it crashes in d3d9.dll. When whatever causes rapid memory usage occurs, the state becomes corrupted to the point that if I manage to restore its window, the entire window client area is already messed up (just blackness). Having hardware acceleration disabled has some weird effect on font rendering in certain cases, so far, I only noticed it on YouTube's player. Anyway, @404notfound, the pref you're probably looking for is webgl.disable-angle.

Spectre can be exploited on AMD CPUs. Plus, updated binaries distributed with MS updates in general since these vulnerabilities became known are probably re-compiled with new compiler flag /Qspectre. MS guys said they did not notice any performance regressions of concern when building whole Windows with this flag enabled. But you know, they have powerful machines. Maybe mitigating Meltdown alone is more expensive? I haven't dug deep into the whole thing.

Have you updated to Aero Glass 1.5.12 yet? Regarding symbols, see: I guess they're not needed right now with the latest AG version, though they'll likely be needed after some future Windows update.

You got some wrong information if you're wondering where to get/put the symbol file. You run a script that does it for you. Some people have posted them on this forum in the past. I wrote a new one recently, you can find it here. Use the Download ZIP button, you'll find it in the downloaded ZIP file in the only folder that's in there. This particular script requires that Debugging Tools for Windows are installed, it's a part of Windows SDK. You can find the SDK download links here. Pick the installer option and when it asks which components to install, deselect everything Except Debugging Tools for Windows. Now you can run the script and the required symbols should be downloaded. Should fix your issue with incompatibility error and clear transparency (have to log off or terminate Desktop Window Manager with Task Manager for changes to take effect). Because nobody else has the skills/interest. Aero Glass is as reliable as it comes, just needs occasional manual intervention with symbols unless you donate. The thing with symbols is explained here. There's no point running as admin if you're going to choose Current user. Anyway, it won't solve OP's issue since it's not a configuration issue in this case.

It's from Create a Homegroup wizard (https://mspoweruser.com/microsoft-to-kill-homegroup-service-in-windows-10/). Remnants from the HomeGroup feature (if we're talking about version 1803 and above) are still lurking around.

I mostly use 32-bit build of Basilisk, sometimes Waterfox if I encounter something that's not compatible with Basilisk (classic branch, multiprocess option disabled). Have Vivaldi installed in case I want Chromium engine feel. Multi-process browsers are very resource intensive, so I only fire up Vivaldi when I don't intend to open many tabs and/or other applications (have mere 4 GB of RAM to work with).

The credentials popup appears if the host PC has an user account which user name matches the user name of the currently logged in account on the PC accessing the share, but the passwords don't match. This applies even if eg. host PC contains a passwordless account with the user name John and you're accessing the share from another PC while you're logged in with password protected account with the user name of John regardless of whether password protected sharing is enabled or not.

I don't like any of the solutions mentioned either here or at other places. Neither tackle the problem at its core. GameUX invocation code is baked in the Shim Engine (I guess it's in %WinDir%\AppPatch\AcGenral.dll). The system compatibility database (%WinDir%\AppPatch\sysmain.sdb) contains entries for 2165 games; executable name and usually some of its properties and/or accompanying files' names for the purpose of matching the executable file to the game and invoking GameUX). It can be viewed with Compatibility Administrator (32-bit) that comes with Application Compatibility Toolkit 5.6 (for Windows 8+, there's Windows Assessment and Deployment Kit (ADK) for specific version). So the best way is to just tell the Shim Engine to ignore those entries so it doesn't even try invoking GameUX. There are two registry files in the ZIP file below, GameUX_DisableShims.reg disables the entries while the other restores the initial state. If particular game has already been launched before importing GameUX_DisableShims.reg, visiting the game's executable properties, selecting Compatibility tab and clicking OK is required for changes to take effect. https://drive.google.com/open?id=1G45mk_NUtUKGkC2TmREqGx9jhbUlN1RU GameUX shim has been removed from Windows 8 onwards, the issue is Windows 7 specific. Vista has GameUX, but no bug there.

I see, that other problem is not related. Here's a working link to Raymond Chen's blog post about this: https://web.archive.org/web/20190218192651/https://blogs.msdn.microsoft.com/oldnewthing/20120726-00/?p=7043 Probably best to wait until some more updates have already been pushed.

The old parameter still applies to Chrome 75, the new one applies to Chrome 76. I guess only time will tell about the future versions.

Wow! Might not be related, but:

I checked the code, they just changed the command line parameter for disabling custom title bar. The correct parameter in newer Chromium browsers is -disable-windows10-custom-titlebar The decision is made in chrome/browser/win/titlebar_config.cc.

Does FullEventLogView show them the same way?

If anyone's interested, Vivaldi is one of the more interesting Chromium based browsers and has the option to enable native title bar (Use Native Window under Appearance in Tools->Settings). It doesn't put tabs on it in that mode.

I think what you're trying to accomplish relies on the shell's internal logic, the option along with all supporting code would probably have to be added to the dialog that opens when you click Change desktop icons from Personalization control panel. So, since MS won't do it, the only option would be analyzing system DLLs and injecting new code into them, a non-trivial task I imagine.

Thanks, this one works. Still find it odd; GreaseMonkey 3.11 doesn't have compatibility issues with Firefox 51. Waterfox on the other hand runs them all.

There are already bugs with existing addons (at least with Basilisk). Options dialog in GreaseMonkey doesn't work. Also this particular fork's default configuration breaks ColorfulTabs (it expects Firefox version number in the user agent string).

The option is really gone in Chromium 76. They removed conditional check (feature toggle via command line parameter) that used to enable native caption bar. There's no hidden registry setting for it or anything like that.

Moonchild Productions ported the custom caption bar drawing code to their Pale Moon fork as well, see this thread. You'll find my comparison screenshots if you scroll down a bit. They say there would be visual glitches on Windows 10 without custom caption bar drawing, but I don't see anything off with the native caption bar. The caption text is always enforced by Pale Moon, the only other difference I can see is spacing between min/max/close buttons and the caption bar height (I might have reduced default caption height setting in Windows, but I'm not 100% certain). So honestly, I've no idea what they're talking about. Looks like the only option that still exists in the current nightly is setting browser.tabs.drawInTitlebar in about:config to false to enable the native caption bar (and put tabs separately). CSS moz-win-glass property is indeed gone.