Page 2 of 2

Re: wget64.exe appcrash when run UpdateGenerator

PostPosted: 13.06.2018, 12:13
by eric99811
And i use WSUS offline update 11.1.1 is normal

But 11.2, 11.3 and 11.4 will show the error message

Re: wget64.exe appcrash when run UpdateGenerator

PostPosted: 13.06.2018, 18:05
by boco
These tools are essential and downloaded from the WOU website. WGet crashes so they can't be downloaded. The error message is a red herring as it is only a result from the core problem (if WGet worked it wouldn't occur).

Does only WGet64.exe crash, or the 32bit version WGet.exe, too?

Re: wget64.exe appcrash when run UpdateGenerator

PostPosted: 13.06.2018, 19:58
by aker
Where do you store wsusou?
Could you try a simple path such as "C:\wsusoffline"?

Urgent seek your support!

PostPosted: 14.06.2018, 08:54
by tommylau
Dear Sir/ Madam,

We can not use the latest version .
Please see the below logs:
Code: Select all
14/06/2018 週四 15:55:30.52 - Info: Starting WSUS Offline Update download (v. 11.4) for w61 glb
14/06/2018 週四 15:55:30.52 - Info: Option /includedotnet detected
14/06/2018 週四 15:55:30.54 - Info: Option /verify detected
14/06/2018 週四 15:55:30.55 - Info: Option /exitonerror detected
14/06/2018 週四 15:55:31.05 - Info: Set time zone to LOC-8:00
14/06/2018 週四 15:55:31.32 - Info: Preserved custom language and architecture additions and removals


Thanks.
Tommy

Re: wget64.exe appcrash when run UpdateGenerator

PostPosted: 14.06.2018, 09:03
by tommylau
eric99811 wrote:UPDATE: Error text

13/06/2018 週三 19:09:57.13 - Info: Starting WSUS Offline Update download (v. 11.4) for w61 glb
13/06/2018 週三 19:09:57.14 - Info: Option /includedotnet detected
13/06/2018 週三 19:09:57.16 - Info: Option /verify detected
13/06/2018 週三 19:09:57.19 - Info: Option /exitonerror detected
13/06/2018 週三 19:09:57.38 - Info: Set time zone to LOC-8:00
13/06/2018 週三 19:09:57.54 - Info: Preserved custom language and architecture additions and removals
13/06/2018 週三 19:09:59.72 - Info: Updated static and exclude definitions for download and update
13/06/2018 週三 19:09:59.72 - Info: Restored custom language and architecture additions and removals
13/06/2018 週三 19:10:00.19 - Info: Downloaded/validated mkisofs tool
13/06/2018 週三 19:10:00.71 - Info: Downloaded Sysinternals' tools Autologon, Sigcheck and Streams
13/06/2018 週三 19:10:01.85 - Info: Downloaded/validated most recent Windows Update catalog file
13/06/2018 週三 19:10:01.86 - Error: Sysinternals' digital file signature verification tool ..\bin\sigcheck64.exe not found



I have a some problem!!, i just can use the Jan2018 version.. another versions are fail to use UpdateGenerator.
There is a error message when i start to generate.
Please help!!! thx

Re: wget64.exe appcrash when run UpdateGenerator

PostPosted: 14.06.2018, 15:38
by Dalai
@tommylau:
Please try the following: Open a CMD window by Shift+right-clicking on your WSUS Offline directory and selecting "Open command prompt here" (or similar) and type (or paste) the following command line:
Code: Select all
bin\wget.exe --server-response --spider --progress=bar:noscroll "http://download.windowsupdate.com/microsoftupdate/v6/wsusscan/wsusscn2.cab"
Does wget.exe crash? If not, repeat the command without the --spider option and let it download the file and see if it crashes then.

Also, please tell us which Windows version (and "bitness") exactly you're using to download files.

Until this issue is solved, please use the older wget.exe included with WSUS Offline Update 11.1.1 to properly download files - but don't use this for the test case above!

[mod-note] I merged the new/separate topic with this thread because it's probably the same issue. [/mod-note]

Regards
Dalai

Re: wget64.exe appcrash when run UpdateGenerator

PostPosted: 15.06.2018, 10:35
by tommylau
i have tried the above command in CMD, it will prompt the: does't find the location.
Any other solution ?
BR,
TommyLau

Re: wget64.exe appcrash when run UpdateGenerator

PostPosted: 15.06.2018, 15:00
by Dalai
tommylau wrote:i have tried the above command in CMD, it will prompt the: does't find the location.

Then you launched the CMD in the wrong path. The CMD must have the current directory set to the root of your WSUS Offline directory. Example: If it's located in c:\wsusoffline, Shift+right-click on that directory and select "Open command prompt here" and the above command will work.

Regards
Dalai