That actually already happened once, with a Windows NT 3.51 server update, it was pretty nasty.
Fortunately MOST server guys who use Microsoft know that they need to have complete backups, not just client file backups.
I can understand why patches can't always be removed, or at least, I think I do, it probably has to do with where those patches are installed. If they make a change to an OS critical .dll, it would be a big hassle to store the old one while still keeping it protected, and then swapping them back etc.
So far I have to say that their automatic update system is pretty streamlined. Ofcourse, the fact that every other day there is another "windows critical" patch shows that despite their Trusted Computing broohaha, they still don't know jack shit about security.
Btw, did anybody install this yet? Any noticeable improvements on anything?
I tend to wait with new DirectX's until a game comes out that tells me "You MUST have DirectX (one higher than I've got) installed to play this game!".
Then I try to play it anyways, and only if it's funky do I upgrade.
Creston, firmly remembering the dreaded days of DirectX 1 and 2... (When you had to reinstall your video and audio drivers, because Microsoft decided that their "generic" drivers were much better than your specific ones, and so installed generic ones without asking you.)