Live data from Hacker News

New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

bleepingcomputer.com

61–70 of 150 posts

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#61

Earlier quoted context omitted.

> 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?

I haven't used a device that Windows didn't ship drivers for In twenty years!

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#62

Earlier quoted context omitted.

[flagged]

Eh, they're both proprietary OSes. Maybe you're more used to the UI paradigms of one or the other, but other than that, I don't see a strong reason to prefer one or the other. Also, I personally don't use any of these tools except Office, but I'm pretty sure classing developers as having psychological issues based on their language ecosystem choice is against HN guidelines.

Under the hood macOS is Unix though... so there is a lot to be said for that. I can run tools like sed, awk, grep right out of the box. As someone who is in a shell 24x7 on multiple remote linux servers it is nice to also have a very similar experience within my local desktop environment.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#63

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.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#64

Earlier quoted context omitted.

Eh, they're both proprietary OSes. Maybe you're more used to the UI paradigms of one or the other, but other than that, I don't see a strong reason to prefer one or the other. Also, I personally don't use any of these tools except Office, but I'm pretty sure classing developers as having psychological issues based on their language ecosystem choice is against HN guidelines.

Under the hood macOS is Unix though... so there is a lot to be said for that. I can run tools like sed, awk, grep right out of the box. As someone who is in a shell 24x7 on multiple remote linux servers it is nice to also have a very similar experience within my local desktop environment.

So then you just `wsl --install` and you get a proper Linux distribution. Also get the Windows Terminal from the store and you're off to the races.

I honestly consider this a better experience compared to Apple's BSD tools and lack of first-party package manager.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#65
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…

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

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#66

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

I can't comment on Office, Adobe and Visual Studio, but for Ableton or any other DAW, I would certainly choose macOS over Windows. Audio runs much smoother on Mac than on Windows. Lower latency, less dropouts, better overall stability from my experience.

Too bad that audio is total joke on Linux. There's very good software, like BitWig and Reaper, but the audio subsystem is total mess doing random stuff all the time. PipeWire seems promising but there are still problems. Maybe one day.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#67

Earlier quoted context omitted.

> 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?

Those are pretty standard Intel cards installed on laptops with Intel CPUs. ax201 or something. If "nothing-ever-works-without-fiddling" Linux is able to ship drivers for that card and work out of the box, I don't see why windows couldn't ship with drivers for that, especially since they seem to get updates via Windows update, so ms has them. Plus, if you're going to force people to use an internet account, maybe make sure that they'll actually be able to get online?

Or maybe the whole point of not supporting the touchpad was to weed off the faint of heart and send them off to Linux?

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#68

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

I had to google Ableton.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#69

Earlier quoted context omitted.

Under the hood macOS is Unix though... so there is a lot to be said for that. I can run tools like sed, awk, grep right out of the box. As someone who is in a shell 24x7 on multiple remote linux servers it is nice to also have a very similar experience within my local desktop environment.

So then you just `wsl --install` and you get a proper Linux distribution. Also get the Windows Terminal from the store and you're off to the races. I honestly consider this a better experience compared to Apple's BSD tools and lack of first-party package manager.

if you enjoy using windows, sure this is a perfectly valid option.

Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens

#70

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 "subscribed" to the preview track, and had to reformat my pc twice. "I subscribed to test betas and they were unstable. Thanks Bill Gates!"

Yeah, I also don't get how people voluntarily choose to use a beta OS, and then complain that it broke.

Like, my brother in Christ, that's why there's the stable version of that OS.

Post reply on HN