locked
Update install Win7 vs Win10 RRS feed

  • Question

  • We are running WSUS 3.2.7600.274 on Server 2008R2 and have a mix of Win7 Pro and Win10 Pro clients in our environment with a WSUS GPO scheduled to push approved updates at 9:00am. I noticed that the Win7 machine downloads the updates from the WSUS server and shortly thereafter a pop-up appears prompting the user to restart. This pop-up never appears for Win10 users, rather Win10 schedules the install for 9:00am the following day which is obviously not optimal.

    How can we change this behavior on the Win10 clients to prompt the user to restart their machine?

    Thanks


    Hank Vare

    Friday, June 24, 2016 2:24 PM

All replies

  • Hi tehrep43,

    1. After installing the update, could you see the restart scheduled pop-up in windows update, could you provide a screenshot after installing the KB in windows update on win10;

    2. What is the AU option do you select?

    3. Have you enabled "No auto restart when logged on users"?

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Monday, June 27, 2016 2:58 AM
  • Hi Anne,

    1. After the updates are installed the Windows Update screen says "A restart has been scheduled" and schedules it for 9:00am the following day. This morning I logged onto my Win10 laptop at 8:30am however the machine never prompted to restart at 9:00am. When I checked the Windows Update screen at around 10:00am it had once again scheduled the restart for 9:00am the following day. (See below for the update log file entries from 9:00am today.)

    2. This option is greyed-out as all updates are controlled by our WSUS GPO.

    3. No, this setting is disabled.

    Thanks, Hank

    2016/06/27 09:00:16.2415158 1000  13260 Agent           Adding timer:
    2016/06/27 09:00:16.2415328 1000  13260 Agent               Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2016-06-28 13:00:16, not idle-only, not network-only
    2016/06/27 09:00:16.4350032 1000  8224  DownloadManager PurgeExpiredFiles::Found 0 expired files to delete.
    2016/06/27 09:00:16.6351783 1000  8224  DownloadManager PurgeExpiredUpdates::Found 815 non expired updates.
    2016/06/27 09:00:16.7573306 1000  8224  DownloadManager PurgeExpiredUpdates::Found 0 expired updates.
    2016/06/27 09:01:01.7044776 1000  8096  Agent           Earliest future timer found:
    2016/06/27 09:01:01.7044946 1000  8096  Agent               Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2016-06-28 13:00:16, not idle-only, not network-only
    2016/06/27 09:01:02.7054443 1000  13260 Agent           Earliest future timer found:
    2016/06/27 09:01:02.7054546 1000  13260 Agent               Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2016-06-28 13:00:16, not idle-only, not network-only
    2016/06/27 09:01:02.7162694 1000  13260 Misc            CreateSessionStateChangeTrigger, TYPE:2, Enable:Yes
    2016/06/27 09:01:02.7162836 1000  13260 Misc            CreateSessionStateChangeTrigger, TYPE:4, Enable:Yes
    2016/06/27 09:01:02.7738493 1000  13260 Agent           Sending shutdown notification to client
    2016/06/27 09:01:02.7738643 1000  13260 Agent           Sending shutdown notification to client
    2016/06/27 09:01:02.7738749 1000  13260 Agent           Sending shutdown notification to client
    2016/06/27 09:01:02.7738852 1000  13260 Agent           Sending shutdown notification to client
    2016/06/27 09:01:02.8386718 1000  13260 Shared          * END * Service exit Exit code = 0x240001
     

    Hank Vare

    Monday, June 27, 2016 2:04 PM
  • Hi techrep43,

    Could you provide the detailed AU settings on win10, please provide the information of the registry keys locates in:

    HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Wednesday, June 29, 2016 9:23 AM
  • [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
    "IncludeRecommendedUpdates"=dword:00000001
    "AUPowerManagement"=dword:00000001
    "RebootRelaunchTimeoutEnabled"=dword:00000001
    "RebootRelaunchTimeout"=dword:00000006
    "RescheduleWaitTimeEnabled"=dword:00000001
    "RescheduleWaitTime"=dword:0000000a
    "DetectionFrequencyEnabled"=dword:00000001
    "DetectionFrequency"=dword:00000002
    "UseWUServer"=dword:00000001
    "NoAutoRebootWithLoggedOnUsers"=dword:00000000
    "NoAutoUpdate"=dword:00000000
    "AUOptions"=dword:00000004
    "ScheduledInstallDay"=dword:00000000
    "ScheduledInstallTime"=dword:00000009

    Hank Vare

    Wednesday, June 29, 2016 3:01 PM
  • Has any progress been made re: this issue? The Win10 clients in our environment still do not prompt the user to restart their laptops after updates have been pushed down. Meanwhile the Win7 clients continue to work properly by prompting the user to restart their machines. This is a headache requiring me to have to monitor each Win10 client and send email to the user to remind them to restart their machine. If I run a report on one of these machines by clicking "Updates needed" the updates all report a status of "Pending Reboot". 

    Hank Vare

    Tuesday, January 10, 2017 3:06 PM