New Windows Updates Cause UNSUPPORTED_PROCESSOR Blue Screens (bleepingcomputer.com) 66
Microsoft's August 2023 preview updates for Windows 11 and Windows 10, labeled as KB5029351 and KB5029331 respectively, have led to blue screen errors citing an unsupported processor problem. BleepingComputer reports: "Microsoft has received reports of an issue in which users are receiving an 'UNSUPPORTED_PROCESSOR' error message on a blue screen after installing updates released on August 2," Redmond said. The company also added that the problematic cumulative updates "might automatically uninstall to allow Windows to start up as expected." Microsoft is investigating the newly acknowledged known issue to find out whether it stems from a Microsoft-related cause. The company also urged users encountering these BSOD errors to file a report using the Feedback Hub.
Re:Not a bug (Score:5, Insightful)
Maybe the update feature of the operating system running on the toaster shouldn’t download a new OS with unsupported requirements?
Re:Not a bug (Score:5, Insightful)
Humanity did some pretty cool things with computers in 1996.
Guess what? The same software that did those cool things running on the same computers will still work now.
Re: (Score:2)
So will any reasonable software from today. And when coding stuff that's meant for multi-TB RAM boxen, despite pushback from some colleagues I make a point of leaving stubs that will compile and do something reasonable even on 32-bit. Not because this particular project will ever make sense on small hardware, it's because varying dependencies makes packagers' life suck.
We run the same kernel codebase on embedded and fat hardware, and likewise the userland should be an universal operating system.
My 2019 de
Re: (Score:2)
I have several computers from 1996. Trust me, any software that has been updated within the past few years either will not run on them, or runs so slowly as to be unusable. Their existing software runs just fine, but is too slow on large jobs.
Software development assumes you have nearly the latest processor, and ease of programming is valued over efficiency. If it's fast enough on current hardware, it's fast enough, period. No money is spent on making it more efficient.
Re: (Score:3)
This is a bug despite what the idiot OP says. It's being triggered by a variety of hardware configurations. Some users of MSI motherboards with Intel's 13th gen processors are reporting issues. Seems completely unrelated to the processor itself and more to do with a UEFI problem, at least that is what MSI is investigating right now.
One additional known factor (Score:2)
Re: (Score:2)
Sure it is. It shows Windows to be excessively brittle. Kinda like those obnoxious car alarms that go off is someone looks too hard.
Re: (Score:1)
Sure it is. It shows Windows to be excessively brittle. Kinda like those obnoxious car alarms that go off is someone looks too hard.
Not really. The OS's job is to accept the details it is given from hardware. This is no different from your AMD64 compiled Linux distro throwing a hissy fit if the UEFI incorrect reports the CPU capabilities as lacking x64 support. The OS doesn't analyse hardware, it trusts the information provided to it from the drivers because knowing hardware is literally not its job.
Re: (Score:3)
Actually, no. Linux had to deal with broken ACPI for many years as well as screwed up APICs. It still booted. Worst case, you might have to give it a commandline option to ignore APICs, ignore ACPI, etc.
There is a no-fail way to test for x86_64 capability, jump in to 64 bit code. If it crashes, it wasn't supported and booting wasn't an option. If it doesn't, continue booting.
Re: Not a bug (Score:3, Interesting)
Re:Not a bug (Score:5, Insightful)
Maybe if you losers bought a new PC instead of trying to run Windows on a toaster from 1996, your PC would actually work.
You do understand that is an update for Windows 10 and 11, right? That means PC passed hardware requirements and Windows was installed.
Re: (Score:3)
This update is, afaik, the optional preview update for the newest version of Win11 and the problem is for specific very new hardware.
Re: (Score:3)
Not exactly.
It is possible that the CPU_CHECK was bypassed on win11 install (you can do that with Rufus when creating USB bootable install media).
Microsoft insists that you need at least Gen8 Intel silicon (forget what family for AMD).
Aside from pipeline improvements, nothing new (security featureset wise) was added to Gen8 vs Gen7 (I have a laptop with Gen7 intel silicon), that I am aware of. As such, a lot of devices with Gen7 silicon have been coaxed into running win11, with no real issues. (again, beca
Re: (Score:2)
Which scenario is more likely?
1) That the users in the stories bypassed Windows 10 and 11 hardware requirements (the update is for both) and somehow installed Windows. Then the users tried to install a preview update that finally caught their non-compliant hardware. And then the users reported the errors about the updates to Microsoft when the problem was noncompliant hardware.
or
2) Windows preview updates have bugs in them that erroneously do not recognize the processors.
Re: (Score:2)
Re:Microsoft updates have led to blue screen error (Score:5, Informative)
I really hate to give the impression that Microsoft managed to do something right, but I think it's possible to uninstall the last update from the Recovery Environment (which appears automatically after 3 failed boots).
Re: (Score:1)
Not sure if it's still like this, but historically you could also boot in Safe Mode by holding down a function key. It would load very simple drivers with crappy graphics, but very robust. It's been ages since I had to do that.
Yeah, MS has issues; but a lot of people here like to call them out for stuff that's not real.
Re: (Score:2)
They've also blocked the update from applying via the Windows Update metadata for impacted processors.
Anything that has Windows forced into it ends up impacted. Usually some form of digital disimpaction is required, typically installing something that isn't Windows.
Not quite! (Score:2)
How do you file? (Score:3)
How do you file a bug report if your computer fails to boot and goes to BSOD?
Re:How do you file? (Score:5, Funny)
How do you file a bug report if your computer fails to boot and goes to BSOD?
Via your Windows phone!
Re: (Score:2)
Assuming no other devices⦠reboot into recovery mode (which should happen after ~3 failed boots) and restore to the previous working point. Then block the update from being installed (or hopefully MS pulls it by then).
Re: How do you file? (Score:2)
Because no windows users have a second computer, a smart phone, tablet or work computer/desktop?
As others noted, after three failed boots the recovery system comes up, you roll back the last update, and reboot - and voila, your back running windows! Amazing.
Re: (Score:2)
Simple: Linux computer for stuff that needs to work. Depend on MicroShit? Am I stupid or what?
Update update update update (Score:2)
The IT monkeys at work insist that not reflexively pulling each and every update is work than reflexively pulling each and every update as it becomes available.
Stuff like this seems to be blocked by their perception filters.
Re: (Score:2)
Unless they really are monkeys they should be testing the updates before rolling them out. If your company has cyber insurance it likely requires a number of things from IT. I have regulatory requirements that force my hand, I also have some users that would be happy to install your ransomware.
Re: Update update update update (Score:2)
You suspend updates, then when you have time to test it, install it on one machine and install it - if it BSODs, you simply mark the 'cumulative update' (and any other 'cumulative update' that causes a BSOD.
It's kinda like you have no idea how windows shops operate, but that can't be true, right?
Re: (Score:2)
Download and install them all individually and skip the ones you don't want.
https://catalog.update.microso... [microsoft.com]
Re: (Score:2)
Almost all Windows updates are cumulative now. That means if don't want the June update and skip it, all those same updates are also going to be present in July, then August, then ....
Drawing a box around "almost all", processor microcode and secureboot dbx updates are separate non-cumulative updates.
Re: (Score:2)
The question was how to skip certain updates. In order to skip certain updates one has to turn off Windows Update and stop installing the Cumulative Updates. After that, you could start with Microsoft's monthly release guide, https://msrc.microsoft.com/upd... [microsoft.com]. That will give you the list of updates for the month, if you drill into the details of each one you can find individual links to the update catalog for each individual update. You can then install the individual updates yo want and skip updates you d
Re: (Score:2)
Hopefully they can write in complete sentences and proof-read their communication.
Never install "update previews". (Score:5, Informative)
In Win11, "update previews" are updates that are offered to users before they are all rolled into Patch Tuesday updates. They have been deemed stable enough to be released from the Windows Insider Program and out onto the PCs of every-day users, but might not be 100% stable, as this issue shows.
Unless the update preview specifically addresses an issue you need fixed right away, it's better to let them cook until Patch Tuesday.
Re: (Score:1)
Even after releasing as stable can still be buggy. So, wait even longer! ;)
Re: (Score:2)
I have found that MS still force-feeds me those updates, even if they are "previews."
Re: Never install "update previews". (Score:1)
Manually searching for updates will cause them to appear in the main update window, with the option of installing them. Once they've all been rolled into the patch tuesdays, they are no longer considered previews, and will automatically install.
How nice of them (Score:4, Interesting)
Re: How nice of them (Score:2, Flamebait)
" The company also added that the problematic cumulative updates "might automatically uninstall to allow Windows to start up as expected." " How thoughtful of them.
Got it, the failing patch rolls-back and restarts the system.
This will make me feel much better while I am fighting with the OS and trying to do a clean install including reinstalling all of my huge software suites, and spending days getting my system back in fully working order aka the way things used to be before the update in the meantime I am losing time and money because I can't get any of my normal work done.
I'm confused, if the patch rolls back and reboots the system, why do you have to spend "days" rebuilding/restoring your system?
I know, you see the BSOD, you power down the system, reformat the HD and do a fresh install of the OS and all your apps by hand - you're too busy to actually have a backup of your system.
(I realize your anger is feigned, you don't run Windows and you have no idea how it works, you just wanted to jump on the "dump on Micro
Re: (Score:1)
Re: (Score:2)
You're not adult enough to run an operating system without assistance.
You don't understand the problem, you don't understand the recovery, and you don't understand all those patches your linux system gets every year.
bleeding edge (Score:2)
If you are installing next month's preview updates you are making yourself a beta tester. They call it a preview for a reason. Thank you brave beta testers for saving the rest of from this fate.
One of those updates broke Windows Update (Score:3)
A few weeks ago, one of those updates broke Windows Update for people on the Windows Insider channel.
Re: (Score:2)
A few weeks ago, one of those updates broke Windows Update for people on the Windows Insider channel.
It makes me so happy that Microsoft disbanded their QA team almost 20 years ago now. I think it is important for customers to be the beta testers so we can know in the Real World how the patches work. There is no need to catch errors before you release. Right?
Borked my installation (Score:1)
Re: (Score:2)
Why didn't you roll back to the previous update? Lemme guess-- you disabled system snapshots because of the resources they consume and you want every single nanosecond of CPU time for your FPS?
Re: (Score:1)
Re: (Score:2)
OK-- that officially sucks. Haven't encountered that.
Goog old MicroShit (Score:2)
Always making things so shoddy and cheaply to be just barely usable (or not in this case), because they do not care one bit about quality, security or their customers.
Re: (Score:2, Flamebait)
The update was part of an optional fast-track, it potentially would uninstall itself, and if it didn't, the system recovery tools would almost certainly have you back up and running in under an hour with no re-installs required.
That is, if you had any fscking clue how Windows worked.
Re: (Score:2, Funny)
I see you suffer from Stockholm Syndrome. You should get that treated.
Re: (Score:2)
I see your ability to make assumptions based on personal bias, rather than reality, is unparalleled.
My primary desktop has been Linux for nearly two decades. But that doesn't prevent me from being aware that Windows has made massive strides in system recovery since Windows 7.
Re: (Score:2)
Using Linux does not make you immune against being an idiot where MS is considered. I also fail to see any advances in system recovery. What actually happened is that they now mess it up so routinely ans so often they had no choice to at least implement some minimal, unreliable resilience. To a sane person that is a regression, not an advancement.
Re: (Score:2)
Automatic system snapshots on updates.
System file repair, without requiring a reinstall.
Your hatred has consumed you.
Anyone surprised ???? (Score:2)
Finally a year of the Linux desktop? (Score:2)
A question asked since the beginning of Slashdot ;-)
Since Windows 11, System not as Stable (Score:2)