disk Posted February 15, 2017 Posted February 15, 2017 We have a WSUS machine group where we have approved the latest build (1607) and have assigned a number of Windows 10 Enterprise PCs running 1511. I have the following policies set and seemingly applied: Turn off auto-restart for updates during active hours: Enabled: Active Hours 7am-7pm Always automatically restart at the scheduled time: Enabled: 30 minute timer Configure Automatic Updates: Enabled: 4 - Auto download and schedule the install: Every day 01:00 Specify intranet Microsoft update service location: Enabled with location set Do not include drivers with Windows Update: Enabled Select when Feature Updates are received: Enabled: Current Branch for Business Select when Quality Updates are received: Enabled For two days now, I have checked two PCs that are running build 1511, and for two days now, when opening the Settings app and checking the Update status, one shows it has downloaded and staged build 1607 and states that 1am looks like a good time to schedule the reboot for install. That makes sense since 1am is what is set in policy. The PC was turned off when I left both days, but I verified it is waking up at midnight via the BIOS wake time. The other PC has been left on since Monday morning and has yet to download the upgrade. I have not yet had time to go through the event logs or run a diagnostic (I was thinking of trying the free SolarWinds WSUS Diag tool). That PC just shows it last installed updates on Feb 4th. Any one have any input on what may be going on here? I'm more concerned with the PC that has downloaded and staged the upgrade but refuses to actually reboot and finish installing at the specified time.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now