Attached below are my existing settings.
1) GPE settings - (3 - Auto-download and notify for install) - which is now over-ridden since the anniversary update.
2) Restart options
Rather than stopping the updates entirely, what about stopping the associated reboots?
This would be ideal, I dont want to stop the updates. Just how it automatically reboots. If you aren't at the PC at the time to see the warning its tough luck
---
Outside active hours is also pretty useless as I run my backups overnight, I have separate backups which all start at various times. I do not want it rebooting itself overnight.
My backup plan is
here. Only difference is that I now use macrium rather than windows backup.
Yep it may seem like overkill, but when I had 2 identical drives fail in June this year I'm glad I did have otherwise
all the site stuff would be gone now.
Just 2 days ago I would have lost a lot of code if I didnt have a backup, backup. Admittedly that was my fault for uploading and overwriting a wrong file. :/
plus to a lesser extent, there's stuff like DSLstats which will end up closing without doing a graceful shutdown so doesn't do screen caps etc.
Its also possibly the way I work, say if I'm doing some coding or looking at the site late at night. Quite often I will get tired and just abandon things ie not want to shut down anything open or Ive also been known to leave posts half finished.
-----
I note that some of the suggestions are setting active hours or the now defunct Group Policy Edit.
These are my logs which show what happened last night and how it shut down by itself when I wasnt around.
27/10/2016 21:34:43
Windows Update started downloading an update.
27/10/2016 21:34:44
The access history in hive \??\C:\WINDOWS\System32\SMI\Store\Machine\SCHEMA.DAT was cleared updating 1 keys and creating 1 modified pages.
27/10/2016 21:34:45
The start type of the Windows Modules Installer service was changed from auto start to demand start.
27/10/2016 21:34:51
The start type of the Windows Modules Installer service was changed from demand start to auto start.
27/10/2016 21:36:24
The start type of the Windows Modules Installer service was changed from auto start to demand start.
27/10/2016 21:36:46
The start type of the Windows Modules Installer service was changed from demand start to auto start.
27/10/2016 21:36:47
The start type of the Windows Modules Installer service was changed from auto start to demand start.
27/10/2016 22:01:57
The start type of the Windows Modules Installer service was changed from demand start to auto start.
27/10/2016 22:02:01
Installation Started: Windows has started installing the following update: Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3197954)
27/10/2016 22:03:08
Installation Started: Windows has started installing the following update: Security Update for Adobe Flash Player for Windows 10 Version 1607 (for x64-based Systems) (KB3201860)
27/10/2016 22:03:10
Installation Successful: Windows successfully installed the following update: Security Update for Adobe Flash Player for Windows 10 Version 1607 (for x64-based Systems) (KB3201860)
27/10/2016 22:03:10
Installation Started: Windows has started installing the following update: Update for Windows 10 Version 1607 for x64-based Systems (KB3199986)
27/10/2016 22:03:12
Installation Successful: Windows successfully installed the following update: Update for Windows 10 Version 1607 for x64-based Systems (KB3199986)
27/10/2016 22:34:00
The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start.
27/10/2016 22:36:02
The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start.
27/10/2016 23:14:13
The process C:\WINDOWS\System32\svchost.exe (SI7) has initiated the restart of computer SI7 on behalf of user NT AUTHORITY\SYSTEM for the following reason: Operating System: Service pack (Planned)
Reason Code: 0x80020010
Shutdown Type: restart
Comment:
27/10/2016 23:14:28
User Logoff Notification for Customer Experience Improvement Program
27/10/2016 23:15:52
DHCPv6 client service is stopped. ShutDown Flag value is 1
27/10/2016 23:15:53
The Event log service was stopped.
27/10/2016 23:15:57
The kernel power manager has initiated a shutdown transition.
27/10/2016 23:15:58
The operating system is shutting down at system time 2016-10-27T22:15:58.408023100Z.
27/10/2016 23:16:09
The operating system started at system time 2016-10-27T22:16:09.497775500Z.
27/10/2016 23:16:17
Microsoft (R) Windows (R) 10.00. 14393 Multiprocessor Free.
27/10/2016 23:16:17
The Event log service was started.
27/10/2016 23:16:17
The system uptime is 8 seconds.
All I want really is to be able to control updates like I used to be able to and reboot when I want... not when windows thinks it will. Judging by the amount of complaints on the MS site Im far from alone.
Its looking like
How to disable auto matic reboot after the installation of updates using the Registry editor from ejs link may be the only viable option.. which will be the next thing I try.
It does seem rather stupid that there's no way of controlling a shutdown. The current update system is obviously not designed with people who use their PCs for work related activities outside 9-5... nor those which may actually be doing something useful all the time and there is no such thing as Inactive hours.