Newsletter Archives
-
What should you do with the July patches?
Good question from s:
You moved to Defcon2 for August but we still don’t know what to do with the July patches. (Win 7) !!??
Short answer: Nothing. Wait for MS-DEFCON 3 or 4.
If you’re in Group B (Win7/8.1 Security only patches), you’ll have to manually install the July patches prior to installing the August patches. But for almost everybody, you don’t need to lift a finger.
-
We continue at MS-DEFCON 1: Don’t install any of the July patches
With August patches just around the corner, you’d be well advised to give up on the July patches. Yes, some folks dodged the (many!) bullets and managed to get some of the July patches installed without hosing their systems.
But for almost everybody, in almost every situation, the risk of installing the July patches is far, far greater than the risk of skipping them.
Computerworld Woody on Windows.
-
Microsoft releases 11 new .NET patches – but none (yet) for Win10 1703, 1709 or 1803
Yesterday saw a massive attempt — the fifth try this month — to fix the July .NET security patches.
Oddly, Microsoft fixed Win10 1607/Server 2016, but didn’t push out a fix for any other versions of Win10.
So far I haven’t seen any bugs. Perhaps the beta testers aren’t done yet. Or maybe they’ve wised up.
Computerworld Woody on Windows.
-
Where we stand with the July 2018 Microsoft patches
Quite possibly the worst month this year for patches.
And that’s saying something!
Computerworld Woody on Windows.
-
So many conflicting details in this month’s Windows patches
Wotta mess.
Yesterday’s round of Windows patches — for all versions of Windows — have so many internal inconsistencies it’s hard to keep score. Somebody’s playing fast and loose with the docs.
Computerworld Woody on Windows.
-
Yet another massive mess of Windows patches
Microsoft just released dozens of new patches — some dated July 23 in the Update Catalog, some dated July 24, some dated July 20.
Wotta mess.
All supported versions of Windows 10 got new patches, which are dated July 24 in the KB articles, but at this moment they’re still dated July 20 in the Update Catalog. Not clear if the patches in the Catalog are the same as the ones described in the KB articles.
The Win10 patches still have the “known issue”:
After you install any of the July 2018 .NET Framework Security Updates, a COM component fails to load because of “access denied,” “class not registered,” or “internal failure occurred for unknown reasons” errors. The most common failure signature is the following:
Exception type: System.UnauthorizedAccessException
Message: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Microsoft is working on a resolution and will provide an update in an upcoming release.
Many of the patches are Intel microcode updates, likely for Spectre 2. The MS Support page dedicated to such fixes hasn’t been changed since July 19. All of those patches, as best I can tell, are manual-install only.
The Monthly Rollup Previews for both Win7/Server 2008 R2 and Win8.1/Server 2012 R2 were re-issued today. I don’t see any documentation about the re-issue, anywhere.
Only a fool would tread in these waters. DON’T PATCH.
-
The July .NET patches are even worse than you think
Earlier today, Microsoft posted this advisory on the official MSDN .NET blog:
The July 2018 Security and Quality Rollup updates for .NET Framework was released earlier this month. We have received multiple customer reports of applications that fail to start or don’t run correctly after installing the July 2018 update.. A COM component fails to load because of “access denied,” “class not registered,” or “internal failure occurred for unknown reasons” errors.
We have stopped distributing the .NET Framework July 2018 updates on Windows Update and are actively working on fixing and re-shipping this month’s updates…
Workaround
Temporarily uninstall the July 2018 Security and Quality Rollup updates for .NET Framework to restore functionality until a new update has been released to correct this problem.
It’s been a banner month for Microsoft patches
-
July patches are all messed up — but a good hint appears in Japanese
I’ve given up on the July patches. Which is why we’re on MS-DEFCON 1.
There’s a little bit of light, though — coming from a Japanese language explanation from a Microsoft employee.
Computerworld Woody on Windows.