#DISABLE QUICKBOOT UPDATE REMONIDER UPDATE#

Maybe it'll be allowed to run in a VM with no network access, or limited network access to whitelisted IPs, but I don't ever see that OS running on bare metal on any of my systems.

#DISABLE QUICKBOOT UPDATE REMONIDER UPDATE#

Unless this changes with the Big November Update (TM), version 10 is where I get off the Windows train. Doesn't matter - it's still the end user's (read: property owner's) decision. Maybe it opens the user up to hacks, sploits and pwnage. Taking away the option to say 'No, not now, not ever' is crossing the line. This blog post was originally written to address end of support for VMware ESXi 5.5, but has been updated to include end of support dates for versions 6.0, 6.5, 6.7 and 7.0. There's nothing wrong with any of these provided the user has the final say on what happens. Opting in to optional/recommended updates is fine.

Setting updates to Automatic by default is fine. EULA nothing, I don't care, I will disregard and disrespect anything written therein that claims the authority for MSFT to make these decisions. They do not have the right to unilaterally decide for me or anyone that that person's PC should be updated on any schedule other than what that person wants. The fact is that a PC is personal (or corporate) property, and unless we're talking about boxes on the Microsoft campus or in Steve Ballmer's house, a PC is property of someone other than Microsoft. It's not about 'best practice' or the PC anti-vax equivalent of the herd-immunity argument.

It's really aggravating to hear all the defenses of Win10's update policy in discussions, including some right here on SW.

Disable quickboot update remonider