DoUpdate.cmd appearently stuck after 12 hours

DoUpdate.cmd appearently stuck after 12 hours

Postby Luigi12 » 07.11.2017, 11:48

Using WSUS Offline Update (v. 9.2.3) on Windows Vista 32b,
I successfully ran .\UpdateGenerator.exe,
then I ran UpdateInstaller.exe from .\client directory.

after about 12 hours the update process is still in the "Listing ids of missing updates" stage.

With sysinternals ProcExp I found the CScript.exe process launched by "DoUpdate.cmd" to execute the script "ListMissingUpdateIds.vbs",
according to the image shown in ProcExp: "C:\Windows\System32\cscript.exe //Nologo //B //E:vbs ListMissingUpdateIds.vbs"

All the threads of this process are in state Wait:..

And this is the output in the DoUpdate window:

Code: Select all
Starting WSUS Offline Update (v. 9.2.3) at 23.25.37,59...
Checking user's privileges...
Determining system's properties...
Determining DirectX main version...
Determining Windows licensing info...
Found Microsoft Windows version: 6.0.6002.19636 (w60 x86 ita sp2)
Found Microsoft Windows Software Licensing Management Tool info...
Nome: Windows(TM) Vista, HomePremium edition
Descrizione: Windows Operating System - Vista, OEM_SLP channel
Codice "Product Key" parziale: WQD8Q
Stato licenza: concesso in licenza
Checking medium content...
Medium build date: 06/11/2017
Medium supports Microsoft Windows (w60 x86 glb).
Checking Windows Service Pack version...
Checking Windows Update Agent version...
Checking Windows Installer version...
Checking Windows Script Host version...
Checking Internet Explorer version...
Checking Trusted Root Certificates' version...
Warning: File ..\win\glb\rootsupd.exe not found.
Checking Revoked Root Certificates' version...
Warning: File ..\win\glb\rvkroots.exe not found.
Checking DirectX version...
Installing most recent DirectX End-User Runtime...
Installing ..\win\glb\directx_Jun2010_redist.exe...
Checking Remote Desktop Client version...
Installing most recent Remote Desktop Client...
Installing update 1 of 1...
Verifying integrity of ..\w60\glb\Windows6.0-KB969084-x86.msu...
hashdeep.exe: Audit passed
Installing ..\w60\glb\Windows6.0-KB969084-x86.msu...
Checking Windows Defender installation state...
Checking state of service 'Windows Update'...
Verifying integrity of Windows Update catalog file...
hashdeep.exe: Audit passed
23.31.55,27 - Listing ids of missing updates (please be patient, this will take a while)...


Any hint would be appreciated

Luigi12

Adding a question: how long should wait before aborting the installation ?
Last edited by Luigi12 on 07.11.2017, 19:05, edited 2 times in total.
Luigi12
 

Re: DoUpdate.cmd appearently stuck after 12 hours

Postby Dalai » 07.11.2017, 15:00

Hello Luigi, and welcome to the forums :),

This is "normal". Take a look at my site http://wu.krelay.de/en/ for more information, why this is happening and how you can fix it. Also, is this the first run of UpdateInstaller you made on this system? Could you please post the contents of C:\Windows\wsusofflineupdate.log (in [CODE] [/ CODE] tags)? I'm primarily asking to find out which scan prerequisite updates are missing on your system.

Regards
Dalai
Dalai
 
Posts: 1021
Joined: 12.07.2016, 21:00

Re: DoUpdate.cmd appearently stuck after 12 hours

Postby labview » 02.01.2018, 03:33

I have the same problem with Windows Vista x64 Ultimate.
I did a new installation of vista sp2 in Virtualbox and Wsus stops at "Listing ids of missing updates (please be patient, this will take a while)", this does not happen with W7 and W8.1.
labview
 
Posts: 2
Joined: 02.01.2018, 03:21

Re: DoUpdate.cmd appearently stuck after 12 hours

Postby Dalai » 02.01.2018, 14:31

@labview: Take a look at http://wu.krelay.de/en/Vista.htm and install the updates listed there (if missing). Then try WSUS Offline again. Note that you'll have to wait either way, it's just a matter of how long; it will get its search done eventually.

Regards
Dalai
Dalai
 
Posts: 1021
Joined: 12.07.2016, 21:00

Re: DoUpdate.cmd appearently stuck after 12 hours

Postby aker » 03.01.2018, 00:58

If you want to install the updates manually, I could provide you a full list of updates & required reboots. But that one will force you to manually install about 250 updates.
Wer Rechtschreibfehler findet, darf sie behalten oder an den Meistbietenden versteigern. / Everybody finding a misspelling is allowed to keep or sell it.
aker
aker
 
Posts: 3665
Joined: 02.03.2011, 15:32

