[solved] Download failure for dotnet x86-glb

[IslandBoy77]

Hi Torsten

That's a good idea - hadn't thought about that, although it would be odd. Anyway, I'm still on Vista Business 32-bit with SP2 (just can't be bothered making the effort to go to W7 since it's such a huge job of format / reload etc, and Vista's running good), this is the result I got:
Microsoft Windows [Version 6.0.6002]
14/04/2008 04:42 a.m. 506,368 msxml.dll
14/04/2008 04:42 a.m. 701,440 msxml2.dll
01/03/2006 12:00 a.m. 37,916 msxml2r.dll
06/06/2012 04:47 a.m. 1,248,768 msxml3.dll
14/09/2010 04:38 p.m. 24,576 msxml3a.dll
02/11/2006 09:41 p.m. 2,048 msxml3r.dll
25/06/2012 04:04 p.m. 1,394,248 msxml4.dll
02/06/2009 12:39 a.m. 44,544 msxml4a.dll
22/01/2009 03:12 a.m. 88,904 msxml4r.dll
06/06/2012 04:47 a.m. 1,401,856 msxml6.dll
02/11/2006 09:41 p.m. 2,048 msxml6r.dll
01/03/2006 12:00 a.m. 26,624 msxmlr.dll

So looks like I've got both (which I thought I would).

