boco wrote:Without any Office installed, this happens, too. None of those updates are applicable and can be installed, in this case.
Simplest way I've found searching and installing updates in XP fast (using POS hack but shouldn't matter).
1. Download and run Windows Update MiniTool.
2. Important: Check the box "Include superseded"!
3. Search for updates, should only be a few seconds.
4. Use the "Selected by Windows Update" box to mark the appropriate updates.
5. Install (third icon on the left), reboot when being asked.
This worked. But not quite as written. (Exactly as written, it had no effect.)
It worked this way:
1. Disable automatic updates in wuaucpl.cpl (but not the wuauserv service)
2. Download and run Windows Update MiniTool.
3. Place wsusscn2.cab from client\wsus alongside the MiniTool's exe.
4. Check the boxed "Include superseded" and "Offline mode".
5. Start the scan.
6. After a scan succeeds, to download and install the updates, uncheck "Offline mode" but keep "Include superseded" checked.
WSUS Offline's scan still hangs after this, at the same stage (see below).
So,
the workaround that WSUS Offline should use is to request superseded updates, and do that in Offline mode.Since it has its own list of superseded updates, it can filter them out anyway.
Additional info shows why
all other suggested solutions do not apply:----
The hang occurrs after detecting updates (this is shown by AU tracing; I would show a .reg for that but the form rejects every attachment extension that I tried). In Process Explorer, it has a prominent pattern of constant ~100% load on one core by svchost.exe hosting the AU, with roughly 50/50 user/kernel mode and no I/O activity.
I conjecture that it builds some kind of graph from the updates and traverses it to find and return leaves (non-superseded updates). Due to some incorrect or unexpected metadata, there appears a loop, and it starts walking along it in circles. When requesting superseded updates, this part of the algorithm is skipped. (this is hinted at by stack traces in Process Explorer with symbols configured. The execution never leaves wuaueng.dll and is endlessly comparing updates (a function named like "Update operator<")).
- Running in non-offline mode right away has no effect.
- Install IE8 updates (KB4018271 and KB4074736 (the latest POSReady cumulative update for now)): logs visibly change, but it instead starts to check for the same updates over and over. Deleting SoftwareDistribution has no effect.
- Install Office updates: on a fresh machine that has the issue, MiniTool lists none of the listed updates as required. After they were installed after a few rounds of prerequisites (except the updates for Office 2010, I do not have this product installed), the problem still persists.