31–40 of 150 posts
Earlier quoted context omitted.
When an issue is at this scale, you have to give some acknowledgment of the issue even if you don't know its cause.
Agreed, but then you'd expect a behemoth like MS to respond that they're aware, working on finding cause for the issue and releasing a fix. What they did here is throw out a 'maybe it'll fix itself'.
When Microsoft says "your CPU needs to be this high in order to run Windows 11", perhaps listen to them eh?
It would be trivial for Microsoft to strictly enforce their CPU "requirements" on install. They've chosen not to. The workaround for that isn't some weird hack, it's an explicit registry value that they made.
Earlier quoted context omitted.
> My guess is that a lot of people are using the crappy Home edition. What makes Home crappy? Other than the account thing, obviously. You can't join a domain with it either, but then most people don't have a domain at home. There's some other disabled features, like Hyper-V, but why should people have to pay for a higher tier Windows to use a local account if they don't need the other features?
I want to say RDP is limited to higher trims. I don’t think you can Remote Desktop to home. But otherwise I agree with your points.
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 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 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 I can adjust the behavior. If I know how. If I even know that's possible. If I'm willing to pay more.
That feature is sending an insanely large amount of personal data to Microsoft, and it's horribly irresponsible to include this feature as it is.
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.
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
That being said, I'm terribly frustrated with the direction Microsoft is taking Windows and I hope to stay off of 11 for as long as I can.
Most 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 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.