This isn't even a case of bloatware or 9000 different "standards" though.
It's a case of MS either hiring incompetent fuckups, or complete assholes.
@thecaveman We had a spat of destroyed units, because other units, due to a parts issue, had been entirely replaced with new units that had blue trim. So kids were destroying their regular all black units, to get the ones with the blue trim. Despite them being exactly the same, except for the blue trim.
We knew this, but couldn't label it as "intentional damage" because we can't actually prove that. We can only prove that if the internal wires are actually "cut" (which does happen).
OH, and the "notes" we get with them. This one takes the cake.
"Unit will not charge unless charger is plugged in".
Yeah, it's my fault that Windows forces me to upgrade, to use ancient formatting standards, that it wants to know what turns me on. How dare I.
On a more serious note, I agree, too many people complain about OS problems when it's user error. User error is such a horrible and chaotic pain for programmers to deal with.
I think the single biggest problem with Windows (regardless of version) is the user. Seriously - if you work in the repair/service sector, how many times do you see a customer come in with a computer thats not working properly and time and time again its because of something the user has done and not the OS. The most common one for me is people doing something that some forum says to do to increase performance and they have NO FUCKING IDEA what they are actually doing, dont understand the side effects, and blame the OS for something a forum recommended they do without understanding the side effects and consequences. So many "Disable this service" or "Edit this registry key" forum posts and the majority of them are ludicrous.
This is an obvious design flaw. If the storage drive fails, then the entire system is rendered inoperable. What kind of moron designs a system like that?
RAID does the opposite except for RAID 0, which I wouldn't know why people still use it, I am still rocking SATA SSD speeds, and if that ain't enough, there is PCI-E and NVMe SSDs
but shit like that can happen. as for the System shitting itself after you removed a hard drive. did you consider if you forgot to set the drives properly?
Apparently Windows 7 would add the second drive the the boot partition/table/whateverit'scalled, in such a way that the system will fail to boot if the storage drive is missing.
I ended up just taking the SSD instead, blanking it (with a Linux thumb drive, because Windows apparently can't be trusted to do things correctly/sensibly/logically), and re-installing her copy of Windows 7 on the 1tb WD Blue drive instead.
which is why and in good practice if you are doing or tinking with the OS from the hard drive level it's best to remove any other hard drive from the system. sadly you learned the hard way.
That and for future reference if you are using an HDD. make a seperate partition for the OS. that way if you move to an SSD you can just take that partiiton clone it to the SSD then delete the partition from the HDD and problem solved..
Windows won't allow you to clone the OS unless you have a drive of similar size.