Comment by ndiddy
One large contributor to modern Windows's lack of quality is that Microsoft laid off all of its dedicated QA staff in 2014, with the expectation that developers would own the OS's quality themselves, and whatever they miss would get caught by telemetry reports from Windows enthusiasts who sign up to test new versions for free. Getting rid of QA eliminated Microsoft's institutional knowledge of what causes bugs, what areas to look at, etc (invaluable when you're dealing with a 30+ year old codebase where large portions were written prior to automated testing being standard). The free Windows enthusiast testing didn't make up for this because you can't expect them to act like how a QA tester would act.
Of course I don't expect Microsoft to suddenly start caring about product quality. The Windows user base has largely stopped growing, so MBA logic is to spend the bare minimum resources on maintenance and to funnel the existing userbase into growth areas like cloud/AI services.
I can totally see how letting go the dedicated QA roles increased the amount of bugs that ship to customers, but
> Getting rid of QA eliminated Microsoft's institutional knowledge of what causes bugs, what areas to look at, etc
Seems incorrect from all interactions I've had with dedicated QA to day.
They usually have no idea about any of that, what they do know is how to use a software and what scenarios have previously broken, but not from a technical perspective that can reason about error scenarios. More like a power user that just learned to use a UI, without knowing what it actually does.
I feel like their recent push to AI driven development has likely had more impact in their issues in the last 2 yrs vs a decision that's at this point 11 years in the past - but they are probably both (along with other unnamed factors) contributing to this end result.
Overall saddening, as windows 10 really was a big leap forward in usability.