forums.wsusoffline.net

That file has about doubled in size since the last time I updated. Tried and tried many times but it'd just stop downloading at around 98% with a few seconds to go.

So I did what I've done before when this happens, go direct to the source at Microsoft. http://download.windowsupdate.com/micro ... usscn2.cab Still had issues with it quitting before finishing. So I used Getright and was able to make Microsoft's server let me have the whole file.

Copied it to client\wsus and the update generator rejected it and deleted it, claimed it didn't match. How the heck not? It was downloaded from the same location wget kept failing to complete the download. Getright gets the entire file, doesn't quit until it has the whole file.

I finally had to run it without verification to force it to accept the wsusscn2.cab file that is the current one.

You provided the answer yourself: WSUSOU stores a checksum for the file. If you exchange it for a different one the checksum doesn't match and it is rejected.

It's NOT different. I used Getright to download the exact same file from the same location wget was failing to download.

But maybe a newer version than tehe version the hashes were stored for.
Pleas delete all files in .\client\md and restart download using UpdateGenerator.

Two possible sources for this download problem:
1) wget lost connection and is not able/willing to reconnect and continue download from point of interruption
2) file has becoming huge in size, maybe your antivirus was still checking it

Wasn't there a fix somewhere to enable/speed-up wget reconnections?

Galane wrote:It's NOT different. I used Getright to download the exact same file from the same location wget was failing to download.

Yes, and since WSUSOU failed to download it has not calculated a (valid) hash for the file, if any at all. The hash is only calculated after successful download.

What would fix that is some way of getting the hashes for the current file versions from an online source. With verification off it'd recognize that the file on the server is no newer than the local file, then go ahead and update.

The last version I used was 7.3.1 and that cab file was less than half the size of the current one.

The .cab file is from M$ so blame them for the filesize explosion. They added support for Win8 and Server spin-offs and probably already something for new office programs.