This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Remove From My Forums

Windows 10 Pro/Enterprise PCs do not follow WSUS Scheduled Installations

Question
0

Sign in to vote

Remove alert

|

Edit

|

Change type

1

Hello, I have a quick question about Windows 10 integration with existing WSUS, specifically the use of Group Policy settings that control WSUS functionality.

I have utilized the setting "Configure Automatic Updates" with a value of "4 - Auto download and schedule the install" successfully for years with Windows 7 clients. I have my scheduled installation day/time set for Thursday at 10:00 pm (22:00)

On the Windows 7 clients on my network, this installation works as expected. Updates queue up on workstations as they are approved and then they install automatically at 10:00 pm on Thursday if the user has not manually installed them beforehand.

On the Windows 10 client under scope of the same policy, this functionality has changed and does not work as expected.

Instead of the updates installing at the scheduled time, it seems like Windows 10 is trying to handle this for me. Right now even, I have an update that I approved last Wednesday and when I go to the new Updates view, the status message says "A restart has been scheduled". Then, I have a greyed out radio button that reads "We'll schedule a restart during a time you usually don't use your device "right now 3:30 AM tomorrow looks good)."

I have been receiving this same message since last Wednesday but the system hasn't restarted. This would include the time frame (Thursday at 10:00 pm) that falls in scope of my GPO scheduled restart, so I would say that policy object doesn't work under Windows 10.

I am in an environment where I want to tightly control the restart window as I'm sure many other users are. I don't want Windows to randomly decide when to reboot my system or not to reboot it at all. I have trained my user base when they can expect an automatic reboot and now with Windows 10 deployment pending, I can't communicate a schedule to the users.

Please advise on this setting include how to disable or to bring back the old functionality. I have asked the same question on the Windows 10 forums and they directed me here.

If this is a known issue, please respond accordingly and provide timeframe as to when we can expect a hotfix.

Wednesday, October 7, 2015 1:46 PM

All replies

0

Sign in to vote

looks like it's an emerging issue, i've seen a bunch of posts on it but have not had time to test it

https://social.technet.microsoft.com/Forums/en-US/7ae7c38d-9c62-4208-b738-27698ea76061/windows-10-wsus-gpos?forum=winserverwsus

Wednesday, October 14, 2015 7:46 PM
0

Sign in to vote

Yes, here is a link to my post on the Windows 10 forums on the same issue:

https://social.technet.microsoft.com/Forums/en-US/30b67b12-f216-42d7-8245-b95bb7ea0c08/windows-10-wsus-scheduled-updates-do-not-work?forum=win10itprogeneral

I have opened up a Support Case with Microsoft on the issue and have confirmation back from them that it is definitely a behavior specific to Windows 10, and not to WSUS.

I will definitely post back should I get any details as to a hotfix release date, etc.

Wednesday, October 14, 2015 7:53 PM
0

Sign in to vote

I think this is due to a change introduced in Win8.0 which is carried forward into Win8.1 and Win10.

There is an additional GP setting which was introduced, and this might be what you need to do:
Use the Always automatically restart at the scheduled time policy

http://blogs.technet.com/b/wsus/archive/2013/10/08/enabling-a-more-predictable-windows-update-experience-for-windows-8-and-windows-server-2012-kb-2885694.aspx

https://vnetwise.wordpress.com/2014/03/20/howto-dealing-with-windows-2012-and-2012-r2-windows-update-behavior-and-the-3-day-delay/

Don

Wednesday, October 14, 2015 8:01 PM
0

Sign in to vote

Thanks for mentioning that setting, Don. Unfortunately I have included that setting both in domain GPO (using latest ADMX template) as well as in local policy on an isolated Windows 10 machine. Both configurations still failed to actually schedule the reboot.

Wednesday, October 14, 2015 8:24 PM
0

Sign in to vote
I was considering testing and changing our update practice to using setting "4" instead of setting "3" in the "Configure Automatic Updates" GPO in the hopes that Windows 10 would at least obey a regular schedule since it doesn't obey WSUS deadlines. Thanks for confirm that this policy setting is also non-functional. :(

I keep looking around the forums for similar issues (and hopefully, a solution), but I've been tracking most of my experience here: https://social.technet.microsoft.com/Forums/en-US/7ae7c38d-9c62-4208-b738-27698ea76061/windows-10-wsus-gpos?forum=winserverwsus
- Proposed as answer by _DaS Friday, November 13, 2015 1:29 PM
- Unproposed as answer by _DaS Friday, November 13, 2015 1:30 PM
Thursday, November 12, 2015 5:19 PM
0

Sign in to vote

For anyone experiencing this issue can you email me at susan-at-msmvps.com (change the -at- to @) and I need to get some log files to pass along to Microsoft to get this better investigated.

Friday, February 5, 2016 8:49 PM