Content Modification: Patches for Windows published 2019-05-15 (v3281)

[bma]

Content in the Patches for Windows site has been modified.

Modified:

[Minor] MS19-FEB: Security update for SharePoint Foundation 2013 - SharePoint Foundation 2013 SP1 - KB4462143 (x64) (Superseded) (ID: 446214301)
[Major] MS19-MAY: Servicing Stack Update for Windows Server 2016 - Windows Server 2016 - KB4498947 (x64) (ID: 449894703)

Reason for Update:
Fixlet ID: 446214301 was referencing wrong superseding KB in its description.
Fixlet ID: 449894703 was incorrectly becoming relevant on some Windows Server 2019 systems

Actions to Take:
None

Published site version:
Patches for Windows, version 3281

Additional links:
None

Application Engineering Team
BigFix

[lloydj]

Hey IBM,
The full patch for .NET Framework 4.7 for Windows 7 SP1 is not detecting as relevant.

Each month Microsoft releases a “security only” update and “security quality” update (which includes non-security fixes) for .NET Framework on Windows 7. They should both detect as relevant on the same systems, for obvious reasons. This month they have sequential KB numbers, 4495587 and 4495588.

MS19-MAY: Security Only Quality Update - Security Only - Windows 7 SP1 - .NET Framework 4.6/4.6.1/4.6.2/4.7/4.7.1/4.7.2 - KB4495587 (x64)
MS19-MAY: Security Monthly Quality Rollup - Windows 7 SP1 - .NET Framework 4.6/4.6.1 - KB4495588 (x64)

4495587 is detecting as relevant on our systems, but 4495588 is not. When running Windows Update against Microsoft servers, 4495588 comes up as needed.

[bma]

@lloydj Team did identify an issue with that .NET framework fixlet as well as the corresponding 32-bit equivalent fixlet.

Updated fixlets have been released in Patches for Windows version 3282.

For the fixlet you mentioned above, there was an update to relevance 6.

Not sure if that’s the specific relevance statement that was causing problems for you but please have a look at the updated fixlet.