Ummm, no they aren't.
Meltdowns aside, these sorts of errors show that responsible, effective Quality Assurance at Microsoft is a lost art.
In my opinion, the technical people were forced to keep to a release schedule for Anniversary because it had to come out on.... wait for it.... THE ANNIVERSARY. Marketing and upper management decreed it so, I'm certain.
Never mind that it wasn't ready.
THAT is why Microsoft deserves every bit of crap being thrown at them about Anniversary. It's a shambles and a travesty.
Microsoft used to be real good. I've used their products since the late 1970's continuously, and for the most part with satisfaction and good results. They used to be REALLY good. But they lost their mojo and this is no way to regain it.
Well ok.
The expectation is that these companies can release complex software to run on thousands of brands and allow you to connect thousand more things to it without a single issue ever.
That is an utterly absurd expectation.
Every platform has had issues like this. People need to get a grip and stop pretending like MS has wronged them personally. Both the issues with Powershell and the Kindels, according to stories, are being addressed by MS, so people can stop overreacting like their lives are coming to an end.
That’s total crap.
There will ALWAYS be issues, in every piece of software and every operating system.
This is true for Linux, Apple and Microsoft.
I can’t even begin to tell you all the problems I have had to get a new Linux variant/release to accept hardware. Or maybe I’m making up the thousands of forums and user communities out there just for this purpose?
Microsoft, like Linux, has the same problem. These operating systems run on other people’s hardware, and just about any vendor’s hardware is different from the other. That’s 10s of thousands of hardware combinations. Some stuff will just never be pre-tested before deployment.
You work in IT and you know this. If deployment was easy (in both Linux and Microsoft realms), then many of us would be out of a job!
Bottom line, Microsoft’s “woes” with these issues in Windows 10 are NOTHING new. It happened in Windows 8.1, Windows Server 2012 and R2, Windows 8, Windows Server 2008 and R2, Windows 7, Windows Vista, Windows Server 2003, Windows XP, Windows 2000 Server and Professional, Windows Millennium Edition, Windows NT 4.0, Windows 98, Windows 95, Windows NT 3.5/1, and the Windows For Workgroups 3.11, 3.1, 3.0 2.0 and MS-DOS. I’ve been down this road on EVERY one of these operating systems.
Additionally, I’ve been working with Red Hat Linux since it was a baby, using RH 3.0. I’ve been using every version of RH Enterprise since that came out in 2002. On every occasion, I’ve had various issues to contend with, including kernel upgrades that “broke” them. It’s what we do for a living.
And Apple? Well, if you are the sole maker of both the hardware and the software, you can test the heck out of them. Then they “just work”, right?
Still, when Apple release a new version, there are tons of support issues getting that release to deploy properly then, with some folks finding older hardware or software not working, etc., and this is on the approved, made by Apple only hardware.
Bottom line here, Dayglored, is that New Microsoft OSs are always like this, and it is nothing new in Microsoft management like you claim. They’ve always been dollar driven A’Holes!
BTW, the PC came out in 1981. Unless you’re talking about BASIC (written for Altair’s), most folks wouldn’t have worked with Microsoft before IBM came out with the PC.