Installer hangs at Listing ids of missing updates...

[Gerby]

Hello dm871,

Yes, installing a newer version of the Windows Update Client is one of the possibilities to get back to search times that can be beared (both fixes you mentioned are the Windows Update Client, even if KB3102810 doesn't name it).

WSUS Offline Update actually takes care of this and installs so-called prerequisite updates before starting the full update run. We are searching each month (or even continuously) for new prerequisites, because Microsoft scrambles the update system from patch day to patch day in a way that previous prerequisites may not be sufficient anymore.

Greetz
Gerby

[Howlingwolf]

Here's an issue which might be connected to this.

Installing the Remote Desktop Client updates before the Windows Update prerequisites on a clean install of Windows 7 SP1 causes KB3172605 to fail.

Code: Select all

Windows update  could not be installed because of error 2149842967 "" (Command line: "C:\Windows\System32\wusa.exe  ..\w61-x64\glb\windows6.1-kb3172605-x64_2bb9bc55f347eee34b1454b50c436eb6fd9301fc.msu /quiet /norestart")


This shows in the windows event log but isn't being picked up by wsusoffline which continues as usual after restarting and hangs at the listing ids stage.

Installing them after installing the scan prerequisites and restarting appears to work without errors.

I've tested it with as many combinations of options as I could over the past week and it consistently fails in this scenario.

Windows 7 SP1 (x64 & x86)
VirtualBox 5.1.6 (Win32 host) & 5.1.8 (Fedora 22 x64 host)
WSUSOffline 10.8
ISO Build Date 25/10/2016

[aker]

Just a note:
2149842967 = 0x80240017 = WU_E_NOT_APPLICABLE (Operation was not performed because there are no applicable updates.)

[Howlingwolf]

The Microsoft documentation is misleading.

0x80240017 is a 'generic' error code often returned by windows update when it can't determine what the actual error is.

In this case it's almost certainly a 'staging conflict' between one of the remote desktop client updates and KB3172605, i.e. the same file being updated by both.

The most obvious way of fixing this would be to insert yet another restart between the remote desktop client updates and scan prerequisites, but I'll leave that to someone who knows more about the internal workings of wsusoffline.

[aker]

Could you provide the files C:\Windows\Logs\CBS\CBS.log and C:\Windows\Logs\DISM\DISM.log of a freshly installed system, which has the error?
[Please clear the 2 folders, then run the installation and post the files then (just to keep the logs as short as possible and prevent misinterpretations)]

[ReedRichards]

I am trying to update a computer running Windows Vista (32 bit) that was reset to factory settings. The installer has been stuck at 'Listing IDs of missing updates..." for over 10 hours now. I downloaded WSUS Offline on 4th November and the prerequisite updates it installed were 3191203, 3168965, 3164033, 3145739, 3109094 & 3078601 but I guess there is something wrong or missing. Is there a way out of this impasse?

[dbyrne]

RE: "Installing the Remote Desktop Client updates before the Windows Update prerequisites on a clean install of Windows 7 SP1 causes KB3172605 to fail." I think I'm also seeing this problem, and I've not been able to find any way to install KB3172605, or indeed the KB3125574 'Convenience Rollup'.

Question: If the KB3172605 pre-requisite is failing is this a fatal error and should I abandon trying to use WSUSo, or does it simply mean that I need to wait longer? I've tried several times on a fast Dell M4700 laptop workstation with core-i7 cpu and plenty of RAM (Win7-x64 SP1), but after 5-6 hours it's still stuck at 'Listing ids'.

FYI, last night it managed to complete a regular Windows Update cycle which showed 106 updates, but 18 of them failed and now still can't be installed after a couple of cycles. Despite the fact that I hate the Windows 10 GUI I'm almost tempted to switch (which is presumably MS's plan!), but I need to maintain some customer applications which require Win 7.

Thanks for any comments or advice guys.

[aker]

@ReedRichards
Sorry to say, but we can't fix this ATM. Even with all prereqs installed it takes that long. We currently don't know, which updates have to be installed to fix this issue.

@dbyrne
The failed installation of KB3172605 just means, that it will take longer (the last time I tried (2016-09) it took about 10 hours).

[LoominousFish]

I'm on Vista x86 and I resolved the issue of Windows Update hanging by manually installing the KB3198234 update. After that WU worked again and 20 minutes later all the November updates were downloaded and installed. I didn't even have to use WSUS Offline. There's more info in this thread: http://answers.microsoft.com/en-us/wind ... a480b95dd3

[harry]

KB3198234 supersedes (among others) KB3168965, which is already listed in .\client\static\StaticUpdateIds-wupre-w60.txt.