Anyone get the March wsusscn2.cab file yet?

March 08, 2016 21:32

The wsusscn2.cab file being acquired in my lab is currently dated Feb 9th. Seems like someone at Microsoft is sleeping on the job again.

9 comments

Please sign in to leave a comment.

Previous 9 comments

Date Votes

Rangesh Vaidya

March 08, 2016 21:51

I have been able to get the latest Microsoft Catalog file (wsusscn2.cab) for March 2016.. it may take some time before all of Microsoft servers are updated with the latest CAB file.

Rangesh Vaidya

March 08, 2016 21:52

Correcting my statement below, I mean to say I have not been able to get it so far.

John Edmondson

March 08, 2016 22:01

I just download it from this link and check the signature date before I try to do anything else. (saves running the actual acquisition to find out). There are a couple of different links that I have seen but they all seem to get updated around the same time.

http://download.windowsupdate.com/microsoftupdate/v6/wsusscan/wsusscn2.cab

James Longo - EU

March 08, 2016 22:12

I delete the data/patch/msft/wsusscn2.cab file, and run a batch file to acquire. Within a minute or 2 you can see if the new wsusscn2.cab file is old/new and kill the dos prompt, wait a few minutes and try again. It takes 3-4 hours to acquire in my lab so I always make sure the wsusscn2.cab file is updated first.

nvdkit-rca-patch.exe ./modules/patch.tkd acquire -bulletins MS16-02*,MS16-03*
pause

Rangesh Vaidya

March 09, 2016 03:07

I also notice wsusscn2.cab date as 2/9/2016. Hopefully, MS will fix it soon.

https://social.technet.microsoft.com/Forums/windowsserver/en-US/e840585c-97ae-4fcb-adf6-fa9b94e8b15d/march-2016-wsusscn2cab-doesnt-appear-to-be-updated-for-today?forum=winserverwsus

John Edmondson

March 09, 2016 13:03

still not updated. 8 am EST

James Longo - EU

March 09, 2016 15:45

wsusscn2.cab has finally been updated.

John Edmondson

March 09, 2016 16:48

We opened an MS ticket, and our TAM said...

"I have an update as it relates to the WSUSSCN2.CAB file. Apparently there was an issue with signing the file yesterday and that is why the file wasn’t updated / released. It looks to have been fixed and the I just downloaded the file and it has a timestamp and certificate dated for March 8^th. Please see if that file has the March updates in it. If not, then the file is still being prepared and should be released very shortly."

and the file is indeed updated.