Other links
Radia - General Discussions
April wsusscn2.cab file corruption
I am getting a wsusscn2.cab file corruption error in my lab (9.2, 9.1) when running an acquisition for the April security patches. Anyone else getting this error?
ERROR: Cabinet file wsusscn2.cab is corrupted
On a side note:
Microsoft released the April Security bulletins via the new Security Update website. I have not detected an updated via the legacy Security Bulletin website yet and the Security bulletin website is re-directing to the new Security Update website. If the legacy bulletin naming convention has been dropped than you may no longer acquire bulletins in the following format. MS17-XXX
Security Update website:
https://portal.msrc.microsoft.com/en-us/security-guidance/summary
Previous 7 comments
John,
Currently the acquisitions should fail due to a change in the wsuscn2.cab file, and Accelerite is working on a resolution.
I only acquire 2 bulletins, the Security rollup and Security only bulletins for Win7 32/64. The number of bulletins will change based on other OS's and products.
For Win732/64 it should be:
MS-KB4015549 and MS-KB4015546
Running an acquire for MS-KB* will bring down all available kb articles on the MUC feed and will take a while. I would suggest narrowing it down to at least a series, for instance MS-KB401*
The acquisition is successful if you use the string MS-KB* or more accurately get the unique KB numbers from the Security Update Guide shared <https://portal.msrc.microsoft.com/en-us/security-guidance>. Select the criteria using the check box, click the Download button on the right side of the screen above the table guide and this will download the guide to an Excel sheet.
This can be used to sort the MS-KB's required for acquisition based on requirement - Security Only, OS or Rollup.
Use comma separated KB numbers instead of MS Bulletin numbers and start acquiring for eg: MS-KB401XXXXX,MS-KB371XXXXX,MS-KB.....
Accelerite will be making an Official announcement on all the MS Bulletins that are released for the April Month.
The acquisitions in my lab on both 9.1 and 9.2 are running longer so the problem may be resolved. The corruption error appeared to be the same as previously reported and resolved with updated patch.tkd modules. I have been running the hotfixes since they were released and still running the same patch.tkd modules. I am not sure if this was a local or global problem. Did anyone else get the corruption errors while running an acquisition yesterday?
Participate
Ask, Discuss, Answer