Back to top
 
 
 

Microsoft has released 46 Security Updates for the month of July, 2017

On Tuesday, July 11, 2017 Microsoft has released 46 new security updates in offline catalog (i.e.WSUSSCN2.cab).

All the 46 security updates newly released in offline catalog (i.e.WSUSSCN2.cab) can be acquired via HPCA/RCA Patch Manager (versions 7.x, 8.1, 9.0, 9.1, 9.2 or 10.0) without having to wait for HP/Persistent supplied data feed corrections.

Summary

KB Numbers for acquisition

Excluding Monthly Rollup

New KBs released by Microsoft in Offline Catalogue file (WSUSSCN2.cab) on  Patch Tuesday – 11th  July

MS-KB4032955, MS-KB4026061, MS-KB4026059, MS-KB4025877, MS-KB4025872, MS-KB4025674, MS-KB4025497, MS-KB4025409, MS-KB4025398, MS-KB4025397, MS-KB4025376, MS-KB4025344, MS-KB4025343, MS-KB4025342, MS-KB4025341, MS-KB4025339, MS-KB4025338, MS-KB4025337, MS-KB4025336, MS-KB4025333, MS-KB4025331, MS-KB4025252, MS-KB4025240, MS-KB4022914, MS-KB4022748, MS-KB4022746, MS-KB4020322, MS-KB4018588, MS-KB3213657, MS-KB3213640, MS-KB3213624, MS-KB3213559, MS-KB3213555, MS-KB3213545, MS-KB3213544, MS-KB3213537, MS-KB3203477, MS-KB3203469, MS-KB3203468, MS-KB3203459, MS-KB3191907, MS-KB3191902, MS-KB3191897, MS-KB3191894, MS-KB3191833, MS-KB2880514

MS-KB4032955, MS-KB4026061, MS-KB4026059, MS-KB4025877, MS-KB4025872, MS-KB4025674, MS-KB4025497, MS-KB4025409, MS-KB4025398, MS-KB4025397, MS-KB4025376, MS-KB4025344, MS-KB4025343, MS-KB4025342, MS-KB4025339, MS-KB4025338, MS-KB4025337, MS-KB4025333, MS-KB4025252, MS-KB4025240, MS-KB4022914, MS-KB4022748, MS-KB4022746, MS-KB4020322, MS-KB4018588, MS-KB3213657, MS-KB3213640, MS-KB3213624, MS-KB3213559, MS-KB3213555, MS-KB3213545, MS-KB3213544, MS-KB3213537, MS-KB3203477, MS-KB3203469, MS-KB3203468, MS-KB3203459, MS-KB3191907, MS-KB3191902, MS-KB3191897, MS-KB3191894, MS-KB3191833, MS-KB2880514

Note: New Quality Rollups KBs released in July are : MS-KB4025341, MS-KB4025336, MS-KB4025331

New KBs released by Security Updates Guide console and API which are not present in Offline catalogue (WSUSSCN2.cab)

MS-KB4022887, MS-KB4022727, MS-KB4022726, MS-KB4022725, MS-KB4022724, MS-KB4022722, MS-KB4022719, MS-KB4022718, MS-KB4022717, MS-KB4022715, MS-KB4022714, MS-KB3212224 

Note: These KBs  cannot be acquired via Radia since they are not present in Offline catalogue (WSUSSCN2.cab) and Radia uses Offline catalogue for Patching.

 

Important Patches for Windows 10

MS-KB4025342 - Cumulative Update for Windows 10 branch 1703

MS-KB4025339 - Cumulative Update for Windows 10 branch 1607

MS-KB4025344 - Cumulative Update for Windows 10 branch 1511

MS-KB4025338 - Cumulative Update for Windows 10 branch 1507

 

KB for Adobe Flash Player

MS-KB4025376

 

Important Security Only KBs

MS-KB4025343  -  Windows Server 2012, Windows Server 2012 (Server Core installation) 

MS-KB4025337 - Windows Server 2008 R2 for x64-based Systems Service Pack 1, Windows Server 2008 R2 for Itanium-Based Systems Service Pack 1, Windows 7 for x64-based Systems Service Pack 1, Windows 7 for 32-bit Systems Service Pack 1, Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation). 

MS-KB4025333 - Windows Server 2012 R2 (Server Core installation), Windows 8.1 for 32-bit systems, Windows 8.1 for x64-based systems, Windows Server 2012 R2.

 

KB for IE Cumulative

MS-KB4025252

 

 

 

Comments

  • Avatar
    Permanently deleted user

    Hello all,
    i am having issue with installation of KB4025252 for IE11 on Windows 7 x64 Enterprise. It is detected by RADIA and reported as installed in the "patch_stats.html" yet it is nowhere visible in the installed updates. Is there a known issue for this one for the RADIA 7.9?

  • Avatar
    James Longo - EU

    There was/is an issue with this patch and I created a custom bulletin as a workaround. I am not sure if Microsoft resolved the MUC patch.

    Known issues in this security update
    Windows 7 for x64-based systems may continue to report that you need to apply this July 11, 2017 Internet Explorer 11 update after it has already been installed.

  • Avatar
    James Longo - EU

    I just had a look at the KB and the Known issue is still present in the Offline scan file, not MUC as I stated earlier. A custom bulletin resolves this problem.

    https://support.microsoft.com/en-us/help/4025252/cumulative-security-update-for-internet-explorer-july-11-2017

    Known issues in this security update
    Windows 7 for x64-based systems may continue to report that you need to apply this July 11, 2017 Internet Explorer 11 update after it has already been installed.

    As of this publication date, Microsoft had corrected the issue for both Windows Server Update Services (WSUS), and Microsoft Update Catalog distributions.
    Update management solutions that use the Windows Update offline scan method, may still experience this issue. Microsoft is currently investigating this issue and will provide an update to the Wsusscn2.cab as soon as possible.
    As a potential workaround, affected customers can choose to install the update by using WSUS, or manually by using the Windows Update Catalog page.

  • Avatar
    Permanently deleted user

    Thank you for very prompt reaction James.
    May you please advice me how to make Custom bulletin as my few attempts last time were unsuccessful?

  • Avatar
    James Longo - EU

    Hi Petar,
    The custom bulletins I create are only available for Evergreen support customers. You can however open a case with Accelerite Radia support and request a custom bulletin be made available for acquisition via Radia.

  • Avatar
    Permanently deleted user

    Thanks James

  • Avatar
    John Edmondson

    For what its worth, Microsoft has updated the cab file this morning (or overnight). the digital signature date is ‎now July ‎14, ‎2017 1:24:11 AM.

  • Avatar
    James Longo - EU

    I checked the bulletin and the known issue with this patch is still present so I would advise opening a case with Microsoft if possible to verify the updated wsusscn2.cab file will resolve the problem. Re-acquiring the wsusscn2.cab file in production will trigger an update to discover patch(wsusscn2.cab) throughout the enterprise.

    In any event, the best solution IMO would be a custom bulletin to target this specific patch without the need to deploy the 200MB wsusscn2.cab file a second time in one month to deploy a single patch.that is 50MB.

    Edited by James Longo - EU