forums.wsusoffline.net

I don't know how to determine that.

On a side note, I found a backup of my system from a few months ago, and it had WSUS 10.7.3 on it with updates from Nov 2016. I used that to make a WSUS flash drive, and that one works just fine.

So something definitely changed in the WSUS version that is causing the issue. I guess it could be the updates themselves, not really sure how this works =P

Double click the signatures. Does it say "The digital signature is valid" (or similar)?

Not sure if this is pertinent, but 3 Windows 7 machines in a row have not updated now. I updated WSUS maybe 5 days ago, then the problem. All the other things are installed: IE11, .NET 4.6.2, etc, but the actual updates are not installed. Consequently I will have 350-620MB of updates to pull online. I have retried to run WSUS on one of the machines and no difference.

Could you post the content of .\client\md\hashes-wsus.txt?

Me? That folder is empty.

Then you are running without verification and most probably have a corrupt wsusscn2.cab catalog as a result.

Yes, that box is unchecked. I'll update again and see if there's a difference. Thanks.

I just attempted a WSUS update, and got a fatal: "ERROR: Catalog file ..\client\wsus\wsusscn2.cab signature verification failure". That folder is also empty.

With verification on, WOU detects if the downloaded catalog is corrupt. Without verification, it proceeds but doesn't give any meaningful results (or no updates at all).

paul1149 wrote:I just attempted a WSUS update, and got a fatal: "ERROR: Catalog file ..\client\wsus\wsusscn2.cab signature verification failure". That folder is also empty.

That's the problem, such a corrupt catalog is not usable at all and thus deleted. You need to retry until you hit an MS server carrying a good copy.

Once WOU has a good copy, it is automatically rolled back to, should it ever download another corrupt one after that.