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 no indication from Microsoft if and/or when they&ll be fixed.These patches, originally released on Patch Tuesday, July 10, are baring their FAANGs:KB 4340556— Security and Quality Rollup updates for .Net Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1 and 4.7.2 for Windows 7 SP1 and Server 2008 R2 SP1 KB 4340557— Security and Quality Rollup updates for .Net Framework 3.5 SP1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, and 4.7.2 for Windows Server 2012KB 4340558 —Security and Quality Rollup updates for .Net Framework 3.5 SP1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, and 4.7.2 for Windows 8.1, RT 8.1, and Server 2012 R2KB 4340559— Security and Quality Rollup updates for .Net Framework 2.0 SP2, 3.0 SP2, 4.5.2, and 4.6 for Windows Server 2008The patches had been out for less than a day when we started seeing error reports on AskWoody.
As I noted on July 12: