Earlier quoted context omitted.
Support it if you want, but you seriously think it's OK for the PC to restart in the middle of a call? What if the user is doing something mission critical; it's acceptable to just wait an hour (or more likely several) to get back to work because "MS knows best"?? There is nothing to stop it from just doing it all over again either. I will never use Windows again because of this behavior.
It was either not fully thought out, or Microsoft's analysis figured that it would cost less to do it this way. Anecdote: When I worked dispatch, the local Network Operations Center pushed out an update that forcibly rebooted all of our Windows workstations...including the machine that ran inbound emergency calls. The admins at the NOC didn't think that anyone would dial 911 at three in the morning. No malfeasance, b…
In the 3am 911 case, those admins could EASILY have cost LIVES with their decision. If that inbound call handler's machine had updates waiting, or more especially had any difficulty installing those updates, you could've had HOURS of downtime in a scenario where MINUTES mean life or death!
I guess my main point is that naivete like that is called criminal negligence and is punishable under the law in many cases. There may have been no malicious intent, but in a case so potentially catastrophic, it hardly matters, and if those admins didn't get into DEEP TROUBLE, they're either very lucky or your administrative discipline system is VERY broken.
And Microsoft is straying into similar territory with this whole thing.