Nothing's certain except death and patches – so that 'final' Windows 10 19H2 build isn't really Having declared 18363.418 the final build for the Windows 10 November 2019 Update, the Windows Insider team has surprised no one at all by issuing patches ahead of release. Last night the team thundered: "We will continue to improve the overall experience of 19H2 on customers' PCs as part of our normal servicing cadence" (its …
I agree. Whack on a Start Menu replacement tool, lock down the spyware and use a tool to wrestle control of the updates and you sort-of have a version of Windows 10 that feels quite like good old Windows 7. Still not perfect, but far better than the "rolling upgrade" quagmire that MS likes to force on everyone.
Anti-cheat software specifically tends to be closely related to DRM (so-called "digital rights management" i.e. "digital rights restriction") in design, in that both have some features of a debugger, tend to try to hook kernel calls, poke around at the system internals, troll around the other processes memory, etc. Some of this is really similar to what spyware or viruses would do. In both cases, this is essentially to make sure the software the DRM or anti-cheat is watching is running as intended and not being poked at by the end user. But, in both cases system changes that would affect zero software that's following normal operating procedures, can easily break software that's trolling around through the system internals, directly hooking calls and trying to directly patch into another piece of software.
As for the "final" non-final version of 19H2? That's weird.
I installed 18363.418 update since I'm in the "insider ring" or whatever you want to call it. After the install, a couple important apps stopped functioning (VMware Workstation fully borked, and Hyper-V isn't able to boot some of my VMs). I found the specific KB to fix it but I can't uninstall it unless I uninstall a whole dependency chain of KBs). Long story short, I rolled back to my last known "good".
You would think that Windows updates would work well and be tested properly on their own hardware, but Surface Book 2 owners got this update very late and then it managed to add yet another service that needs shutting down before the screen can be undocked or moved. Given the time it takes, it is easier to switch off, change screen orientation and then restart than find all the various services that need killed before the red button turns green. Of course then it doesn't detect that it is folded back on itself and you cannot use the keyboard and have to try and re-enable the on-screen keyboard, which doesn't work until you select accessibility at which point it tells you audibly that you've chosen to use that. Does anyone at MS actually use their own equipment?
"Person choosing to run Fedora Rawhide encounters difficulties"
I'm on the Fast Ring as I want to be able to use WSL2, I signed up fully knowing I may encounter problems with beta software, and that's fine with me.
Being on the Fast Ring is a choice, and at the time of enabling this users are warned they may encounter instability and will receive frequent OS upgrades, such as this. I'm not sure where the scandal is here.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2025
