Windows Update Restart Loop


  1. Posts : 4
    Windows 10
       #1

    Windows Update Restart Loop


    I work for a library university. We have a couple hundred computers running Windows 7 Enterprise 64 bit and over the past month or two we have seen a handful of computers that get caught in a loop of requiring a reboot to install updates. There seems to be nothing related to the computers that have this problem. Screenshots follow:





    After a restart we get the same thing. It doesn't even seem to even try and process any updates as it boots up and we cannot search for new updates at all when this happens.

    When we check the history of updates we see this weird one:


    I don't know why Windows 7 is trying to download and process the November upgrade for Windows 10. I thought that Enterprise versions of Windows were unable to upgrade to 10 via Windows Update. (We don't want to do this anyway. When we move to 10 we will make a new image at that point.) There is no way that I can find to delete or disable this update. We only ever see this problem once this has already failed and none of the other computers that don't have this problem ever see this update.

    On a number of these computers where we see this problem it seems to resolve itself. Within a couple of hours or the next day the computer is just fine and there is no listed record of this update even attempting to install. There are a handful of computers that did not just fix themselves. We re-image these and this fixes the problem, but I'd like to see if anyone else has seen this and possibly has an easier solution.

    1. System Update Readiness Tool (SURT)

    Ran System Update Readiness tool and rebooted. No change and no errors listed in CheckSUR.log or CheckSUR.persist.log files. I don't really know what I'm looking for in the CBS.log but I found this which might be relevant, not sure:

    2017-01-19 13:15:20, Info CBS Session: 30569096_1620829713 initialized by client WindowsUpdateAgent.
    2017-01-19 13:15:20, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]

    2. SFC Scan

    Ran System File Checker - no errors, nothing fixed

    3. Windows Update Error Codes

    This is the only error we get:

    Related to the update, but I mean we don't want this update anyway so...

    4. Log Collection

    Attached is the CBS.zip as requested.


    5. Other things I have tried

    a. Stopped wuauserv, deleted software distribution folder, and restarted wuauserv. This completely wiped the list of updates of course, but the computer is still requesting a restart infinitely and will not check for new updates.

    b. Data Execution Protection is already on. (another thread somewhere suggested turning this on so I checked up on it)

    c. Ran Microsoft Fixit 50202 for Resetting Update Components using the "aggressive mode" option. No change.
      My Computer


  2. Posts : 7,107
    W7 home premium 32bit/W7HP 64bit/w10 tp insider ring
       #2

    Hi Genogold.

    For the affected comps can you DISconnect them from the NET

    Reset windows updates to never

    REBOOT

    Reconnect to the net
    RESET WondowsUpdate to LET ME CHOOSE
    give it 10/15 minutes to run thru the operation

    IT should then give you a tick screen
    The W10 update KBXXXXXX will appear on it
    On the update>> description << click on it will give you a smaller box hover on the Hide option press enter.
    Until MS changes the KB number it should not re-appear.

    comment
    im assuming these problem comps are connected to a server, are thier GPO's correct or were they added to the the domain after the ignore W10 command was written/sent.


    First thoughts before looking at log
    Roy
      My Computer


  3. Posts : 7,107
    W7 home premium 32bit/W7HP 64bit/w10 tp insider ring
       #3

    Hi Genogold,

    Well CBS is clean, would you mind posting the log from here
    C >> Windows >> WindowsUpdate

    and just to check that its running enterprise, copy/paste the output please
    http://go.microsoft.com/fwlink/?LinkID=52012

    No sensitive data is shown by it please post in its entirety

    Roy
      My Computer


  4. Posts : 4
    Windows 10
    Thread Starter
       #4

    Hey thanks for the reply! Here's what I got:

    torchwood said:
    Hi Genogold.

    For the affected comps can you DISconnect them from the NET

    Reset windows updates to never

    REBOOT

    Reconnect to the net
    RESET WondowsUpdate to LET ME CHOOSE
    give it 10/15 minutes to run thru the operation

    IT should then give you a tick screen
    The W10 update KBXXXXXX will appear on it
    On the update>> description << click on it will give you a smaller box hover on the Hide option press enter.
    Until MS changes the KB number it should not re-appear.

    comment
    im assuming these problem comps are connected to a server, are thier GPO's correct or were they added to the the domain after the ignore W10 command was written/sent.


    First thoughts before looking at log
    Roy
    I did this. It never checked for updates or changed from the screen stating it needed a restart that I saw.

    torchwood said:
    Hi Genogold,

    Well CBS is clean, would you mind posting the log from here
    C >> Windows >> WindowsUpdate

    and just to check that its running enterprise, copy/paste the output please
    http://go.microsoft.com/fwlink/?LinkID=52012

    No sensitive data is shown by it please post in its entirety

    Roy
    I have attached these files.
    Windows Update Restart Loop Attached Files
      My Computer


  5. Posts : 7,107
    W7 home premium 32bit/W7HP 64bit/w10 tp insider ring
       #5

    Hi Genogold,

    Mgadiags fine.

    Quick first look at log, will do more in depth shortly.

    I see that compatel is instigating the W10 update,
    (if i remember rightly 3rd party?)
    MS >>> Compatel (chooses updates) >>> you
    If this is the case then you will have to get them to prune the update out.


    Roy
      My Computer


  6. Posts : 4
    Windows 10
    Thread Starter
       #6

    torchwood said:
    Hi Genogold,

    Mgadiags fine.

    Quick first look at log, will do more in depth shortly.

    I see that compatel is instigating the W10 update,
    (if i remember rightly 3rd party?)
    MS >>> Compatel (chooses updates) >>> you
    If this is the case then you will have to get them to prune the update out.


    Roy
    Thank you again so much for looking through these logs. Just for my education, can you let me know what parts of this log indicate this?
      My Computer


  7. Posts : 4
    Windows 10
    Thread Starter
       #7

    FYI, this is kind of dumb but...

    We deleted the following registry key that prompts for reboot and rebooted:

    -HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired

    After that we could find updates and that update was just not listed there at all.
      My Computer


  8. Posts : 7,107
    W7 home premium 32bit/W7HP 64bit/w10 tp insider ring
       #8

    Hi Geno.,
    here you go
    ** START ** Agent: Finding updates [CallerId = <<PROCESS>>: CompatTelRunner.exe]
    2017-01-19 10:02:22:471 1060 fa8 Agent *********
    2017-01-19 10:02:22:471 1060 fa8 Agent * Online = Yes; Ignore download priority = No
    2017-01-19 10:02:22:471 1060 fa8 Agent * Criteria = "(CategoryIDs contains '405706ED-F1D7-47EA-91E1-EB8860039715' AND Type='Driver' AND VersionOverride='10.0.10586.2.0.0.256.1') OR (CategoryIDs contains '34F268B4-7E2D-40E1-8966-8BB6EA3DAD27' AND Type='Driver' AND VersionOverride='10.0.10586.2.0.0.256.1') OR (CategoryIDs contains '05EEBF61-148B-43CF-80DA-1C99AB0B8699' AND Type='Driver' AND VersionOverride='10.0.10586.2.0.0.256.1')"
    2017-01-19 10:02:22:471 1060 fa8 Agent * ServiceID = {51DDABC9-705D-4E40-B14C-3EA992A48843} Third party service
    2017-01-19 10:02:22:471 1060 fa8 Agent * Search Scope = {Machine}
    2017-01-19 10:02:22:471 5564 8f0 COMAPI <<-- SUBMITTED -- COMAPI: Search [ClientId = ]


    Roy
      My Computer


  9. Posts : 7,107
    W7 home premium 32bit/W7HP 64bit/w10 tp insider ring
       #9

    Hi Geno

    THATS NOT a good idea,
    what youv'e now done is KILL any update session that requires a reboot to complete.

    I provided the info for compatel

    SO WHERE'S my answer
    is it a 3rd party controlled WU session


    Roy
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 08:54.
Find Us