Live data from Hacker News

New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

bleepingcomputer.com

11–20 of 150 posts

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#11
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.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#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.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#13
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.

Pro

https://www.tomshardware.com/how-to/install-windows-11-witho...

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#14

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.

And thanks to Steam deck/proton, that gap is also decreasing significantly.

Windows definitely has regressed in terms of user experience and updates/upgrades and online integration are two big pain points that really make me miss Linux (Ubuntu or Arch+lxde, if you want names) every time I'm there.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#15
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.

I'm confused by that as well. I've setup multiple machines this past year with Windows 11 and they are all just straight up local accounts.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#16
post #3

> The company also urged users encountering these BSOD errors to file a report using the Feedback Hub. > To do that, you will have to go through the following steps: > Launch Feedback Hub by opening the Start menu and typing "Feedback hub", or pressing the Windows key + F Something seems off here.

After several (three, I think?) boot failures, Windows will automatically restart to recovery mode and use system restore to undo the last update. This fixes the BSODs until you install the updates again.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#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.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#18
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.

Agreed, vitriol not required.

Still, Microsoft gutted their internal testing, so they hold some blame for disastrous failure, even during preview.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#20

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.

> Installing is a nightmare too with the online account requirement.

My nightmare, before the account shenanigans, was finding a mouse for my HP laptop, whose trackpad didn't work OOB. Then, once I'd managed to go through the installation, the account thing was a PITA because the Intel wifi card wasn't supported, and this laptop doesn't have a wired network port. I was actually going to use an MS account (this is a work computer, and they're all in on MS). But I couldn't set it up without jumping through the hoops of creating a local account first and then grabbing the wifi drivers by booting Linux.

This happened mid-2023 with a 2020 model laptop. Also, HP recommends Windows. Arch Linux worked fully out of the box.

Post reply on HN