I was aghast that you cannot move the taskbar. Now I am forced to keep it in the least optimal orientation. On my employer-provided system that is. No way is that dumpster fire of privacy invading, 80% baked UX, nonsense getting anywhere near my own devices.
New Windows updates cause UNSUPPORTED_PROCESSOR blue screens
51–60 of 150 posts
Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens
#52Earlier 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!"
I ran insiders since later windows 8.1 updates... I had to reinstall a couple times, when the win11 went full release (didn't have secure boot and tpm enabled and it broke itself) and there was another bug a few months later. What really irked me into leaving was that someone thought it was cool to show literal ads in the start menu search results. Insiders or not, that's something that is just wrong. I changed my default boot to my linux drive and haven't looked back on my personal desktop.
Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens
#53Earlier quoted context omitted.
> I can’t think of a compelling to use windows outside of gaming. - Office - Adobe - Ableton - Visual Studio
[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.
Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens
#54I 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…
>drive the pitchfork driven clickbait FUD that seems to be invading HN lately.
This isn't "lately", HN has been this way since at least 2017 when I started reading. If you didn't notice it, that's on you. Almost nobody has ever read the articles on HN.
Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens
#55My 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 ;-)
I've never heard crap like that in my life before.
Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens
#56My 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 keeps me trapped using Windows on my main home workstation is simply that a lot of the professional software I use is Windows-only, and always will be.
Fortunately, the advancements in Proton and better cross-platform support for a lot of software has let me use Linux on my gaming computer and notebook. There are a few games which I can't play, but honestly there's so many options available that I don't miss them much. I don't think I'll ever completely eliminate Windows from my life, I think around 2021 was The Year Of Linux On The Desktop for me.
Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens
#57My 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 did three installs of Pro this year. Two of them required hacks to force local account creation because the motherboard (Asus) ships with a _literal rootkit_ that injects a wireless driver that Windows itself does not ship with. So you either have to disable that in firmware before first boot to Windows OOBE, or run the BypassNRO cmdlet from a hidden shell to convince it that you do not, in fact, have internet access.
I tried to domain join the third device to see what that flow is like. It asks:
1. Personal use / Work or School
2. You are asked to login to Azure AD. You have to click a small (10pt?) link for "Sign-in options." with no indication that will let you join to the domain.
3. Pick "Domain Join instead"
4. It asks you to setup a local account ("Even better, use an online account" :-)
5. _You finish setup without the device actually being joined to the domain!?_
6a. You now have to login (click)
6b. and go to the system settings (click)
6c. go to accounts (click, ad for M365),
6d. go to "Connect to work or school" (click),
6e. click another "Connect" button with no indication that it will join it to a domain,,
6f. Click another small link for "Join this device to a local Active Directory domain" to domain join the PC.
So, I'm sorry, but if you think the Pro SKU is better in this regard you are just incorrect. There is no excuse for these dark patterns, this is user-hostile behavior designed to convert you to being recurring SaaS revenue and not retail revenue.
As an added bonus I just tried to create a Windows 11 VM in hyper-v to confirm my memory, and _Microsoft Hyper-V_ doesn't even correctly configure itself to allow Windows installation to proceed by default. (Secure Boot enabled, but no vTPM.) It then proceeded to download updates to the installer and reboot without a prompt or any option to skip it. Microsoft _clearly does not give a shit_ about the OOBE if you are not using their cloud services.
Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens
#58Earlier quoted context omitted.
Agreed, vitriol not required. Still, Microsoft gutted their internal testing, so they hold some blame for disastrous failure, even during preview.
It's always puzzled me how much people are willing to take from Microsoft for products they pay good money for, without ever considering that there might be an world where not everyone buys their software from the same vendor.
Almost nobody buys Windows though. The vast majority of users get given a laptop with windows on it from work, where the robust AD system is pretty great, though O365 is a letdown in a lot of ways, and the rest get Windows pre-installed on their laptops from the store, where microsoft gives OEMs a sick deal.
The only people who "buy" Windows are those who build their own gaming machine. Even then, they usually buy a sketchy "volume license" key off ebay.
I bought windows retail, because I actually like the Windows kernel, and despise running pretty much any install of Linux that isn't just a command line to boot daemons and web servers from. I use my computer every single goddamn day, and don't ever want it to randomly break, which Linux has always done to me. The steam deck is the first Linux install that hasn't been utterly useless or shit the bed on me.
Every single problem I have had in Windows has been caused by shitty hardware, or AMDs abysmal drivers.
Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens
#59Most popular OS on planet earth and they can't afford testing their software on popular CPUs These execs and managers should be criminally charged
I agree with you. Except for criminal charge. There no complex, big, up-to-date and bug-free program in a world.
Re: New Windows updates cause UNSUPPORTED_PROCESSOR blue screens
#60Earlier quoted context omitted.
> I can’t think of a compelling to use windows outside of gaming. - Office - Adobe - Ableton - Visual Studio
[flagged]
>If I needed all of those tools for my daily workflow I’d be on macOS without hesitation.
And how do switch my existing PC from Windows to MacOS, without spending money to buy new proprietary HW in a locked-down unrepairable unupgradable ecosystem that comes with insane markups on RAM and storage?
At least Linux, works with what I already have and doesn't require me to spend money on proprietary HW and then spend more money on paid apps just to have some functioning window management out of the box. :drops mic: