Comment on Microsoft has a new idea on how to deter students from MacBook Neo - 9to5Mac

• ProdigalFrog@slrpnk.net ⁨6⁩ ⁨days⁩ ago

  I think a majority of people would consider needing to disable multiple parts of the default installed system to not encounter potentially breaking bugs to be a pretty big indicator that the platform is not as stable as it used to be.

  Personally, I never had to disable anything, perform any specific actions, or disable a particular part of Windows XP or Window 7 to achieve a very stable system, and new updates generally didn’t introduce any bugs either since MS had a pretty big QA team.

  There are now regularly reports of major or critical components of a windows system failing or even becoming unbootable due to updates or bugs in new features in Windows 11, which is very much a change from the norm.

  It is likely these bugs are being introduced far more frequently due to MS laying off the majority of their QA team, and instead relying on regular users to report bugs after they have already been shipped.

  source

  • Steve@communick.news ⁨6⁩ ⁨days⁩ ago

    Wow. I had full blue-screen system crashes every couple months at least, even daily with XP and 7. I haven’t seen any with 10 or 11. But I’ve always kept them both pretty clean.

    source

    • ProdigalFrog@slrpnk.net ⁨6⁩ ⁨days⁩ ago

      I definitely had a few blue screens with XP over the years, maybe once every 5 or 6 months?

      7 was super stable on my hardware, I’ve probably had about the same amount of blue screens on that as I did on Windows 10, maybe about 4 or 5 from what I can recall? The bigger issue I had back then was AMD’s GPU drivers were insanely unstable at that point, resulting in constant green screen crashes from youtube videos.

      At least for me, blue screens haven’t been too much of an issue, especially since after they reboot, everything is still working as normal. That’s in contrast to Windows 11’s bugs introduced from updates, which often introduce a new persistent problem that a user either has to actively troubleshoot to resolve, or cannot resolve on their own, leaving them to wait until Microsoft pushes out a fix.

      Examples of that being:

      • KB5077181 breaking Blutooth and causing Samsung devices to lose the ability to access the C: drive
      • KB5085516, preventing users from resizing or moving windows, which itself was supposed to be a fix for KB5079473
      • Microsoft themselves admitting that multiple major core features were broken for months

      I personally consider the severity and frequency of these issues are appearing in Windows 11 to be fairly unprecedented in the history of Windows, which happens to coincide with the QA team being fired.

      source