Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

bleepingcomputer.com

Post reply on HN
Print view View original

111–120 of 150 posts

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#111

Post by tuetuopay »

justsomehnguy wrote: post #107
tuetuopay wrote: post #91

Earlier quoted context omitted.

I recently had the (dis)pleasure to install Windows 10 on a Dell XPS laptop from 2018. The Windows installer had no drivers for the nvme controller _that is provided by the CPU itself_, so a platform controller. Oh and getting the installer to recognize the drivers was much harder than the usual "stick the files on a thumb drive, plug to laptop, tell the installer". I had to generate a custom Windows ISO with the dri…

Yep, just as I said in the previous comment: everyone is at fault but for sure it wasn't the vendor of the device! How the vendor could be the culprit in doing something what would cripple the boot/install of the OS? Nonsense!

The vendor? Ha! Let me laugh.

Would this have tripped on some obscure device specific to Dell laptops, sure, I would understand. (like their blimey fingerprint reader). But this is the standard NVMe controller on this generation of intel CPUs. The drivers are common for _most intel platforms_: the Intel Rapid Storage Technology.

As somebody else pointed out, Linux fares much better in this space. All devices are properly recognized out of the box, including this bog-standard NVMe controller.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#112

Post by gumballindie »

jonhohle wrote: post #42
whalesalad wrote: post #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.

It’s somewhat ironic that Windows users used to call Macs “toy computers”. Now most deeply technical people are using Macs or at least Linux or BSD and Windows is relegated to games. It seems Windows is for toy computers ;-)

> Windows is relegated to games.

Unless you absolutely must play ea games then even that can be done on linux rather nicely.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#113

Post by gumballindie »

whalesalad wrote: post #74
DiabloD3 wrote: post #71

Earlier quoted context omitted.

I don't know any technical people who use Macs with OSX still installed. They all gave up on that trainwreck of an OS, and either their final Mac died and they replaced it with an even better laptop by a different vendor (Framework, et al), or they still own a Mac but it now runs Windows or Linux (and when that one dies, it will be their last, and they will become post-Mac, too). I know exceptionally few tech people…

What the heck are you on about? This is patently false. I've been using Mac hardware professionally since 05 in a ton of different environments. We very rarely had issues. Apple makes the best laptops in the world, nothing else comes remotely close.

Battery aside apple laptops are rather lame.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#114

Post by konschubert »

deely3 wrote: post #63
konschubert wrote: post #46

Windows, Office and Teams are so weirdly unpleasant to use. It's hard for me to put my finger on it - it's a mix of ugly UI, bad UX and general bugginess.

I can't agree about Office and Windows tho. They still have quirks, and I definitely can put finger (a lot of fingers actually) at points that stupid and I can't stand, but in general I like working with Office and Windows. I tried Open Office, Libre Office, few Linux distibutives, but return to Windows everytime.

Have you tried google docs? The cooperative editing and commenting feels much more robust than what office 365 is doing.

The default new tab on bing is a bunch of trashy news. It’s just icky.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#115

Post by ndriscoll »

bitwize wrote: post #97
rstat1 wrote: post #72

Earlier quoted context omitted.

If their supported CPU list wasn't completely arbitrary BS, then you might be on something here. But it isn't There are CPUs that have no problem running the OS that are for no discernible reason "not supported". And I'm not talking about old crap like Pentium 4s or something. I'm talking about ones that are barely 5yrs old.

Microsoft is moving to a model of "signed software from power on to application level" for Windows. The supported CPUs have the TPM features necessary to support this transition. Presumably, for Windows 12, remote attestation capability (Pluton) will be required.

Right and for the home user, there is exactly zero benefit from this. There is no reason someone should have to go buy a new computer to replace one that's only 5 years old. A world where local accounts are an enterprise feature and hardware attestation is a home feature is completely backwards.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#117

Post by failuser »

DiabloD3 wrote: post #71
jonhohle wrote: post #42

Earlier quoted context omitted.

It’s somewhat ironic that Windows users used to call Macs “toy computers”. Now most deeply technical people are using Macs or at least Linux or BSD and Windows is relegated to games. It seems Windows is for toy computers ;-)

I don't know any technical people who use Macs with OSX still installed. They all gave up on that trainwreck of an OS, and either their final Mac died and they replaced it with an even better laptop by a different vendor (Framework, et al), or they still own a Mac but it now runs Windows or Linux (and when that one dies, it will be their last, and they will become post-Mac, too). I know exceptionally few tech people…

Are all those technical people Linux kernel hackers? Maybe even just hackers, running a some BSD OS.

You should realize “I don’t know people who do X” is a very weak argument.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#118

Post by hypercube33 »

tw04 wrote: post #65
toasteros wrote: post #27

Earlier quoted context omitted.

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 ther…

> Is it therefore possible that this bug check is being implemented as part of the journey towards actually dropping "support" for these CPUs? That seems entirely possible. That being said, I'm not sure I'm going to be upset about them dropping support for a 20-year old CPU built on an architecture that I think is pretty widely accepted as a failure.

The two I saw on Reddit having this bsod were on 13th gen Intel so I'm not sure but I'd guess some issue handling p and e core transitions is causing the problem.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#119

Post by nullindividual »

whalesalad wrote: post #102
nullindividual wrote: post #90

Earlier quoted context omitted.

Windows runs the largest of enterprises. Very few go without at least Active Directory.

Fortunately the enterprise IT seems to be slowly waking up to the realization that AD is just LDAP wrapped in a thick layer of (very expensive) Microsoft epoxy and glue. OSS is alive and well in the enterprise!

AD is LDAP+Kerberos+mgmt tooling+integrated DNS/DHCP+replication svcs

Only Samba implements part of the above. OSS has a way to go, yet.

To be clear, AD never has, never was, and is incapable of being “just LDAP”.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#120

Post by rstat1 »

bitwize wrote: post #97
rstat1 wrote: post #72

Earlier quoted context omitted.

If their supported CPU list wasn't completely arbitrary BS, then you might be on something here. But it isn't There are CPUs that have no problem running the OS that are for no discernible reason "not supported". And I'm not talking about old crap like Pentium 4s or something. I'm talking about ones that are barely 5yrs old.

Microsoft is moving to a model of "signed software from power on to application level" for Windows. The supported CPUs have the TPM features necessary to support this transition. Presumably, for Windows 12, remote attestation capability (Pluton) will be required.

>> moving to a model of "signed software from power on to application level" for Windows.

This already a thing with Windows 10 in S Mode. So definitely not that.

There are quite a few CPUs that implement the necessary TPM crap and aren't supported. So not that. There are several new CPU features they want, but half or 3/4s of the CPUs on the supported list don't have them. So not that either.

Only valid reason left is that's arbitrary and not based on anything logical.

Post reply on HN