In reply to boco - if I put the ./client directory somewhere "safe", delete the WSUS folder, download a totally fresh copy of the WSUS installer & set it up as per usual, then copy the ./client folder back, does that sound like a feasible / likely fix (that won't involve a 13GB re-download)?

Thanks

[boco]

./client/ directory except the following subdirectories:

bin - binaries, usually populated by WSUSOU as needed
cmd - batch files and scripts for installing updates, they come with the WSUSOU package
md - contains the hash files, copying them across to a new installation will give trouble as there may be discrepancies
opt - option lists, come with package
static - static definitions, come with package; only copy custom files you created, if any

[IslandBoy77]

Hi Boco

I copied only the directories from the Client folder that you didn't specify. Still no go after downloading a totally clean version of WSUS 7.4.2.

Error in CMD window is:

Code: Select all

--2012-08-25 10:21:32--  http://download.sysinternals.com/files/Sigcheck.zip
Warning: Integrity database ..\client\md\hashes-dotnet-x86-glb.txt not found.
Determining static update urls for dotnet x86-glb...
Extracting Microsoft's update catalog file package.xml...
10:21:36.50 - Determining superseded updates (please be patient, this will take a while)...

ERROR: Download failure for dotnet x86-glb.

The error log is also full of warnings:

Code: Select all

Sat 25/08/2012 10:21:32.42 - Info: Downloaded Sysinternals' tools Autologon, Sigcheck and Streams
Sat 25/08/2012 10:21:32.47 - Warning: Integrity database ..\client\md\hashes-wsus.txt not found
Sat 25/08/2012 10:21:33.70 - Info: Downloaded/validated most recent Windows Update Agent installation and catalog files
Sat 25/08/2012 10:21:33.70 - Info: Verified digital file signatures of Windows Update Agent installation and catalog files
Sat 25/08/2012 10:21:33.70 - Info: Created integrity database for Windows Update Agent installation and catalog files
Sat 25/08/2012 10:21:34.78 - Warning: Integrity database ..\client\md\hashes-dotnet.txt not found
Sat 25/08/2012 10:21:35.90 - Info: Downloaded/validated installation files for .NET Frameworks 3.5 SP1 and 4
Sat 25/08/2012 10:21:35.90 - Warning: Integrity database ..\client\md\hashes-dotnet-x86-glb.txt not found
Sat 25/08/2012 10:21:35.92 - Info: Determined static update urls for dotnet x86-glb
Sat 25/08/2012 10:21:36.53 - Error: Download failure for dotnet x86-glb

When I copied across the contents of the MD folder, things progressed better, but I still end up with failure:

Code: Select all

Sat 25/08/2012 10:27:45.15 - Info: Verified integrity of Windows Update Agent installation and catalog files
Sat 25/08/2012 10:27:46.14 - Info: Downloaded/validated most recent Windows Update Agent installation and catalog files
Sat 25/08/2012 10:27:46.14 - Info: Verified digital file signatures of Windows Update Agent installation and catalog files
Sat 25/08/2012 10:27:46.14 - Info: Created integrity database for Windows Update Agent installation and catalog files
Sat 25/08/2012 10:27:47.09 - Info: Verified integrity of .NET Frameworks' installation files
Sat 25/08/2012 10:27:52.30 - Info: Downloaded/validated installation files for .NET Frameworks 3.5 SP1 and 4
Sat 25/08/2012 10:27:52.32 - Info: Verified integrity of existing updates for dotnet x86-glb
Sat 25/08/2012 10:27:59.91 - Info: Determined static update urls for dotnet x86-glb
Sat 25/08/2012 10:28:00.66 - Error: Download failure for dotnet x86-glb

Where to from here?

[Denniss]

What's the installation path of your WOU files?
->Does it contain some special characters?
Do you always get the "Determining superseded updates (please be patient, this will take a while)..." on re-runs?
->If the process was successfully completed, it should have created a file "ExcludeList-superseded.txt" in the \exclude subfolder, about 1MiB in size. The process will only be restarted if M$ updated their patch database file.

[IslandBoy77]

WOU? Do you mean the WSUS folder itself? It normally lives in my Shared folder so that it can be accessed across my wired LAN network. The folder name / location is: C:\Users\Public\Documents\_WSUS_Offline_6.82

I tried creating a brand new folder with the default wsusoffline folder name in the root of C:, then transferring the md contents from client and also the relevant actual data folders - but that made no difference at all. I do note that all of the hashes in the md folder contain an entry similar to this:

Code: Select all

## Invoked from: C:\Users\Public\Documents\_WSUS_Offline_6.82\client\md
## C:\Users\Public\Documents\_WSUS_Offline_6.82\client\md> ..\bin\hashdeep.exe -c md5,sha1,sha256 -l -r ..\cpp

So, if I copy the content of the md folder to a "vanilla" wsus setup folder (along with the other relevant folders from the client folder), I get this:

Code: Select all

Sat 25/08/2012 11:53:38.26 - Warning: Integrity database ..\client\md\hashes-wsus.txt not found
Sat 25/08/2012 11:53:38.63 - Info: Downloaded/validated most recent Windows Update Agent installation and catalog files
Sat 25/08/2012 11:53:38.64 - Info: Verified digital file signatures of Windows Update Agent installation and catalog files
Sat 25/08/2012 11:53:38.64 - Info: Created integrity database for Windows Update Agent installation and catalog files
Sat 25/08/2012 11:53:39.58 - Info: Verified integrity of .NET Frameworks' installation files
Sat 25/08/2012 11:53:44.69 - Info: Downloaded/validated installation files for .NET Frameworks 3.5 SP1 and 4
Sat 25/08/2012 11:53:44.69 - Info: Verified integrity of existing updates for dotnet x86-glb
Sat 25/08/2012 11:53:51.83 - Info: Determined static update urls for dotnet x86-glb
Sat 25/08/2012 11:53:52.45 - Error: Download failure for dotnet x86-glb

If I do the same but DONT copy the content of the md folder, I get this:

Code: Select all

Sat 25/08/2012 12:04:34.11 - Info: Verified integrity of Windows Update Agent installation and catalog files
Sat 25/08/2012 12:04:35.03 - Info: Downloaded/validated most recent Windows Update Agent installation and catalog files
Sat 25/08/2012 12:04:35.03 - Info: Verified digital file signatures of Windows Update Agent installation and catalog files
Sat 25/08/2012 12:04:35.03 - Info: Created integrity database for Windows Update Agent installation and catalog files
Sat 25/08/2012 12:04:36.02 - Warning: Integrity database ..\client\md\hashes-dotnet.txt not found
Sat 25/08/2012 12:04:36.23 - Info: Downloaded/validated installation files for .NET Frameworks 3.5 SP1 and 4
Sat 25/08/2012 12:04:36.23 - Warning: Integrity database ..\client\md\hashes-dotnet-x86-glb.txt not found
Sat 25/08/2012 12:04:36.24 - Info: Determined static update urls for dotnet x86-glb
Sat 25/08/2012 12:04:36.81 - Error: Download failure for dotnet x86-glb

I've checked the hashes-wsus.txt file - it exists and appears to be correct. I've checked it's pathname - all fine.:

Code: Select all

%%%% HASHDEEP-1.0
%%%% size,md5,sha1,sha256,filename
## Invoked from: C:\Users\Public\Documents\_WSUS_Offline_6.82\client\md
## C:\Users\Public\Documents\_WSUS_Offline_6.82\client\md> ..\bin\hashdeep.exe -c md5,sha1,sha256 -l -r ..\wsus
##
6776168,f723820b8656e82958fa7ed854a7eefe,50186ec913a4896a92d72e5e5384693bf3a71182,b2512e0c2786f72ed41559580261c782a13fb5ea7fe23878873f83ecaeeec25f,..\wsus\WindowsUpdateAgent30-x86.exe
7749976,b46c93117c07626bebc7af83a7562034,fc0ee3a9af88ef2237aac450bc94b2fc08af79f5,d500a5b5945fafc6a52fb54b7169b62c6c1137e1694184ff2eff790aa1394ece,..\wsus\WindowsUpdateAgent30-x64.exe
32937230,90e27b6c9b6dade9cd3c45b7b67e90d8,8f1b5d8c17e1de110afd1ac1bed54a826bf37d43,ae3eca56b0f3dd1014846ac97d46639fb807a7c2d1c7aeeb1e9033843613e364,..\wsus\wsusscn2.cab

There is a ExcludeList-superseded-exclude.txt at this location C:\Users\Public\Documents\_WSUS_Offline_6.82\exclude that contains these entries:

Code: Select all

windows6.0-kb2633171
windows6.1-kb2633171
kb2645640

Is that text file supposed to read ExcludeList-superseded.txt or ExcludeList-superseded-exclude.txt?

There's also a file called ExcludeList.txt in the C:\Users\Public\Documents\_WSUS_Offline_6.82\client\exclude folder. It contains these entries:

Code: Select all

kb816093,MS03-011: Flaw in the Microsoft VM could enable system compromise
kb951847,.NET Framework 3.5 Service Pack 1
kb890830,Malicious Software Removal Tool
kb926874,Internet Explorer 7
kb940767,Internet Explorer 7
kb944036,Internet Explorer 8
kb982861,Internet Explorer 9
kb976002,Browser Choice
kb923618,Office 2003 Service Pack 3
kb953195,Office 2007 Service Pack 2
kb2526086,Office 2007 Service Pack 3
kb2460049,Office 2010 Service Pack 1
kb936929,Windows XP Service Pack 3
kb914961,Windows Server 2003 Service Pack 2
kb936330,Windows Vista / Server 2008 Service Pack 1
kb948465,Windows Vista / Server 2008 Service Pack 2
kb976932,Windows 7 / Server 2008 R2 Service Pack 1

[harry]

Could you please verify the existence and functionality of %systemroot%\system32\expand.exe (see ...\cmd\DownloadUpdates.cmd [line 916]).

[boco]

There is a ExcludeList-superseded-exclude.txt at this location C:\Users\Public\Documents\_WSUS_Offline_6.82\exclude that contains these entries:

This one is OK. Sometimes superseded patches (which are usually deleted by WSUSOU) are still needed in some cases, so these are excluded from being deleted. I have the same three entries here.

What we really mean is the ./Exclude/ExcludeList-superseded.txt file. For me, it currently has a size of 1,031,086 bytes, nearly one MiB. If you don't have that file then this is the problem. Personally, I still think it has to do with the msxsl.exe ===> XSLT.vbs change.

[IslandBoy77]

PROBLEM SOLVED!

Well, I found the problem. Whilst poking about I decided to try running WSUS on my PC (been a while since I have) and it immediately came up with the dreaded Determination of OS properties failed error message. I thought that odd since nothing else on my PC has been grumping (I checked various Event Viewer logs - nothing of note or relevant). All the regsvr commands that are typically recommended for fixing VBScript worked but still I couldn't get the WSUS script that determines the OS to run. Looking through a post on another website that talked about making sure than various Registry entries were correct, I found that my Registry was missing 2 of the 3 main keys. Fortunately, I just happen to be working on a Vista (32-bit) laptop at the moment, so I exported the 2 missing keys (which FYI were HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8} and HKEY_CLASSES_ROOT\CLSID\{B54F3743-5B07-11cf-A4B0-00AA004A55E8} - the relevant numbers being highlighted in bold) and now everything in WSUS works.

Hopefully this saga will help someone else with corrupted VBScript registry entries whose having trouble with WSUS.

Thanks to boco for his help.

[WSUSUpdateAdmin]

Hi IslandBoy77,

thanks for your joyful feedback!

Regards
Torsten Wittrock