News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon

Blog Archives

  • Microsoft re-releases buggy July .NET Security Only patches

    Posted on October 13th, 2020 at 21:17 woody Comment on the AskWoody Lounge

    Microsoft just announced that it has re-issued the buggy July .NET Security Only patches identified as CVE–2020-1147, and covering a gazillion different KBs. Okay, I overspoke. Maybe half a gazillion.

    The bug? Ahem:

    After you apply this update, some applications experience a TypeInitializationException exception when they try to deserialize System.Data.DataSet or System.Data.DataTable instances from the XML within a SQL CLR stored procedure.

    You had to ask.

    Anyway, if you see a .NET patch from July suddenly appear in October, you need to install it, and now you know why.

    UPDATE: @PKCano has the gory details – including KB numbers for the re-released Security Only patches for Win7 and Server 2008 R2 – posted here.

  • Problems with the .NET updates

    Posted on December 16th, 2019 at 06:38 woody Comment on the AskWoody Lounge

    This from Barry Dorrans on Saturday:

    It isn’t clear to me which .NET updates he’s talking about, but Barry knows whereof he speaks. He goes on to say that admins can block the rollout using opt out switches “in the comments in the blog post.” And he’s on vacation.

    I’m going to guess that he’s referring to KB 4533002 but may well be wrong. That patch is still available in the Update Catalog.

    Anybody have more details?

  • Report: The new .NET updates break Veritas Backup Exec

    Posted on August 22nd, 2019 at 06:24 woody Comment on the AskWoody Lounge

    Two days ago, Microsoft released a bunch of patches for .NET Framework 3.5, 4.7.2 and 4.8.

    Now comes word from Günter Born that they’re breaking Veritas Backup Exec.

    The updates (per deskmodder.de):

    They all claim to fix the bug “Addresses a crash that occurs after enumerating event logs in Bass Class Library (BCL).”

    Born has a translation of a German blog post that says after installing the .NET 4.8 patches, Veritas BackupExec 20.4 won’t start. Apparently, rolling back the patch brings Backup Exec back to life.

    Have you had any problems with the .NET patches?

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

    Posted on July 20th, 2018 at 21:56 woody Comment on the AskWoody Lounge

    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

  • What’s happening with Win7 .NET updates?

    Posted on October 21st, 2017 at 13:29 woody Comment on the AskWoody Lounge

    Just got this from reader OC:

    Today I received from MS new updates for my Win 7 Pro, x64, SP1 (to be installed when I decide to), for .NET 4.6.4, 4.61. 4.62, 4.7; another for 4.5.2 and a third for 3.5.1.
    They are, respectively, kb4040973; … 77; … 80 (the first 5 digits are the same for all three.)

    Further, the message says they replace kb2978120 and … 28.

    Now, when going to the MS page with the explanation and I click on the corresponding kb, say …73 to go to the site where there is a link to the MS site where I can download it, that takes me to a page for …86; when I click on the next one, it also takes me to a page for a different kb, and same for the third one. And they are all include fixes, not the ones advertised in the message, but for … 4.7 ! (Which, according to your site, is best avoided, for now.)

    I hope this can be cleared out in the not too distant future. In the meantime, I am keeping this update parked “unticked” in my machine, until that clarification happens, or until postings in your site advise that it is OK to go ahead and install them as they are, or…

  • Why is it so hard to push good .NET patches?

    Posted on July 5th, 2011 at 18:36 woody Comment on the AskWoody Lounge

    Hard to imagine what patching Windows 8 will be like, if MS can’t even get .NET 3.0 patched correctly.

    InfoWorld Tech Watch.

  • Those lousy .NET patches

    Posted on October 28th, 2010 at 12:05 woody Comment on the AskWoody Lounge

    Hey, you think I’m the only one who complains about the ^%$#@! furshlinger .NET patches.

    Susan Bradly has a comprehensive list of what’s wrong with this month’s .NET patches (nevermind last month’s) in the latest Windows Secrets Newsletter, which just hit the stands.

    If you don’ t have a subscription to WSN, you’re missing one of the great bargains on the Web. You set the price – pay what you think it’s worth. You’ll get all of Susan’s stuff (mine, too).