Live data from Hacker News

New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

bleepingcomputer.com

21–30 of 150 posts

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#21
post #17

I think people might need to put the pitchforks down. It's a preview release, and we have 0 information on the systems in question. You can easily avoid the issue by not participating in the early release program. Finding issues like this is literally why the preview program exists. Should they have caught this with internal testing? Maybe, we don't have enough information to know.

I'm torn on this.

I'm really happy with where MS is going, I think they have been killing it with vs code, chatgpt integration, and I was quite bullish on the surface pros.

But after having owned one for 1 month, they were still a real disaster in the OS area. I "subscribed" to the preview track, and had to reformat my pc twice. It was a fricking disaster. I'm back on osx now, having sold the surface pro.

Hardware and OS is still very much their weakpoint imo. It's like the whole OS is designed by product owners working on macbook pros (which apparantly isn't far from the truth)

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#22
post #7

>"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." "Might"? What a weaselly way to put it. Either Windows will, or it won't. I realise ther…

Linguistically, "might" could also mean "will under certain circumstances". It doesn't definitively imply they don't know.

I myself have used "might" when speaking to customers when the criteria by which we would differentiate is something that isn't necessarily accessible to the audience.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#23
post #7

>"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." "Might"? What a weaselly way to put it. Either Windows will, or it won't. I realise ther…

Linguistically, "might" could also mean "will under certain circumstances". It doesn't definitively imply they don't know. I myself have used "might" when speaking to customers when the criteria by which we would differentiate is something that isn't necessarily accessible to the audience.

Yeah I guess you're right. If that's the case I'd expect the journalist to ask some follow up questions to broadly define in which circumstances it would or wouldn't.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#24
post #17

I think people might need to put the pitchforks down. It's a preview release, and we have 0 information on the systems in question. You can easily avoid the issue by not participating in the early release program. Finding issues like this is literally why the preview program exists. Should they have caught this with internal testing? Maybe, we don't have enough information to know.

[deleted]

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#26
post #2

When Microsoft says "your CPU needs to be this high in order to run Windows 11", perhaps listen to them eh?

It would be trivial for Microsoft to strictly enforce their CPU "requirements" on install. They've chosen not to.

The workaround for that isn't some weird hack, it's an explicit registry value that they made.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#27
post #17

I think people might need to put the pitchforks down. It's a preview release, and we have 0 information on the systems in question. You can easily avoid the issue by not participating in the early release program. Finding issues like this is literally why the preview program exists. Should they have caught this with internal testing? Maybe, we don't have enough information to know.

Indeed no pitchforks, but I can see where some concern has come from. On the release of Windows 11 it was stated that only newer Intel and AMD generations were to be officially supported and while workarounds are built in (literally a registry flag in the installer) to install on even a Pentium 4 [1], they came with a warning from Microsoft that installations in such environments "may not receive updates".

Is it therefore possible that this bug check is being implemented as part of the journey towards actually dropping "support" for these CPUs?

Indeed, it's a preview release, and the Insider program is amazing for getting insight into Windows development and it shouldn't be held up to the same level of journalistic scrutiny as a sanctioned general release, but I can absolutely see why this particular change may have raised some eyebrows.

[1]: https://www.youtube.com/watch?v=ivrlU73VcHw

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#28
post #12

My experience with Windows 11 has been roughly bug free - but it’s not a pleasant place to be. Installing is a nightmare too with the online account requirement. You can circumvent with a shell but still annoying. I’ve been much happier with Debian 12 and KDE for my primary workstation. I can’t think of a compelling to use windows outside of gaming.

What edition of Windows 11 are you using? I hear this a lot about the online account requirement but on my versions (Pro and Enterprise) you just select “Domain Join” and it bypasses the online account requirement. My guess is that a lot of people are using the crappy Home edition.

> My guess is that a lot of people are using the crappy Home edition.

What makes Home crappy? Other than the account thing, obviously. You can't join a domain with it either, but then most people don't have a domain at home. There's some other disabled features, like Hyper-V, but why should people have to pay for a higher tier Windows to use a local account if they don't need the other features?

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#29
post #28
post #12

Earlier quoted context omitted.

What edition of Windows 11 are you using? I hear this a lot about the online account requirement but on my versions (Pro and Enterprise) you just select “Domain Join” and it bypasses the online account requirement. My guess is that a lot of people are using the crappy Home edition.

> My guess is that a lot of people are using the crappy Home edition. What makes Home crappy? Other than the account thing, obviously. You can't join a domain with it either, but then most people don't have a domain at home. There's some other disabled features, like Hyper-V, but why should people have to pay for a higher tier Windows to use a local account if they don't need the other features?

I want to say RDP is limited to higher trims. I don’t think you can Remote Desktop to home. But otherwise I agree with your points.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#30

My experience with Windows 11 has been roughly bug free - but it’s not a pleasant place to be. Installing is a nightmare too with the online account requirement. You can circumvent with a shell but still annoying. I’ve been much happier with Debian 12 and KDE for my primary workstation. I can’t think of a compelling to use windows outside of gaming.

> I can’t think of a compelling to use windows outside of gaming.

- Office

- Adobe

- Ableton

- Visual Studio

Post reply on HN