Content Modification: Patches for Windows published 2019-02-20

Content in the Patches for Windows site has been modified.

Modified:

[Major] MS18-JUL: Security Only Quality Update - Security Only - Windows 7 SP1 - .NET Framework 3.5.1 - KB4338612 (x64) (ID: 433861201)
[Major] MS19-FEB: Security Monthly Quality Rollup - Monthly Rollup - Windows Server 2012 - .NET Framework 4.6/4.6.1/4.6.2/4.7/4.7.1/4.7.2 - KB4483449 (x64) (ID: 448344901)
[Major] MS19-FEB: Security Only Quality Update - Security Only - Windows Server 2012 - .NET Framework 4.6/4.6.1/4.6.2/4.7/4.7.1/4.7.2 - KB4483468 (x64) (ID: 448346801)
[Major] MS19-FEB: Cumulative security update for Internet Explorer - Windows Server 2012 R2 - IE 11 - KB4486474 (x64) (ID: 448647413)
[Major] MS19-FEB: Security Monthly Quality Rollup - Monthly Rollup - Windows Server 2012 R2 - .NET Framework 3.5 - KB4483459 (x64) (ID: 448345901)
[Major] MS19-FEB: Security Only Quality Update - Security Only - Windows Server 2012 R2 - .NET Framework 3.5 - KB4483484 (x64) (ID: 448348401)
[Major] MS19-FEB: Security Monthly Quality Rollup - Monthly Rollup - Windows Server 2012 R2 - .NET Framework 4.5.2 - KB4483453 (x64) (ID: 448345303)
[Major] MS19-FEB: Security Only Quality Update - Security Only - Windows Server 2012 R2 - .NET Framework 4.5.2 - KB4483472 (x64) (ID: 448347201)
[Major] MS19-FEB: Security Monthly Quality Rollup - Monthly Rollup - Windows Server 2012 R2 - .NET Framework 4.6/4.6.1/4.6.2/4.7/4.7.1/4.7.2 - KB4483450 (x64) (ID: 448345001)
[Major] MS19-FEB: Security Only Quality Update - Security Only - Windows Server 2012 R2 - .NET Framework 4.6/4.6.1/4.6.2/4.7/4.7.1/4.7.2 - KB4483469 (x64) (ID: 448346903)

Reason for Update:
False negative for February 2019 security fixlets on systems that have the re-released versions of KB2919355 and KB4054566.
Address false negative case for fixlet ID: 433861201

Actions to Take:
None

Published site version:
Patches for Windows, version 3197

Additional links:
None

Application Engineering Team
BigFix

I’m a bit confused with what to do with these modified patches.

We have already deployed 3 of these affected .Net patches to our Dev-Test servers. With no issues thankfully.

The baselines used for our Dev-Test environment will also be used for our Production environment pending a waiting period.

I noticed that on our baselines today, the affected .Net fixlets had to be ‘Sync’d with source’ - so does that mean my baselines now contain different versions of what was there last week when I rolled out to Dev-Test?

Am I correct in thinking that MS have re-released a newer version of these .Net patches in the Preview rollup dated 19/Feb (not yet visible in Bigfix), and so if we’ve already deployed the “old” versions to Dev-Test, we should wait and send the “new” versions to Dev-Test again, before deploying to production?

We’ve halted patching for now until we see the ‘new’ versions appearing in the Preview for March rollup.

Thanks in advance.

The patch binaries in these fixlets have not changed. The fixlet relevance was updated to address some detection issues.

The March preview patches will be released as new separate fixlets.

1 Like

The March preview rollups have been released in Patches for Windows version 3198.

1 Like

This topic was automatically closed after 30 days. New replies are no longer allowed.