Re: DoUpdate.cmd appearently stuck after 12 hours

Postby labview » 04.01.2018, 02:19

thanks for reply,
I tried this old package and it works very well and fast: http://www.chip.de/downloads/CHIP-Windo ... 14507.html
After I used the latest version 9.2.3 for the latest updates, in this way Wsus does not wait indefinitely.
labview
 
Posts: 2
Joined: 02.01.2018, 03:21

Re: DoUpdate.cmd appearently stuck after 12 hours

Postby Izibia » 17.09.2019, 09:39

The problem of "Listing ids of missing updates (please be patient ..." hapenned to me with Win7

Dalai wrote:This is "normal". Take a look at my site http://wu.krelay.de/en/ for more information, why this is happening and how you can fix it.

I tried this fix, but it didn't help, maybe because
- I wanted to avoid the rollups
- I wasn't able to run updates via WUSA
BTW, why the install via WUSA is required?

The partial fix (Support for SHA-2 and Servicing Stack Update, both applied without WUSA) helped to solve another problem: without the partial fix updates B4512486 and KB4515566 weren't installed by WSUSOU.
It looks it conforms this article: https://borncity.com/win/2019/08/14/win ... x80092004/

Finally I got rid of "Listing ids of missing updates" this way:
1) ctrl-C
2) Terminate batch job (Y/N)? n
3) this caused the batch to continue to work (I don't understand why? Previous line should cause only a batch pause?) EDIT: I tested it and it looks ctrl-C always stops the execution of the current command (line) of the batch.
4) Finally I ran UpdateInstaller again, and it went through the "Listing ids of missing updates" point
Izibia
 
Posts: 22
Joined: 30.08.2014, 22:24

Re: DoUpdate.cmd appearently stuck after 12 hours

Postby aker » 17.09.2019, 22:40

If you cancel the process and restart shortly it afterwards, the dynamic update search will fail as WUA isn't able to do more than one task at the same time.
Means: you won't get patched as the dynamic update search fails.

Regarding the "partial fix":
if you decide to skip wsusou's preparations, it also won't install the SHA2-support, which will cause some updates not to install.

If you want to get all updates, you have to wait.
If you want to avoid the rollups, you can try to update the Windows Update Agent using KB4015546 (2017-04 SecOnly update), which also should update it to a version, which fixes the long search issue (if combined with the most recent Servicing Stack).
Wer Rechtschreibfehler findet, darf sie behalten oder an den Meistbietenden versteigern. / Everybody finding a misspelling is allowed to keep or sell it.
aker
aker
 
Posts: 3665
Joined: 02.03.2011, 15:32

Re: DoUpdate.cmd appearently stuck after 12 hours

Postby Izibia » 17.09.2019, 23:19

aker, thank you for the assistance.

aker wrote:If you cancel the process and restart shortly it afterwards

I didn't cancel the process, I only cancelled the line with "Listing ids of missing updates (please be patient ...". Then updates continued to be installed. Total 57 updates were installed in this very first run of UpdateInstaller, including windows6.1-kb4015546-x64_38eb1331847d3fb193ad26a6d1b6e9d525d8014a.cab

In next run(s) cca 103 updates were installed.

aker wrote:Regarding the "partial fix":
if you decide to skip wsusou's preparations ...

what do you mean by skipping wsusou's preparations?
Izibia
 
Posts: 22
Joined: 30.08.2014, 22:24

Re: DoUpdate.cmd appearently stuck after 12 hours

Postby boco » 18.09.2019, 09:58

WOU will statically install some prerequisites, for solving the "long search problem", latest Service stack, SHA2 update etc. If that process is interrupted or aborted, not all dynamic updates will be installed*.

*Updates often need other updates to be installed first. If these prereq's are missing, WUA will not report the updates as being required (status is "not applicable". The same with Windows Update - some updates will not be offered to you, until you have the prerequisites in place.

Possible prerequisites:
- Other updates, usually Service Packs, platform updates, Service stacks, and the SHA2 update for legacy OS.
- A Registry key, we had such a case during the Spectre/Meltdown disaster.
- Status of the user account, if you are member of any Windows 10 Insider rings, you will get different updates offered. In Windows 10, it matters if you actively search for updates ("seekers") or not.
- Hardware conditions, like in the "Clover Trail" case, where machines using that platform are exempt from the Windows 10 1607 EOL and receive updates until 2023.
Microsoft update catalog: http://catalog.update.microsoft.com/v7/site/
Windows Install media download: https://support.microsoft.com/en-us/help/15088/windows-create-installation-media
boco
 
Posts: 2320
Joined: 24.11.2009, 17:00
Location: Germany

Next

Return to Installation / Updating

Who is online

Users browsing this forum: No registered users and 19 guests