Yes, there is a difference, but the auto-scheduling part is not the one that has the bug. The bug is that OS is in a borked state, and the update infrastructur

Yes, there is a difference, but the auto-scheduling part is not the one that has the bug. The bug is that OS is in a borked state, and the update infrastructure cannot deal with it. This is what ends up bricking the system. (Using the loose definition of the term here, I understand that it doesn't literally damage the hardware) The overall big picture is the fact that most users don't want to be system administrators; they just want it to be managed automatically. However a subset of users, do want to administer the system and have a level of control, and this is where Microsoft screwed up, by not providing us those tools. At work we have our IT manage the updates on all of our machines, and they have managed to apply some kind of policy where they can control the updates. I am assuming this is only possible in a domain environment, and not on a stand-alone PC.