Comment Re: NVidea's problem, not Microsoft's (Score 2) 317
I feel your pain.
Actually, the most recent system-crippling screw-up I had was installing the latest AMD drivers for a FirePro series card on one of our older machines. You know, the ones where you pay a fortune to have roughly the same hardware as a much cheaper gaming card, because of the quality and capabilities of the drivers? Except that this completely routine update, which we were hoping might finally fix the frequency glitches that have plagued the card from day one, took out the whole machine and even made it difficult to recover using the system restore feature.
Fortunately, this was a Windows 7 machine, so once we did have it up and running again, we just made a note not to install that update, and the user of the computer got on with their work the next day as normal. I'm not sure what the answer to that is supposed to be with Win10, if drivers are going to be pushed out via the same compulsory update mechanism. Presumably you're supposed to defer the driver update on every machine that might be affected (or via WSUS if you're big enough to use it) and hope that someone fixes the problem before the ticking time bomb goes off when you can't defer any longer...