Slashdot Mirror
Anti-Cheat Software Causing Big Problems For Windows 10 Previews (arstechnica.com)
An anonymous reader quotes a report from Ars Technica: The Windows 10 Insider Preview Slow Ring -- the beta track that's meant to receive only those builds that are free from any known serious problems -- hasn't received an update for months. While the fast ring is currently testing previews of the April 2019 release, codenamed 19H1, and the even-faster skip-ahead ring is testing previews not of the October 2019 release, 19H2, but of the April 2020 release, 20H1, the Slow Ring is yet to receive a single 19H1 build. This has prompted some concern among insiders that perhaps the ring has been forgotten about, and it has even caused a few complaints from companies that are using the Windows Insider for Business program to validate new Windows releases before their launch. Without Slow Ring builds to test, there's nothing to validate, meaning that they'll have to delay deployment of 19H1 once it ships.
Microsoft's Dona Sarkar, chief of the Windows Insider program, explained yesterday what the problem is, and in many ways it's a throwback to Windows' past, before the days of DEP and ASLR and PatchGuard and all the other measures Microsoft has implemented to harden Windows against malicious software: the build is crashing when some unspecified common anti-cheat software is used. Sarkar's tweet says that the software causes a GSOD, for Green Screen of Death; the traditional and disappointingly familiar Blue Screen of Death, denoting that Windows has suffered a fatal error, is colored green for preview releases so they can be distinguished at a glance from crashes of stable builds. Fast ring builds have the same GSOD issue, and indeed, it has been listed on their known issues list for many months. Sarkar says that the fix must come from the third-party company that developed the anti-cheat software. In an update, Ars Technica's Peter Bright says Microsoft has pushed a build to the Slow Ring, number 18342.8, but the GSOD issue remains. "To avoid crashing machines, the build won't be offered to any system that has the offending anti-cheat software installed," Bright writes. "It's not clear why this approach could not have been used months ago."
Microsoft's Dona Sarkar, chief of the Windows Insider program, explained yesterday what the problem is, and in many ways it's a throwback to Windows' past, before the days of DEP and ASLR and PatchGuard and all the other measures Microsoft has implemented to harden Windows against malicious software: the build is crashing when some unspecified common anti-cheat software is used. Sarkar's tweet says that the software causes a GSOD, for Green Screen of Death; the traditional and disappointingly familiar Blue Screen of Death, denoting that Windows has suffered a fatal error, is colored green for preview releases so they can be distinguished at a glance from crashes of stable builds. Fast ring builds have the same GSOD issue, and indeed, it has been listed on their known issues list for many months. Sarkar says that the fix must come from the third-party company that developed the anti-cheat software. In an update, Ars Technica's Peter Bright says Microsoft has pushed a build to the Slow Ring, number 18342.8, but the GSOD issue remains. "To avoid crashing machines, the build won't be offered to any system that has the offending anti-cheat software installed," Bright writes. "It's not clear why this approach could not have been used months ago."
Why does what amounts to spyware get preferential treatment?
The solution to this is simple: games shouldn't be loading their own kernel drivers.
"Screw Sun, cross-platform will never work. Let's move on and steal the Java language." - Visual J++ Product Manager
Three sides of the same coin.
I'd prefer an ultra Ultra slow and very stable tested train of updates.
You know maybe even give it a name, a more simplified ui, call it something like windows 7 or something like that.