locked
MBSA not detecting any of the June 2016 hotfixes RRS feed

  • Question

  • Hello,

    just downloaded the latest wsusscn2.cab (167909 kb) for MBSA offline scanning ... but it does not detect any of the new June 2016 hotfixes. Same result when MBSA is downloading it itself.

    Any ideas somebody?

    Wednesday, June 15, 2016 6:10 AM

All replies

  • Same here. The contents are dated 13th June and some of the content in package.xml refers to files from June 2016 but somehow the detection logic does not work.

    Hopefully MS will notice and correct it soon!!

    Ray

    Wednesday, June 15, 2016 7:57 AM
  • Hello,

    I tried it this Morning with Windows Server 2012 R2 Systems and no new MS Updates where detected for June 2016.

    There seems to be a problem with the wsusscn2.cab file.

    J.U.K


    Wednesday, June 15, 2016 8:12 AM
  • Same here. Previous (e.g. may) updates *are* detected but none of the June updates.

    Since we are not using mbsa but the wua api directly, this is clearly due to the cabinet.

    • Edited by jkhemker Wednesday, June 15, 2016 8:16 AM
    Wednesday, June 15, 2016 8:14 AM
  • Come on MS, fix the cab file.  Waiting for Doctor Watson to make it into the office?
    Wednesday, June 15, 2016 3:13 PM
  • I am seeing the same behavior as what others have reported, please provide an update soon as you can.  

    Greatly Appreciated,
    RV

    Wednesday, June 15, 2016 6:33 PM
  • This is currently being investigated.  No ETA at this time.

    Wednesday, June 15, 2016 6:56 PM
  • Hello Blake,

    Can we expect a Offical Communication rolled out by Microsoft on https://technet.microsoft.com/en-us/security/bulletins.aspx

    This will help us know the whats the issue, ETA and we can also update back our customers.

    Regards,
    Jagan

    Wednesday, June 15, 2016 11:55 PM
  • Hey folks, sorry for the delay.  We are still waiting on an update from the component owners.  I will update this thread when I have more details.

    Thursday, June 16, 2016 2:16 PM
  • Hey folks, sorry for the delay.  We are still waiting on an update from the component owners.  I will update this thread when I have more details.

     Blake,

      Can you run over to Starbucks and ask the component owners if they have an update yet? The rest of the world would like to go back to not waiting for Microsoft to release the wsusscn2.cab file.

      

    Thursday, June 16, 2016 4:58 PM
  • Still waiting on an update from the Microsoft Update devs.  Will post an update when I have more info.  Sorry for the delay folks!

    Thursday, June 16, 2016 6:21 PM
  • Hi Blake

    Nothing has or is changing.  Please can you check with the MSFT Update Developers directly

    instead of waiting for their reply 

    Comparing files wsusscn2.cab and WSUSSCN2-5.CAB
    FC: no differences encountered

    06/15/2016  08:09 AM       171,938,570 wsusscn2-1.cab
    06/15/2016  02:59 PM       171,938,570 wsusscn2-2.cab
    06/15/2016  10:00 PM       171,938,570 wsusscn2-3.cab
    06/16/2016  07:46 AM       171,938,570 wsusscn2-4.cab
    06/16/2016  10:21 AM       171,938,570 wsusscn2-5.cab
    06/16/2016  02:41 PM       171,938,570 wsusscn2.cab

    Thanks

    Thursday, June 16, 2016 6:57 PM
  • All I can say is that they are still investigating/working on this issue.  I will update this thread when I have more information.  Thank you for your patience.
    Thursday, June 16, 2016 7:24 PM
  • The wsusscn2.cab file has finally been updated by Microsoft.
    Friday, June 17, 2016 7:43 AM
  • Wsusscn2.cab has been updated:  http://go.microsoft.com/fwlink/?LinkID=74689

    Thanks folks!

    Friday, June 17, 2016 11:57 AM