Newsletter Archives

• The patch waiting game — September edition

  Posted on September 16, 2019 at 01:05 CDT by Tracey Capen • Comment in the Forums

  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).

  Patch Watch AskWoody Plus Newsletter, Cumulative Updates, NET, Office updates, Windows Updates

• Official history of cumulative updates for .NET in Win10 1809 and 1903

  Posted on July 18, 2019 at 03:17 CDT by woody • Comment in the Forums

  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

  Windows Patches/Security NET

• Install the Patch Tuesday .NET security-only patch KB 4457916 and you clobber SharePoint Workflows

  Posted on September 17, 2018 at 10:06 CDT by woody • Comment in the Forums

  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.

  Windows Patches/Security KB 4457916, NET, SharePoint

• Microsoft releases 11 new .NET patches – but none (yet) for Win10 1703, 1709 or 1803

  Posted on July 31, 2018 at 07:29 CDT by woody • Comment in the Forums

  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.

  Windows Patches/Security July 2018 Black Tuesday, NET

• Server error “invalid AppPoolId ‘CertWebService_App’” due to bad .NET patches?

  Posted on July 25, 2018 at 15:22 CDT by woody • Comment in the Forums

  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..

  Windows Patches/Security NET

• The July .NET patches are even worse than you think

  Posted on July 20, 2018 at 21:56 CDT by woody • Comment in the Forums

  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

  Windows Patches/Security .NET patches, July 2018 Black Tuesday, NET

• .NET patches — manual installation only — released

  Posted on July 25, 2017 at 14:08 CDT by woody • Comment in the Forums

  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.

  Windows Patches/Security NET

• Resurrected KB 951847 ‘zombie’ patch fixed — but now has new problem

  Posted on October 18, 2013 at 19:34 CDT by woody • Comment in the Forums

  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

  Windows Patches/Security KB 951847, NET, zombie patch

• Black Tuesday update

  Posted on June 14, 2012 at 10:49 CDT by woody • Comment in the Forums

  There’s been a lot of hubub about last Tuesday’s Microsoft patches.

  The best piece of advice: DON’T use Internet Explorer – it’s been compromised once again, and apparently the exploit is widely distributed.

  Tellingly, the only Black Tuesday patch to win ISC Storm Center‘s “Patch Now” status is the IE patch.

  I see some advice from antivirus companies to install the other patches, but I don’t buy it. The .NET exploit might be a problem, but I haven’t heard of any active attacks on .NET – and patching .NET is always so much fun.

  Keep your powder dry. I’m leaving us at MS-DEFCON 2: Patch reliability is unclear. Unless you have an immediate, pressing need to install a specific patch, don’t do it.

  Windows Patches/Security Internet Explorer, June 2012 Black Tuesday, NET

• It’s time to run .NET out of town

  Posted on May 24, 2012 at 18:19 CDT by woody • Comment in the Forums

  Microsoft can’t get their act together. Patching .NET is always a hassle. It’s time for developers to throw in the towel and choose an alternative that works.

  InfoWorld Tech Watch.

  Windows Patches/Security botched patches, NET

• MS-DEFCON 4: Pass on a couple of patches

  Posted on July 10, 2011 at 06:57 CDT by woody • Comment in the Forums

  I’m moving to MS-DEFCON 4. If you’re willing to trudge through the details, you should apply most outstanding Microsoft patches. If you don’t want the headache, you can safely pass on the June Black Tuesday patches – for now.

  Susan Bradley has an excellent roundup of the problems with the .NET patches in her Windows Secrets article. There are two .NET patches in this group, MS11-039 and MS11-044. They’ve spawned an evil mess of KB articles and, unfortunately, you have to wade through the KB numbers to get the right patches. These are the ones to avoid:

  XP: KB 2478656, KB 2478658, KB 2478663, KB 2518864, KB 2530095, and KB 2518870;

  Vista: KB 2478657, KB 2478659, and KB 2478663, KB 2518863, KB 2518865, and KB 2518870;

  Win7: KB 2478662, KB 2478663, KB 2518867, KB 2518870, and KB 2518869

  Like I said, it’s a mess. If you don’t want to fool around with individual patches, I say avoid the current round altogether: pick them up next month.

  At this point, I would also avoid Office 2010 Service Pack 1. There’s no benefit in it, if you’ve kept up on patching Office 2010.

  The other Microsoft patches look like they’re good to go.

  By all means, make sure you download and run the Malicious Software Removal program, and apply Microsoft Security Essentials updates.

  We’re at MS-DEFCON 4: There are isolated problems with current patches, but they are well-known and documented here. Check this site to see if you’re affected and if things look OK, go ahead and patch.There are isolated problems with current patches, but they are well-known and documented here. Check this site to see if you’re affected and if things look OK, go ahead and patch.

  Windows Patches/Security June 2011 Black Tuesday, NET