Hi everyone,
I'm using Windows 10 Home OEM 64Bitand I have the following problem: lately, my PC reboots between 2 and 5 times a day due to updates (windows or from automatic security maintainance). 15 mins before it reboots it warns me, and then after 15mins it just reboots without warning, in the middle of everything. Needless to say, this is extremely aggravating.
I disabled automatic windows updates, but it doesn't seem to work.
2 or 3 things are "strange" in my windows environment:
- in windows update settings, the option "select a restart time" is forever grey, i.e. I cannot set such a time. I havn't found anywhere how to fix this.
- in windows update settings still, it tells me since at least 5 days that there is an update available (version 1511, 10586) and that "a restart has been scheduled".
Aside from that, I unchecked the option "give me updates for other microsoft products..." and selected notify to schedule restart and put "off" in the menu called "choose how updates are delivered".
Can you please help me, I'm a bit at a loss and can't find a solution by simply googling my problem...
Hello askir Welcome to the windowssh blog!
It's ironic but the new and latest Windows Insider Preview build addresses this exact same issue by seeing a brand new option to schedule updates to work around the time period you are active at the machine! In fact with a test seen on a previous build before that saw the latest go on it is quite possible to add this new option by simply adding in two new values in the System Registry manually however. The quick edit sees the new option appear in seconds! Windows Update Active Hours - Change in Windows 10 - Windows 10 blog
The test here was to find out if it was possible and confirmed in the initial reply to the new guide posted. What the Active Hours does is see the Start time and End time set where all updates are held off which includes automatic system restarts until the down time when you are away from the machine. These two new registry entries are pointed to in the guide itself making for easy reference. This could be a quick fix for seeing your problem solved as well by setting a predetermined activity period forcing all updates to go on when you are not present.
Try those 2 settings, not sure if they work on Home though. Run CMD as admin and enter:
reg add "HKLMSoftwarePoliciesMicrosoftWindowsWindowsUpdateAU" /v "AlwaysAutoRebootAtScheduledTime" /t REG_DWORD /d "0" /f
reg add "HKLMSoftwarePoliciesMicrosoftWindowsWindowsUpdateAU" /v "NoAutoRebootWithLoggedOnUsers" /t REG_DWORD /d "1" /f
Other than that, I can think only about disabling WU completely and perform updates yourself.
The two reg entries should work as easily on the Home edition as it would in Pro, Education, possibly even the Enterprise edition since the WU is a standard function in all editions. This simply adds the option to limit the time updates will take over when set to automatic. 10 no longer has the notify but let me choose when option and why MS must have gotten a good earful from people about that! People do not like to be interrupted while they are right in the middle of something and why this option is actually long overdue for Windows period!
Hi, thanks a lot !. I think it fixed my problem indeed (regedit thing).
Well that's good to know! I couldn't actually try out the new reg entries on an older build long enough without simply setting up a new VM with the Threshold 2 update in mind. Another problem that appeared suddenly last night wasn't update related however which there won't be any reg tweaks to find when the latest build suddenly restarted in order to collect information on something?
I was right in the middle of posting a reply on another topic and suddenly the screen goes blue with all of the text explaining that one. The browsers windows were then restored following a lengthy wait after the immediate restart to see a totally dark screen and then finally life came back. Apparently MS is seeing some automatic collection of data from this build going on? Or it might have simply been from an old pc game stalling earlier in the day being in an event log being gathered up.
