Exit on error

[aker]

Please try the following:
Create a temporary folder and copy .\client\wsus\wsusscn2.cab .\cmd\XSLT.vbs and .\xslt\ExtractUpdateRevisionIds.xsl into that folder. Unpack the "package.cab" from wsusscn2.cab and extract the file package.xml from it.
Open a command prompt and enter:

Code: Select all

cd /d "<your folder>"
cscript .\XSLT.vbs .\package.xml .\ExtractUpdateRevisionIds.xsl > log.txt


Check if it returns an error message and post the size and the first line of log.txt here.

[paul1149]

Again, I'm still back on 9.5 on this machine.

I got as far as trying to unpack wsusscn2.cab, then 7zip reported these errors:

Thanks

wsus 7zip error.jpg

(70.47 KiB) Not downloaded yet

[Denniss]

wsusscn2.cab should be 101 MB in size with the following checksums:
CRC32: 01930809
MD5: 8E262BD38DCDD3D9DB2BB1D976ACF6CC
SHA-1: A924275EF21D4F9F96519E8AA46D67C3D9FB5473

If your file has correct checksums, disable your Antivirus Software while running the WOU Update generator, wouldn't be the first time an AV software interferes with WOU processing of this file.

[aker]

If your checksums don't match please delete .\client\wsus\wsusscn2.cab (and .\client\md\hashes-wsus.txt if exists) and restart download.

Which AV program are you using?

[paul1149]

The copy I made of 9.5 wsusscn2.cab reports:

wsusscn2.cab

MD5 793dcdeb5ca03f1f9cee6f5117d4ebff
SHA1 f3e60071a949a69b5677e7c38077ce4e8f899fcf
CRC32 695308f7

I use Panda Free AV. I ran WSUSo 9.5 again, with the same error. I then disabled Panda, both AV and process monitoring. Same error. Then I ran WSUSo again, this time accepting its offer to update to the latest version. Same error.

I then ran hash on the actual wsuscn2.cab WSUSo uses, now updated, and it reports the same numbers.

[aker]

Please delete the wsusscn2.cab and rerun wsusou.
Try adding an exception for the wsusou folder.

[paul1149]

Instant success. I should have mentioned that I have an exclusion for the WSUSo folder in Panda, but my focus was on whether something got blocked in downloading WSUSo itself . I don't know how this file became corrupted, but I then synced it to usb sticks, and from there ran it on the other machines, where it of course replicated the error.

Thanks much for your time and attention.

Paul

[aker]

This might be interesting, too:
viewtopic.php?f=7&t=3863