{"id":12875,"date":"2018-07-23T04:30:08","date_gmt":"2018-07-23T12:30:08","guid":{"rendered":"http:\/\/www.palada.net\/index.php\/2018\/07\/23\/news-6642\/"},"modified":"2018-07-23T04:30:08","modified_gmt":"2018-07-23T12:30:08","slug":"news-6642","status":"publish","type":"post","link":"https:\/\/www.palada.net\/index.php\/2018\/07\/23\/news-6642\/","title":{"rendered":"July Windows .Net patches appear, disappear, reappear, disappear again"},"content":{"rendered":"

<\/p>\n

Credit to Author: Woody Leonhard| Date: Mon, 23 Jul 2018 05:15:00 -0700<\/strong><\/p>\n

Microsoft’s July 2018 series of patching missteps, with .Net security patches in particular, have left many admins in the lurch. Less than two weeks after they were first unleashed, poorly documented versions of the patches now appear to be available, but are not being actively pushed. There\u2019s no indication from Microsoft if and\/or when they\u2019ll be fixed.<\/span><\/p>\n

These patches, originally released on Patch Tuesday, July 10, are baring their FAANGs:<\/span><\/p>\n

The patches had been out for less than a day when we started seeing error reports on AskWoody. As I <\/span>noted on July 12<\/span><\/a>:<\/span><\/p>\n

If you tried to install KB 4340558, the \u201cSecurity and Quality Rollup updates for .Net Framework 3.5 SP1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, and 4.7.1 for Windows 8.1, RT 8.1, and Server 2012 R2\u201d and had it crash with an error 0x80092004, you aren\u2019t alone. AskWoody poster<\/span> macauln82 says<\/span><\/a> he\u2019s seen it happen on all of his Server 2012 R2 machines. G\u00fcnter Born has a<\/span> detailed explanation<\/span><\/a>. <\/span><\/p>\n

On July 13, in damage control mode, Microsoft <\/span>posted article KB 4345232<\/span><\/a>, <\/span>“0x80092004” error occurs and July 2018 .NET Security and Quality Rollup update KB4340557 or KB4340558 does not install after you apply June update KB4291497 or KB4291495<\/span><\/i>. The original version of that article listed two manual workarounds, neither of which worked in all cases.<\/span><\/p>\n

Microsoft modified the patches (it\u2019s not clear exactly how), and reposted them on the Update Catalog dated July 16.<\/span><\/p>\n

Then, on July 19, they were reposted again. If Microsoft changed the KB article to reflect the new-new versions, I can\u2019t find the modification. But the KB 4345232 article was updated on July 19 to say:<\/span><\/p>\n

Microsoft has re-released the July 2018 .NET Framework Security and Quality Rollup updates, KB 4340558 and KB 4340557 to correct an installation issue. You can scan for these updates through Windows Update. You can also download and install these updates directly through the following Knowledge Base articles …<\/span><\/p>\n

As if that weren\u2019t enough, the patches were updated again, and now appear in the Update Catalog marked July 20. Again, there\u2019s no indication what was changed or why, but the original KB articles now say they were updated on July 20.<\/span><\/p>\n

According to <\/span>Susan Bradley<\/span><\/a>, <\/span><\/p>\n

For the record the .NET updates have not be officially \u201cpulled\u201d but they are unchecked and not being pushed via Microsoft update. If you use WSUS to patch you may want to pull back on approval<\/span><\/p>\n

I\u2019ve seen multiple reports of the patches not appearing in the WSUS list.<\/span><\/p>\n

That leaves us with a handful of .Net patches that have gone through at least four revisions \u2014 most of which are completely undocumented \u2014 in the past two weeks. Who\u2019s testing this stuff? <\/span><\/p>\n

Stuck in a .Rut? Join us on the<\/span><\/i> AskWoody Lounge<\/span><\/i><\/a>.<\/span><\/i><\/p>\n

http:\/\/www.computerworld.com\/category\/security\/index.rss<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

<\/p>\n

Credit to Author: Woody Leonhard| Date: Mon, 23 Jul 2018 05:15:00 -0700<\/strong><\/p>\n

\n
\n

Microsoft’s July 2018 series of patching missteps, with .Net security patches in particular, have left many admins in the lurch. Less than two weeks after they were first unleashed, poorly documented versions of the patches now appear to be available, but are not being actively pushed. There\u2019s no indication from Microsoft if and\/or when they\u2019ll be fixed.<\/span><\/p>\n

These patches, originally released on Patch Tuesday, July 10, are baring their FAANGs:<\/span><\/p>\n