wsusscn2.cab just updated. Enjoy.

Hello Jim,

My understanding is that the WSUSSCN2.cab is not updated yet. 

Hi Jim

I have started an .acq and the file downloaded is current

03/14/2017 01:24 PM 217,061,128 wsusscn2.cab
1 File(s) 217,061,128 bytes

Currently we have the new March cab file. However, when it extracts to Data/PatchManager/pach/msft/wsus/* during the acquire it halts after package11.cab and states the wsusscn2.cab is corrupt. I have deleted the .cab file and let the acquire download again however, it still stops at the same point as corrupt. Is anyone else having this issue or is it specific to our environment?

I did not have that problem on Tuesday and the acquisition completed successfully. What version of Radia/patch.tkd are you using? I will see if I can replicate in the lab using Radia 9.1/9.2 and get back to you shortly.

Hi!

My RCA 9.1 customer ran into the wsusscn2.cab corrupted issue a while back, and I received a hotfix for it (patch.tkd).

Contact Accelerite Support for the latest patch.tkd.

Best regards,

Arne

I have completed the acquisition a while back and I can see until package 63. Radia/Patch.tkd version may help us here, we can also look for any issues with download in the RCA\PatchManager\logs\Patch-acquire.log.

Radia 9.1, with patch.tkd version 9.10.0000 build 91105.

Open a support case and get the latest patch.tkd. The new patch.tkd changed the extraction process. I think you should be at this level.

module patch         version 09.10.0000 build   91131

Got it. Support case going now. Thanks everyone!

We have downloaded it this morning to our development domain only. We have up to pkg63 as well.

Yes, the patch.tkd that solved it for my customer was version 09.10.0000 build 91131 from HOTFIX_OVCM_PATCHMGR_V9.1_2016-11-18_147945246423a81fa.
I must also add that it looked like the wsusscn2.cab file on the mirror that was accessed in fact was corrupt, in other words two simultaneous problems!

The updated patch.tkd (91131) decreases the amount of time the acquire runs due to the increased efficiency of the extraction procedure. I went from 3-4 hours down to around 2 hours with the new patch.tkd

I would also like to take this opportunity to remind the Radia community that we offer a wsusscn2.cab free environment for those that would like to utilize Radia Patch Manager without updating the wsusscn2.cab file each month.

We able to download the cab file (dated 3.15.17) .. But the below patches are skipping.  Do any of the have same issues.

MS17-009

MS17-011

Thanks,

Parthy

HI we've the same issue with the bulletin MS17-009 and MS17-011. The acquisition process is running smoothly however those 2 bulletins are not on the final list !

With regards to MS17-009 and 011 not downloading: If you take a look at the Q numbers inside the bulletins you will find they are duplicated within other bulletins. The acquire only retrieves what is needed. In this case that's probably MS17-012.

The main bulletin for March is MS17-006 and that is where you will find the kb numbers for 009, and 011. Did you acquire MS17-006?

Yes, thanks to everyone. I confirm that we have he MS17-006 which include the other missing bulletin

Microsoft is dropping the MS17-XXX naming convention and will use only kb number in the future, at least that is what they keep telling us. Here is the link to the new format that we should all get very familiar with as the bulletins(MS17-XXX)  can stop updating at any time. 

https://portal.msrc.microsoft.com/en-us/security-guidance/summary