So does that mean the update will never be installed?
Yes, it can't auto-update while the computer is turned off.
How to make it happen?
Just set it to auto-update at an hour in which your computer is always on. If you are doing this because you don't want to update while you are using your computer, then set it to the time when you usually eat dinner or something, and leave the computer on while you do it.
An alternative, as mentioned by David on the comments, is to set your computer to auto-turn on in the BIOS. Note that not all BIOS support that. To do so:
Enter your BIOS by pressing del or whatever other key is indicated on boot-up - when the computer is turning on.
Look for Resume on RTC Alarm
or Power on By RTC Alarm
or Resume by Alarm
and enable it.
Set the time to 4:55PM or something close to when you want it to update. Save and quit.
That's it, your computer will automatically turn on 5min before the auto-update and then Windows will update. You can also make a .bat
so it will automatically turn off after a few hours or even after the update is finished (by looking for the process using tasklist | find
).
As for strategies from Microsoft's side, they now have the Insider program which allows them to test some patches with a larger audience beforehand. In return, Insiders don't need to buy a Windows license.
Of course there are still many kinds of patches they can't test that way. For example they can't roll out patches of undiscovered critical vulnerabilities to Insiders first, because attackers could thus discover and use the vulnerability before the majority of the non-Insider systems are patched.
Microsoft has frequently broken Windows with updates in the past. Even the update process itself managed to put systems in a broken state. The changes they implemented reduce that risk, but they do not remove it. In short, it's almost guaranteed that some updates will screw up some people's computers, so the risk that you can't access your computer at a critical time due to Windows Update is small but real. Keep in mind in most cases you can just roll back an update, and you will lose no more than 10-30 minutes.
There are 2 ways to look at this:
First, you can put this in the same bucket of risks as a hardware failure (e.g. a HDD dies), in which case you need to adopt a workflow that accepts the temporary or permanent loss of any one device at any point in time. Use a version control server for software development, use shared browser bookmarks, use a cloud based note taking app like OneNote, etc.
Second, you can decide that the risk of a failure due to an update is large enough that it warrants protecting against more so than a hardware failure. In that case you usually want to have a controlled environment where updates install at regular intervals, usually once a week. You also want to be able to prevent the system from updating during some timeframes, e.g. if you do seasonal trading you wouldn't want to install any updates during the trading season. In these cases, the obvious solution is to not use Windows Home Edition. I'm not sure which Windows versions are currently included in MSDNAA, which is free for students, but I'd expect it to have at least the Pro and Server versions.
If you want to know how to prevent Windows Updates in Windows 10 Home Edition, there are a couple questions that attempt to address this question: Stopping all automatic updates windows 10 , How can I defer updates in Windows 10 Home? , Make Windows 10 stop installing driver software automatically Personally I'd just try to firewall wuauclt.exe, or stop the wuauserv service.
Best Answer
Security updates achieve 2 things: 1. They fix vulnerabilities, usually previously unknown. 2. They make every attacker aware of what the vulnerability is.
Releasing a patch makes unpatched systems less secure. A patch might add a new unknown vulnerability, which might be exploited. But by not installing a patch you decide to keep a known vulnerability, which will be exploited.
You can block updates even with the Home version in various ways, for example with a firewall.