Newsletter Archives
-
The patch waiting game — September edition
PATCH WATCH
By Susan Bradley
For those of us in the northern hemisphere, September can be a time when days seem to be noticeably shorter — the daylight hours more precious.
Time has value, too, when it comes to patching our systems. As regular Patch Watch readers know, we need some time for the monthly updates to sort themselves out. In the days following Patch Tuesday, some updates get reissued due to significant issues, while others need clarification.
Read the full story in AskWoody Plus Newsletter 16.33.0 (2019-09-16).
-
Official history of cumulative updates for .NET in Win10 1809 and 1903
Two important links for anyone wrangling with .NET updates:
History of Cumulative Updates for .NET Framework for Windows 10, version 1809
History of Cumulative Updates for .NET Framework for Windows 10, version 1903
There aren’t any entries in the latter list, so far.
Thx, @abbodi86
-
Install the Patch Tuesday .NET security-only patch KB 4457916 and you clobber SharePoint Workflows
I haven’t seen this bug show up in other .NET patches just yet, but it’d be worthwhile keeping your eye out for it.
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.
-
Server error “invalid AppPoolId ‘CertWebService_App’” due to bad .NET patches?
Interesting quandary from @jstillings1:
Ok folks theory check this.
Windows server 2016 essentials set up 7/21/2018
All patches are installed… yes the july ones.
Local machines are getting an error when trying to use the web interface to connect to the domain by using http://[server-name]/Connect
I have a theory it is due to the certificate issues with IIS with .Net updates with the july patches…
Here is the error codes in IIS
The application ‘/’ belonging to site ‘2’ has an invalid AppPoolId ‘CertWebService_App’ set. Therefore, the application will be ignored.
Site 2 was disabled because the root application defined for the site is invalid. See the previous event log message for information about why the root application is invalid.
The Application Host Helper Service encountered an error trying to delete the history directory ‘C:\inetpub\history\CFGHISTORY_0000000014’. The directory will be skipped and ignored. Note that the directory may still get deleted in the future if the service restarts. The data field contains the error number.
So am I just a IT noob and didnt set up the server right or… did the .NET patches break something..
-
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
-
.NET patches — manual installation only — released
Windows 7 and 8.1 non-security .NET updates are now available, but only through the Microsoft Catalog.
Details on the Windows Software Update site.
-
Resurrected KB 951847 ‘zombie’ patch fixed — but now has new problem
If you’re running XP or Server 2003, and you’re trying to keep .NET off of them, this is going to be a very complicated re-re-patch.
InfoWorld Tech Watch