No one tests their apps on declared unsupported hardware. How would you identify potential unsupported-but-might-work hardware? It's not worth the cost.
Still, it sounds like someone simply screwed up a compiler setting.
> Still, it sounds like someone simply screwed up a compiler setting.
A screw up would imply they hadn't intended to make the change. It could just have easily been someone trying to improve performance or security by optimizing for supported platforms while not knowing that a lot of unsupported platforms would run the code or be impacted.
If the change doesn't negatively impact stated supported platforms then it wasn't a mistake imo and I don't think they should revert it.
A lot of security issues exist because we continue to support legacy systems that cannot be secured or not without negatively impacting performance. If MS pushed a security patch that gobbled 5-10% performance from decade old systems some people would lose their minds.
Remember how painful the switch from XP was? And from Win7? And now Win10? Some people just refuse to upgrade hardware or software until forced and will bitch piss and moan the entire time.
Is there any chance someone at Microsoft is going to insert a CPU compatibility check before bug-patch-Tuesday force installs these on millions of machines? WindowsReport.com cautions about KB5034203 on older CPUS and I have some older machines currently showing "Optional quality update available 2024-01 Cumulative Update Preview for Windows 10 Version 22H2 for x86-based Systems (KB5034203)" I wouldn't be surprised if those are no longer optional come Tuesday.
tl;dr is that an SSE4.2 instruction was introduced into an optional but commonly used runtime library that ships with the Visual C++ compiler. There's no runtime checking for whether the CPU supports this instruction, so it crashes on older CPUs.
That's it. Was hoping I could ride out staying on Windows 10 until it support was cut off. Enough is enough, I'm wiping Windows tonight and only single booting Ubuntu. Steam library be damned, whatever works on Proton works on Proton. I'm buying a Steam Deck.
If you read the thread, this is a "Microsoft App" issue. The core OS remains functional. You can still play games, surf the Web, and run 3rd party software. Very embarrassing for MS, and it tracks with their ready, fire, aim QA process.
[+] [-] coldcode|2 years ago|reply
Still, it sounds like someone simply screwed up a compiler setting.
[+] [-] cptskippy|2 years ago|reply
A screw up would imply they hadn't intended to make the change. It could just have easily been someone trying to improve performance or security by optimizing for supported platforms while not knowing that a lot of unsupported platforms would run the code or be impacted.
If the change doesn't negatively impact stated supported platforms then it wasn't a mistake imo and I don't think they should revert it.
A lot of security issues exist because we continue to support legacy systems that cannot be secured or not without negatively impacting performance. If MS pushed a security patch that gobbled 5-10% performance from decade old systems some people would lose their minds.
Remember how painful the switch from XP was? And from Win7? And now Win10? Some people just refuse to upgrade hardware or software until forced and will bitch piss and moan the entire time.
[+] [-] BillSims|2 years ago|reply
[+] [-] ack_complete|2 years ago|reply
tl;dr is that an SSE4.2 instruction was introduced into an optional but commonly used runtime library that ships with the Visual C++ compiler. There's no runtime checking for whether the CPU supports this instruction, so it crashes on older CPUs.
[+] [-] AdmiralAsshat|2 years ago|reply
[+] [-] DaveFlater|2 years ago|reply
[+] [-] throwaway918274|2 years ago|reply
That's it. Was hoping I could ride out staying on Windows 10 until it support was cut off. Enough is enough, I'm wiping Windows tonight and only single booting Ubuntu. Steam library be damned, whatever works on Proton works on Proton. I'm buying a Steam Deck.
[+] [-] dimgl|2 years ago|reply
[+] [-] pathartl|2 years ago|reply
[+] [-] unknown|2 years ago|reply
[deleted]
[+] [-] tux3|2 years ago|reply
No runtime detection, no software trapping/emulation. Hard crash for very old hardware.
[+] [-] 1970-01-01|2 years ago|reply
[+] [-] unknown|2 years ago|reply
[deleted]