ERROR: Download failure for dotnet x64-glb.

[sgtwtf]

Started getting this error a few days ago when trying to pull updates. Tried on a few different systems on different networks and no change. Love your work and wanted to make sure you were aware. I search on the forums and was not able to find anything regarding this. Tried previous release as well same issue.

[Time Stamp] - Determining dynamic update urls for dotnet x64-glb...

ERROR: Download failure for dotnet x64-glb.

[aker]

Do you have the last about 5-10 lines of .\log\download.log?
Could you also take a screenshot of the cmd-window, when it reports the error.

[sgtwtf]

Log file:
Sun 11/20/2016 12:07:10.02 - Info: Starting WSUS Offline Update download (v. 10.8) for w61-x64 glb
Sun 11/20/2016 12:07:10.02 - Info: Option /includedotnet detected
Sun 11/20/2016 12:07:10.03 - Info: Option /exitonerror detected
Sun 11/20/2016 12:07:10.12 - Info: Set time zone to LOC8:00
Sun 11/20/2016 12:07:14.61 - Info: Updated static download and update definitions
Sun 11/20/2016 12:07:15.04 - Info: Downloaded/validated mkisofs tool
Sun 11/20/2016 12:07:29.98 - Info: Downloaded/validated most recent Windows Update catalog file
Sun 11/20/2016 12:07:33.57 - Info: Downloaded/validated installation files for .NET Frameworks 3.5 SP1 and 4.x
Sun 11/20/2016 12:07:34.70 - Info: Determined superseded updates
Sun 11/20/2016 12:07:34.71 - Info: Determined static update urls for dotnet x64-glb
Sun 11/20/2016 12:07:34.75 - Error: Download failure for dotnet x64-glb

See attachment for screen grab.

Capture.PNG

Screen Grab

(22.36 KiB) Not downloaded yet

[hbuhrmester]

Most often, errors during the determination of superseded updates are caused be a disabled Windows Script Host (WSH). The script DownloadUpdates.cmd needs it to run several VBScripts for XSLT transformations, to extract information from the file package.xml.

Unfortunately, the UpdateGenerator.exe does not check, that the Windows Script Host is running.

The UpdateInstaller.exe, however, checks this precondition, so you could make a simple test:

• Start the UpdateInstaller.exe in the client directory.
• If it starts normally, quit it again without making any selections, since you don't actually want to install anything at this point.
• If it displays any error message, report it here and try to fix it. The WSH is usually running. It may get disabled by some Registry hacks or Windows Tuning Utilities. If you disabled it somehow, you will have to find that out yourself.

The error happens when Cscript.exe is called, but Cscript.exe fails silently, because it uses the batch option /B. This option suppresses all messages:

/B
Specifies batch mode, which does not display alerts, scripting errors, or input prompts.

https://technet.microsoft.com/en-us/lib ... 20171.aspx

Therefore, it is somewhat typical, that there are error messages before and after the calls of Cscript.exe, with Cscript itself keeping silent.

If the reason for the errors is still not clear, you may get more accurate error messages, if you remove the option "//B" from all calls of Cscript.exe.

Change:

Code: Select all

%CSCRIPT_PATH% //Nologo //B //E:vbs

to:

Code: Select all

%CSCRIPT_PATH% //Nologo //E:vbs

[sgtwtf]

So this is a fresh install on Win 7 pro 64 bit from Official ISO from Microsoft Volume license center so no hacked/tweaked system settings (yet )

The Updater loaded without issue. I tested the Scripting Host by running a VB Script that just outputted some text and that also worked. The updater loaded the patch data from the 16th which was the last successful update.

[aker]

What about the rights of %temp%. Are there (for a reason I can't explain) any restrictions?

[TomDel]

I got a download failure on this product too, using aria2c so it's a bit more verbose. It looks like

Code: Select all

http://download.microsoft.com/download/E/9/B/E9B7D680-7AF0-4922-8813-5561626639A5/NDP46-KB3136000-x86.exe

has been replaced with

Code: Select all

http://download.microsoft.com/download/E/9/B/E9B7D680-7AF0-4922-8813-5561626639A5/NDP46-KB3136000-v2-x86.exe

.

[hbuhrmester]

An unusual installation path can also cause problems with the script DownloadUpdates.cmd or Cscript.exe in particular.

Scripts can be broken by overly long installation paths or by unusual characters in the path. Cscript seems to be more sensible to such problems, because it runs in a different environment: Sometimes Cscript doesn't seem to find the current working directory or files within it, while the rest of the script runs fine.


Both UpdateGenerator.exe and UpdateInstaller.exe check for common problems with the installation path. They both ensure, that:

• the path is no longer than 192 characters
• the path does not contain the characters !%&()^+,;=

But there may be some corner cases, which are not easily detected.


So, what is the installation path to the wsusoffline directory?

Does it reside on a network drive?

WSUS Offline Update does run from a network drive, but you should assign it a drive letter, not just mount it as a network resource with UNC notation. For the installation part, network drives must be mounted twice, once as a regular user and once with Administrator privileges.

Is WSUS Offline Update running in a virtual machine?

I didn't try that, but it should work fine. But some users create fancy configurations with some parts of WSUS Offline Update inside the virtual machine, and some parts outside. Such configurations may not work.


Problems with the installation part can be avoided by copying the directory wsusoffline directly onto the C: drive, so that the path to the UpdateGenerator is:

Code: Select all

C:\wsusoffline\UpdateGenerator.exe

Then run it from that directory.

[hbuhrmester]

I got a download failure on this product too, using aria2c so it's a bit more verbose. It looks like

Code: Select all

http://download.microsoft.com/download/E/9/B/E9B7D680-7AF0-4922-8813-5561626639A5/NDP46-KB3136000-x86.exe

has been replaced with

Code: Select all

http://download.microsoft.com/download/E/9/B/E9B7D680-7AF0-4922-8813-5561626639A5/NDP46-KB3136000-v2-x86.exe

.

Actually, the update kb3136000 is downloaded as:

Code: Select all

wsusoffline/client/dotnet/x86-glb/ndp46-kb3136000-v2-x86_da08d435925193b28f5c674dc1ac275d60f47c56.exe

wsusoffline/client/dotnet/x64-glb/ndp46-kb3136000-v2-x64_133bd44462f529c6ccf3c5243c9102768241d71b.exe

These downloads are dynamically created, which means, that the URLs are extracted from the WSUS catalog file wsusscn2.cab. As far as I can tell, they were never statically defined in WSUS Offline Update.

But, if you use the custom download lists from cababs, you may sometimes find broken links. In this case, they are in the files:

Code: Select all

wsusoffline/static/custom/StaticDownloadLinks-w60-x86-glb.txt
wsusoffline/static/custom/StaticDownloadLinks-w60-x64-glb.txt

Since the update is already downloaded using dynamic links, you can safely delete these broken links.

[sgtwtf]

since update the issue is resolved. Just wanted to close the loop on this post.