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

41–50 of 150 posts

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#41

Post by Stranger43 »

nehal3m wrote: post #23
kube-system wrote: post #22

Earlier quoted context omitted.

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.

That assumes that the company lets journalist talk to non marketing people.

The term might in marketing department vetted communications often cover over "the techies droned out for 10 minutes using words we did not understand" and few large brands feel that comfortable letting anyone not under some kind of confidentiality agreement talk to anyone in the technical teams.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#42

Post by jonhohle »

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 ;-)

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#43

Post by laserdancepony »

ramblerman wrote: post #21
tw04 wrote: 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 an…

> I "subscribed" to the preview track, and had to reformat my pc twice.

"I subscribed to test betas and they were unstable. Thanks Bill Gates!"

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#44

Post by zamadatix »

nehal3m wrote: post #23
kube-system wrote: post #22

Earlier quoted context omitted.

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.

Everything seems to be from the linked text source so I doubt the journalist actually got to interact with Microsoft at all.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#45

Post by yjftsjthsd-h »

ramblerman wrote: post #21
tw04 wrote: 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 an…

> I "subscribed" to the preview track, and had to reformat my pc twice. It was a fricking disaster. I'm back on osx

Are you tracking the pre-release versions of MacOS?

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#47

Post by tracker1 »

toasteros wrote: post #27
tw04 wrote: 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 ther…

I was on insiders for years, switched for WSL1... I switched over to using Linux as my personal desktop OS when I first say ad results in the Windows start menu search. It may have been preview, but was just one thing too far that someone would even consider it. I still have a windows drive in my desktop, I only booted into it once a few months ago to update my ssd/nvme firmware (samsung bugfix).

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#48

Post by FirmwareBurner »

tw04 wrote: 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 think people might need to put the pitchforks down. It's a preview release, and we have 0 information on the systems in question.

Yeah, but making this info clear in the title doesn't drive the pitchfork driven clickbait FUD that seems to be invading HN lately.

Nearly half of Windows 11 related topics I read here lately were mistakenly titled or factually wrong, and yet full of rage comments of people who haven't even read the article, or don't even use Windows, but came by to tell everyone they use Arch or MacOS.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#49

Post by justsomehnguy »

vladvasiliu wrote: post #20
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.

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

Ah, yes, Gates personally banned the drivers for this 2020 WiFi cards.

Or maybe it was Intel who did a bazillion of cards with a minor diffs and/or didn't ask MS to add this flavour to the default driver set, shipped with Windows install media?

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#50

Post by tracker1 »

pavel_lishin wrote: post #35
ramblerman wrote: post #21

Earlier quoted context omitted.

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

I've sworn off Windows as an OS after multiple dealbreakers: advertisements in the OS, and hard reboots with no warning. I understand there are workarounds - such as buying a non-personal Windows license, and fiddling with the registry - but that's like selling me a car that'll shut its engine off on the highway and force me to listen to its own advertisements while I'm using a bluetooth device, and assuring me that…

Yeah, running insiders and seeing an advert in the start menu search was the final straw for me. I've used it for work a couple times, but mostly choose Mac, only because the corp apple experience isn't as bad as corp Windows can get.
Post reply on HN