none
Unexpected automatic restart behaviour after installation of Update KB2952664 Rev.200 from 06.06.2017 RRS feed

  • Question

  • Hello,

    in our company we use Windows 7 Clients in ActiveDirectory 2008R2, a WSUS and GPOs for Windows Update active.

    Updates are automatically approved for a group of computers for testing.  These Computers are set with a GPO that does not install updates automatically but informs the user about new updates . The user decides the installation time. Among other settings we also set with GPO that disables an automatic reboot after update installation: "No auto-restart with logged on users for scheduled automatic updates installations" enabled.

    GPO Result Check prooves, the policies are still appliead as expected - and this has always worked as expected.

    The GPO has not been changed for over a year.

    With KB2952664 Rev.200(!!) reissued by Microsoft on 06.06.2017 and installed today we experienced an unexpected forced reboot within 15 minutes for all affected computers of the above mentioned group. The shown image (German text) popped up and it was not possible to stop the reboot process.

    08.06.2017 10:02:28    WindowsUpdateClient    22
    Restart required: To complete the installation of the following updates, the computer will be restarted within 15 minutes: Update for Windows 7 for x64-Systems (KB2952664)

    Today, our clients are rebooting once again. This time after installation of KB3203460.

    I copied this thread from customer forums: https://answers.microsoft.com/en-us/windows/forum/windows_7-update/unexpected-automatic-restart-behaviour-after/f27dc43f-5751-48c8-9e7f-ba52a5e142cc

    unexpected reboot windows update

    Friday, June 16, 2017 8:28 AM

Answers

  • Maybe I found the reason:

    the Windows Update GPO policy was not changed as described above.

    But what was changed was a setting in WSUS that seems to overwrite the GPO setting somehow:
    Automatic approval of updates was changed from somewhat to a deadline installation. That caused the installation at 10:00 two days after the update has been approved.

    Found a hint here:

    https://social.technet.microsoft.com/Forums/en-US/bd5027b7-8de7-4de8-b9c4-85fbc73ad839/postpone-button-disabled-grayed-out?forum=winserverwsus&prof=required

    • Edited by L_Herzog Friday, June 16, 2017 3:37 PM
    • Proposed as answer by Tony_TaoModerator Monday, June 19, 2017 1:55 AM
    • Marked as answer by L_Herzog Sunday, July 2, 2017 7:55 PM
    Friday, June 16, 2017 3:35 PM

All replies

  • Maybe I found the reason:

    the Windows Update GPO policy was not changed as described above.

    But what was changed was a setting in WSUS that seems to overwrite the GPO setting somehow:
    Automatic approval of updates was changed from somewhat to a deadline installation. That caused the installation at 10:00 two days after the update has been approved.

    Found a hint here:

    https://social.technet.microsoft.com/Forums/en-US/bd5027b7-8de7-4de8-b9c4-85fbc73ad839/postpone-button-disabled-grayed-out?forum=winserverwsus&prof=required

    • Edited by L_Herzog Friday, June 16, 2017 3:37 PM
    • Proposed as answer by Tony_TaoModerator Monday, June 19, 2017 1:55 AM
    • Marked as answer by L_Herzog Sunday, July 2, 2017 7:55 PM
    Friday, June 16, 2017 3:35 PM
  • I appreciate your answer. Thanks for sharing, I will introduce this experience to other forum users who face the same condition. Please mark the reply as an answer if you find it is helpful:)


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


    Monday, June 19, 2017 1:55 AM
    Moderator