• March Madness begins

    Home » Forums » Newsletter and Homepage topics » March Madness begins

    Author
    Topic
    #2648151

    Ready or not, here comes the March updates for Windows. Windows 10 22H2 gets KB5035845 Known issues include:  “Copilot in Windows (in preview) is not
    [See the full post at: March Madness begins]

    Susan Bradley Patch Lady/Prudent patcher

    3 users thanked author for this post.
    Viewing 27 reply threads
    Author
    Replies
    • #2648169

      AKB 2000003 has been updated for Group B Win7 and Win8.1 on Mar 12, 2024.

      See #2648110 and #2648115 for information on Win7 and Win8.1 updates (Logged in Member access required).

      2 users thanked author for this post.
    • #2648157

      well March Madness begins and the problems with KB5034440 & KB5034441 still go on, even in March as windows update continues to offer them.

      continuing to hide/block KB5034440/KB5034441 using wushowhide.diagcab or wumgr on my end

    • #2648174

      1507 KB5035858
      1607 KB5035855
      1809 KB5035849

    • #2648178

      W10 22H2 …. Feb-Mar CUs for me have been under 20 min … Today KB5035845 / SSU / MSRT …..

      W10 Pro 22H2 / Hm-Stdnt Ofce '16 C2R / Macrium Pd vX / GP=2 + FtrU=Semi-Annual + Feature Defer = 1 + QU = 0

      1 user thanked author for this post.
    • #2648186

      I wonder if Windows 10 22H2 KB5035845 might also address the problem from last month with KB5034763? Same behavior as the Win 11 update is supposed to fix:

      Windows 11 23H2 and 22H2 KB5035853.  This fixes the issue seen in earlier updates: “This update addresses a known issue that might affect the February 2024 security and preview updates. They might not install, and your device might stop responding at 96%. The error code is “0x800F0922.” The error message is, “Something did not go as planned. No need to worry – undoing changes. Please keep your computer on.”

      Except for stalling at 94%, this is the exact issue I had trying to install KB 5034763 last month. Would be nice if MS included a fix for whatever caused that problem, too.

      • #2648216

        KB5035845 is a CU update so you don’t have to install Feb. KB5034763.

        1 user thanked author for this post.
        • #2648247

          KB5035845 is a CU update so you don’t have to install Feb. KB5034763.

          Yes, I am not even going to try, but I am concerned that the same thing is going to happen with KB5035845 if I can’t ever figure out what the problem was for KB5034763.

    • #2648222

      Hardened Windows user:

      KB5035853 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems
      KB5036451 .NET 7.0.17 Security Update for x64 Client
      KB890830 Windows Malicious Software Removal Tool x64 – v5.122

      No hiccups, other than Edge getting re-installed, but Revo Uninstaller made short work of it.

      Now running Windows 11 Pro Version 23H2 (OS Build 22631.3296) I’ll wait for the push on my NAS and E5420.

      Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
      We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.
      We were all once "Average Users".

    • #2648223

      I also ran into this:

      2024-03 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5035849) – Error 0xd0000034

      1 user thanked author for this post.
      • #2648244

        “0xC0000034 – STATUS_OBJECT_NAME_NOT_FOUND”

        it probably trying to update component that exist only on Windows 10 1809

      • #2648267

        From Reddit – Patch Tuesday Megathread (2024-03-12) discussion:

        Indications are that KB5035849 failing with error – Error 0xd0000034 occurs via install through Microsoft Update but without issues via manual install through Microsoft Catalogue or install through WSUS.

        HTH.

        1 user thanked author for this post.
    • #2648246

      Installed KB5035853 and MSRT for Windows 11 23H2.  Installation seemed somewhat slow.  No Edge, no CoPilot , no nuthin.  All good so far.

      Mark

       

    • #2648279

      I can confirm server 2019 all error from windows update with error 0xd000034 KB5035849.

      Downloaded kb from windows catalogue and installs fine on 3 2019 servers thus far.

      server 2016 and 2022/21h1 all install from windows update no issues thus far

      Still getting offered 4111 for winre on my win10 which fails.

       

      honestly microsoft need to get their act together

      1 user thanked author for this post.
      • #2648281

        Winre 4441 patch think i got number wrong.

    • #2648304

      No zero-days, but there’s that MS CVE at 9.8…which will keep Azure SysAdmins busy.

      https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2024-21334

    • #2648325

      I did the update for my Win10 PC. Then I opened Chrome, used it and closed it. Suddenly a popup in the bottom-right corner of the screen. It was asking if I want to change the search engine in Chrome to GPT-4. I panicked a little bit. I opened task manager. The process was something like BingInstaller or something. It was signed by Microsoft. I was releived. I clicked “No, thanks”. The executable seems gone from my drive. LOL

       

      • #2648327

        I was wrong, C:\Windows\Temp\MUBSTemp\BingChatInstaller.EXE is still there, but it requires admin rights.

      • #2648553

        I haven’t yet installed the March Windows updates, but when I visited the Chrome Web Store, I saw a pop-up in the lower right corner of my screen advertising Bing Chat. At first, I thought the ad was coming from the Web Store itself. But I clicked on the browser window and the Bing Chat ad disappeared, or so I thought. When I closed the browser, the ad was still there. I used Sysinternals Process Explorer to determine which process was responsible and terminate it. Then I used FileASSASSIN to remove the adware (BingChatInstaller.exe and the MUBSTemp folder). Finally, I opened Sysinternals Autoruns to disable the startup item.

    • #2648394
      Devices running Windows Server 2019 and LSTC editions of Windows 10, version 1809 attempting to install the March 2024 security update, released March 12, 2024 (the Originating KBs listed above) might face issues during the download process via the Windows Update and Windows Update for Business channels. The download will fail with error code ‘0xd000034’.
      Workaround: The update can be downloaded from the Microsoft Update Catalog and Windows Server Update Services (WSUS) channels.
      Next steps: We are working on a resolution for this issue and will provide more information when available.

      Susan Bradley Patch Lady/Prudent patcher

      3 users thanked author for this post.
    • #2648422
      1 user thanked author for this post.
    • #2648455

      It should be noticed that there are 2 versions of Windows 10/11.
      Versions for EU’s DMA and versions for the rest of the world.
      With this come 2 versions on monthly updates.

      2 users thanked author for this post.
    • #2648497

      2024-03 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5035853)

      2024-03 .NET 8.0.3 Security Update for x64 Client (KB5036452)

      2024-03 .NET 7.0.17 Security Update for x64 Client (KB5036451)

      Windows Malicious Software Removal Tool x64 – v5.122 (KB890830)

      All were installed without incident. Now running Windows 11 Pro 22631.3296

      --Joe

    • #2648546

      Is there no .NET update for Windows 10 this month?

      • #2648547

        I’ve updated 2 win 10 machines.  No NET updates for either one.

        Desktop Asus TUF X299 Mark 1, CPU: Intel Core i7-7820X Skylake-X 8-Core 3.6 GHz, RAM: 32GB, GPU: Nvidia GTX 1050 Ti 4GB. Display: Four 27" 1080p screens 2 over 2 quad.

      • #2648548

        Non-security content: MS Software Update Services

        2024-03 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 10 Version 22H2, Windows 10 Version 21H2, Windows 10 Version 21H1, and Windows 10 Version 20H2 (KB5036032)

        • #2648577

          Non-security content: MS Software Update Services 2024-03 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 10 Version 22H2, Windows 10 Version 21H2, Windows 10 Version 21H1, and Windows 10 Version 20H2 (KB5036032)

          Hi PKCano:

          I haven’t tried installing the March 2024 Patch Tuesday updates for my Win 10 Pro v22H2 machine yet, but If I click the link to https://support.microsoft.com/help/5036032 in that article I get a “Sorry, page not found” message.

          If there was a March 2024 update released for the Win 10 v22H2 .NET Framework an announcement should have been posted in the .NET blog at https://devblogs.microsoft.com/dotnet/ (e.g., like the .NET Framework February 2024 Security and Quality Rollup Updates announcement that was posted in that blog last month.

          There is also no March 2024 update for Win 10 v22H2 .NET Framework listed in the release notes for .NET Framework Updates for Windows 10 Version. 22H2.
          ————–
          Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v123.0.1 * Microsoft Defender v4.18.24010.12-1.1.24020.9 * Malwarebytes Premium v4.6.10.316-1.0.2286 * Macrium Reflect Free v8.0.7783

          1 user thanked author for this post.
          • #2648580

            Copying info from MS site linked. ???
            Doesn’t show up now in the MS Catalog either.

            Maybe that’s an early notice for the Preview later this month considering the 5036🙂

            • #2648586

              @PKCano

              I just now saw the same thing you did on the “Description of Software Update Services…” page, and the update is still listed on that page right where you probably saw it.

              BUT, as @lmacri pointed out, I got a 404 error when I tried going to that page which is linked to on the Software Update Services page.

              Since the title of the update doesn’t contain the word “Preview” anywhere in it, perhaps they pulled the update at the last second due to issues they found at the last minute and forgot about the listing for it on the Software Update Services page??

              If it is indeed a preview, well someone screwed up royally on this one by releasing it before the week C or D date for March and didn’t bother to include the word “Preview” in the update’s title.

              Time will tell, I guess, on the final fate of it.

              P.S. Like @lmacri , I haven’t been offered it either.

    • #2648598

      So far, I have updated four Win 10 Pro 22H2 “canary” machines, and one semi-canary machine with KB 5035845.

      Two machines with Office Pro 2016 C2R also updated to v2402 (Build 17328.20184)

      No obvious issues seen yet. Only one was semi-stress tested so far. If I see anything untowards I will update.

      YMMV

      Basic research is what I am doing when I don't know what I am doing - Werner Von Braun

    • #2648655

      Is there no .NET update for Windows 10 this month?

      2024-03 .NET 6.0.28 Update for x64 Client (KB5036450) was delivered to my two Win10/Pro, 22H2 machines. GitHub <here> says “NET 6.0.28 release carries non security fixes.” I didn’t used to get non-security patches, but that doesn’t seem to be WU’s practice anymore.

      No .NET Framework though.

      • #2648684

        I didn’t used to get non-security patches, but that doesn’t seem to be WU’s practice anymore.

        What’s the setting in Group Policy under Windows Update for Business, specifically the “Select when Preview Builds and Feature Updates are received” setting? Is it enabled? If so, how many days’ delay are set or have you put a date in the “Pause Preview Builds or Feature Updates starting:” field instead?

        My settings have that setting Enabled, with a one day delay set, but no specific date set in the  “Pause Preview Builds or Feature Updates starting:” field. With these settings I’ve yet to receive a preview update of ANY kind, nor have I been offered a non-security .NET Framework update. I can’t speak to the full .NET setups with version 6 or 7, as I haven’t installed either one.

        • #2648812

          … With these settings I’ve yet to receive a preview update of ANY kind, nor have I been offered a non-security .NET Framework update.

          Hi Bob99:

          Does that mean that you did not receive KB5031224 (2023-10 Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 Version 222H2 for x64) with your Oct 2023 Patch Tuesday updates and / or KB5034685 (2024-02 Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 Version 222H2 for x64) with your Feb 2024 Patch Tuesday updates?

          Both these .NET Framework updates had no security improvements but I received both KB5031224 and KB5034685, in spite of the fact that I have the same Group Policy settings as you at Windows Update for Business | Select When Preview Builds and Feature Updates Are Received (see attached image).

          I have never been offered a Preview update with these Group Policy settings, but prior to October 2023 I was not receiving .NET Framework updates that did not include a security improvement. See my 15-Feb-2024 post # 2638118 in Susan Bradley’s February 2024 Patches for Windows for further details.
          ———–
          Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v123.0.1 * Microsoft Defender v4.18.24010.12-1.1.24020.9 * Malwarebytes Premium v4.6.10.316-1.0.2286 * Macrium Reflect Free v8.0.7783

          1 user thanked author for this post.
          • #2649520

            Hi @lmacri !

            Upon further inspection and research, I do indeed have both of those updates installed.

            The one from February, however, does have a security update in it that was an out-of-band release a few days prior to the preview update for .NET Framework that was released in, I believe, the “D” week of January. The February update says that it doesn’t have any new security updates since the release of the preview update, which is true since there were none released between February’s Patch Tuesday and the “D” week of January.

            So, the .NET out-of-band security patch was released and incorporated by default into the D week preview released at the end of January since that is a roll-up type of release, and by default that D week release was then incorporated into February’s Patch Tuesday release.

            I seem to recall seeing mention of the out of band security patch for .NET Framework here in AskWoody, but I don’t recall just which thread it was in.  🙁

            However, I was unable to find any such occurrence for the October update for .NET Framework, so maybe MS has indeed changed their policies with regards to the .NET releases and is now giving them to those who only wanted releases with security updates in them as well as everyone else.

            I suppose going forward that we can look at the bulletin that accompanies the .NET Framework monthly updates, and if there’s no security update in them we could then hide them and not install them, our individual choice.

            1 user thanked author for this post.
        • #2648993

          What’s the setting in Group Policy under Windows Update for Business, specifically the “Select when Preview Builds and Feature Updates are received” setting? Is it enabled? If so, how many days’ delay are set or have you put a date in the “Pause Preview Builds or Feature Updates starting:” field instead?

          My settings have that setting Enabled, with a zero day delay set, but no specific date set in the “Pause Preview Builds or Feature Updates starting:” field. With these settings I’ve yet to receive a Preview update of ANY kind, but I was offered a non-security .NET Framework update for Oct, 2023 (KB5031224) and Feb 2024 (KB5034685).

          • #2649054

            @lmacri may refute this, but in my experience….

            Updates offered on Patch Tuesday are NOT considered Previews. The metadata puts them with the monthly Security Updates, even as in the case of the Feb. 2024 .NET Framework update where there was no Security content.

            The Group Policy setting should keep you from getting updates that are not issued with the Security Updates on Patch Tuesday.

            That has been my experience.

            1 user thanked author for this post.
            • #2649082

              Updates offered on Patch Tuesday are NOT considered Previews.

              agreed, although in my mind, they’re now mass public beta’s and apparently betta when the MS-Defcon numerical value is raised 😉

              Windows - commercial by definition and now function...
            • #2649083

              The Group Policy setting should keep you from getting updates that are not issued with the Security Updates on Patch Tuesday.

              but doesn’t keep you from getting the non-security updates on Patch Tuesday?

              True, I don’t get non-Patch-Tuesday updates. I get only Week B ones. And the rare O-O-B ones.

              @lmacri may refute this, but in my experience….

              I’m like @Imacri: I received KB5031224 (2023-10 Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 Version 222H2 for x64) with my Oct 2023 Patch Tuesday updates and KB5034685 (2024-02 Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 Version 222H2 for x64) with my Feb 2024 Patch Tuesday updates, even though these had no security improvements.

              And like or unlike @lmacri (haven’t yet see any post from them about it), I received KB5036450 2024-03 .NET 6.0.28 Update for x64 Client, even though it has no security improvements, either.

            • #2649154

              And like or unlike @lmacri (haven’t yet see any post from them about it), I received KB5036450 2024-03 .NET 6.0.28 Update for x64 Client, even though it has no security improvements, either.

              Hi WCHS:

              Sorry, I won’t be able provide any relevant feedback because I removed the MS .NET Runtime 6.0.27 (x64) and MS Windows Desktop Runtime 7.0.16 (x64) from my Win 10 Pro v22H2 machine last week since I no longer have any installed software that requires those runtimes.

              I still have the MS Windows Desktop Runtime 8.0.2 (x64) installed and expect to receive this month’s KB5036452 (2024-03 .NET 8.0.3) update since the MS Blog post at .NET March 2024 Updates – .NET 8.0.3, 7.0.17, .NET 6.0.28 shows that the .NET 7.0.17 and .NET 8.0.3 updates both include security improvements.
              ———–
              Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v123.0.1 * Microsoft Defender v4.18.24010.12-1.1.24020.9 * Malwarebytes Premium v4.6.10.316-1.0.2286 * Macrium Reflect Free v8.0.7783

              1 user thanked author for this post.
            • #2649165

              since I no longer have any installed software that requires those runtimes.

              How do you go about learning what installed software you have that no longer requires certain runtimes?

              Maybe, start another topic to answer, if you can?

            • #2649390

              How do you go about learning what installed software you have that no longer requires certain runtimes?

              Hi WCHS:

              I just sent you a private message.  If you don’t find any useful information in that PM then I’d suggest you start a new topic to see if anyone else knows an easy way of doing this.

            • #2660574

              Hi @lmacri:
              I’ve read your Apr 16 response to Retired Geek #2660507 about a .NET (Core) Runtime’s being only installed if it is required for a software program that is used on one’s system and that these Runtimes are not backwards compatible. You noted some Runtimes that you were able to safely uninstall because programs on your system were no longer using them or because you no longer had the program installed.

              As you know, I am running Dell’s SupportAssist (now version 4.0.x). which requires Microsoft .NET Runtime 6.0.x (currently 6.0.28; I have not installed the April 6.0.29 yet). {Yes, I know that it’s ridiculous that Dell continues to develop new versions of SA that require 6.0, when support for 6.0 is going to expire 6 months from now, i.e., in November 12, 2024!!}

              In Apps & features, I have a Microsoft .NET Runtime – 5.0.17 (dated May 20, 2022). I’m almost certain that it is a Runtime version that was required by some earlier version of SA. In fact, .NET Runtime 5.0 is no longer supported.

              I’d like to clean up these Runtimes if they are no longer needed.
              Do you think that it’s safe to uninstall .NET Runtime 5.0.17?

              1 user thanked author for this post.
            • #2660586

              As you know, I am running Dell’s SupportAssist (now version 4.0.x). which requires Microsoft .NET Runtime 6.0.x …In Apps & features, I have a Microsoft .NET Runtime – 5.0.17 (dated May 20, 2022). I’m almost certain that it is a Runtime version that was required by some earlier version of SA. In fact, .NET Runtime 5.0 is no longer supported. I’d like to clean up these Runtimes if they are no longer needed. Do you think that it’s safe to uninstall .NET Runtime 5.0.17?

              Hi WCHS:

              Just to clarify, Dell released a SupportAssist v3.11.4.29 installer on 23-Jun-2022 that required a .NET (Core) Runtime v5.0.x, but .NET (Core) Runtime v5.0.17 had already reached end of support a month earlier on 10-May-2022. In that particular instance, SupportAssist users had to use SupportAssist v3.x with an unsupported .NET Runtime (Core) v5.0.17 for 5 months before Dell finally released SupportAssist v3.12.3.5 on 11-Oct-2022 that was compatible with .NET (Core) Runtime v6.0.x.

              The release notes <here> for the new SupportAssist v4.0.x (rel. 01-Feb-2024) state the minimum system requirement has changed again and is now .NET Desktop Runtime v6.0.x. This is a different edition of .NET v6.0 (see the download page at https://dotnet.microsoft.com/en-us/download/dotnet/6.0/runtime) that includes the “base” .NET (Core) Runtime v6.0 that can run console apps plus some additional files required to run desktop apps. Hopefully, Dell will release a SupportAssist v4.x version that requires .NET Desktop Runtime v7.0.x long before support for .NET Desktop Runtime v6.0.x ends on 12-Nov-2024. NOTE: I uninstalled  all Dell SupportAssist-related software  from my Insipron 5584 over a year ago.

              As I stated in the private messages I sent you starting 15-Mar-2024 titled When is it Safe to Uninstall a MS .NET Runtime?, you can safely uninstall your unsupported .NET (Core) Runtime v5.0.17 as long as you do not have other software that requires this outdated .NET v5.0 software. If you aren’t sure, the worst case scenario is that you uninstall .NET (Core) Runtime v5.0.17 and it breaks a software program that forces you to reinstall .NET (Core) Runtime v5.0.17.  However, any software you might have that still requires an unsupported .NET (Core) Runtime v5.0.17 is unsafe and you really shouldn’t be using it anyway.
              ————-
              Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4291 * Firefox v124.0.2 * Microsoft Defender v4.18.24030.9-1.1.24030.4 * Malwarebytes Premium v4.6.12.323-1.0.2309 * Macrium Reflect Free v8.0.7783 * Dell Update for Windows Universal v5.2.0 * MyDell v2.2.6.0

              2 users thanked author for this post.
            • #2660626

              The release notes <here> for the new SupportAssist v4.0.x (rel. 01-Feb-2024) state the minimum system requirement has changed again and is now .NET Desktop Runtime v6.0.x.</here>

              Thanks for pointing out .NET Desktop Runtime v6.0.x. I didn’t take notice of the ‘Desktop’ in the name. Now, I know why I have both: .NET Runtime 6.0.28 AND .NET Desktop Runtime 6.0.28 — the former was installed by WU and the latter was installed by the latest version of SA.

              Hopefully, Dell will release a SupportAssist v4.x version that requires .NET Desktop Runtime v7.0.x long before support for .NET Desktop Runtime v6.0.x ends on 12-Nov-2024.

              It’s my understanding that .NET Desktop Runtime 7.0 will lose support on May 14, 2024 – i.e., sooner than .NET Desktop Runtime 6.0 will on Nov 12, 2024. So, hopefully, a new version of SA will be requiring Long Term Support .NET Desktop Runtime 8.0, which doesn’t lose support until Nov 10, 2026.

              Thanks for reminding me of your PM starting March 15, 2024. At the time, I was thinking that I would definitely need to know what programs were requiring what runtimes before I uninstalled any — because if I uninstalled .NET Runtime 5.0.17, I might never know what program was broken, simply because I never happened to run the program that needed it. But, now the rationale for uninstalling is clearer – if there’s a program that is requiring it, it shouldn’t be run anyway, because 5.0 has long been out of support. So, I don’t really need to know what program is asking for it – whatever it is, it’s risky/out-dated and shouldn’t be run anyway — period.

            • #2660640

              You might start with the .NET Uninstall Tool…

              https://learn.microsoft.com/en-us/dotnet/core/additional-tools/uninstall-tool?tabs=windows

              After installation, run dotnet --info to find all of the SDKs and runtimes installed.
              
              Then, run dotnet-core-uninstall list to find what can be uninstalled with the tool.
              1 user thanked author for this post.
            • #2660689

              Then, run
              dotnet-core-uninstall list
              to find what can be uninstalled with the tool.

              It doesn’t work.
              command-doesnt-work

              Why use ‘the tool’? Why not uninstall it via Control Panel>Programs and Features or Apps & features?
              in-uninstall-updates

              A-and-F

            • #2649156

              This is where the documentation gets confusing.

              https://devblogs.microsoft.com/dotnet/march-2024-updates/

              According to that it does have security fixes included BUT when you dig into the MSRC info https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2024-21392 it’s 7 and 8 that have the security issue.

              Per https://github.com/dotnet/core/blob/main/release-notes/6.0/cve.md February .net 6 had security issues.

              The good news is that these updates are well behaved.

              Susan Bradley Patch Lady/Prudent patcher

            • #2649177

              Per https://github.com/dotnet/core/blob/main/release-notes/6.0/cve.md February .net 6 had security issues.

              And the one for March .net 6 says there are no security fixes > https://github.com/dotnet/core/blob/main/release-notes/6.0/6.0.28/6.0.28.md

              Yet, WU delivered it to my Win10/Pro 22H2 device. Which I think is strange, since I thought I had GP settings to preclude it, if there were no security improvements.

              You’re right … you really have to dig for the security info for these .NET 6.0.x releases.

            • #2649363

              This is where the documentation gets confusing. https://devblogs.microsoft.com/dotnet/march-2024-updates/ According to that it does have security fixes …

              Hi Susan:

              I can’t see documentation in any of those links that says that the March 2024 .NET 6.0.28 includes a security improvement.

              For example, both CVEs listed in the blog post at https://devblogs.microsoft.com/dotnet/march-2024-updates/ state that “Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 7.0 and .NET 8.0“.
              ———–
              Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v123.0.1 * Microsoft Defender v4.18.24010.12-1.1.24020.9 * Malwarebytes Premium v4.6.10.316-1.0.2286 * Macrium Reflect Free v8.0.7783

            • #2649090

              The Group Policy setting should keep you from getting updates that are not issued with the Security Updates on Patch Tuesday.

              Hi PKCano:

              In my experience that Group Policy setting could also prevent Win 10 Pro users from getting .NET Framework updates issued on Patch Tuesdays (i.e., .NET Framework updates that were not Previews) if they did not include a security improvement, or at least that was the case until some time around Oct 2023.

              I’m not sure which exact combination of Windows Update settings at Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business used to prevent Windows Update from offering .NET Framework updates on Patch Tuesdays if they did not include a security improvement, but the general consensus in doneager’s 09-Jun-2021 .NET Update Confusion was that it was a combination of enabling both the Select When Preview Builds and Feature Updates Are Received setting and the Target Feature Update Version setting.

              As Susan Bradley noted in her 07-Sep-2021 post # 2388500 in donnegars’ topic:

              If you set any of the normal deferrals, you get treated like a “business” patcher and only get offered when a .NET update gets released with a new security update.

              What you are experiencing is indeed “normal”.

              As I noted last month in my 19-Feb-2024 post # 2639561 of Susan Bradley’s February 2024 patches for Windows, I suspect I started receiving .NET Framework updates without a security improvement on Patch Tuesdays around mid to late 2023 when Microsoft removed the option to select a delivery channel (e.g., Semi Annual Channel) in the Select When Preview Builds and Feature Updates Are Received setting on my Win 10 Pro v22H2 machine.

              As far as I can tell, delivery of .NET Framework Monthly CU updates that do not have a security update is a relatively recent phenomenon on my own machine. I’m guessing this started after Microsoft removed the option to select the “Windows Readiness Level for Updates You Receive” (e.g., Semi-Annual Channel) from the LGPE setting at Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select When Preview Builds and Feature Updates Are Received.

              The dropdown box to select a delivery channel for Windows Updates in that LGPE setting can still be seen in the second (now outdated) 24-Jun-2020 image in post # 2275043 of PKCano’s AKB2000016: Guide for Windows Update Settings for Windows 10, but that dropdown box is no longer present in my current LGPE setting (see attached image).

              I’ve re-attached that image here.
              ————
              Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v123.0.1 * Microsoft Defender v4.18.24020.7-1.1.24020.9 * Malwarebytes Premium v4.6.10.316-1.0.2286 * Macrium Reflect Free v8.0.7783

    • #2648739

      Imaged a Win 10 22H2 system, and installed the March updates.

      Installs went well, and no issues so far.

      1 user thanked author for this post.
      Geo
    • #2648744

      Windows 10 Pro 22H2 March update.
      All is OK

      1 user thanked author for this post.
      Geo
    • #2649071

      March 2024 experience report:
      2 off W10 Pro x64 22H2 systems
      KB5035845 CU installed and winsxs regeneration confidently done. No problems this month. Installation took an extra 10mins from the normal times of 20-25mins on Haswell & Ivybridge systems.
      1 off W10 Pro x86 22H2 the same scenario with no issues.

      Windows - commercial by definition and now function...
    • #2649397

      Hi Susan:

      Windows Update successfully installed all updates offered for the March 2024 Patch Tuesday on my Win 10 Pro v22H2 laptop, and I haven’t observed any negative effects so far. This includes:

      • KB5035845: 2024-03 Cumulative Update for Win 10 Version 22H2 for x64 (OS Build 19045.4170)
      • KB5036452: 2024-03 .NET 8.0.3 Security Update for x64 Client
      • KB890830 : Windows Malicious Software Removal Tool x64 – v5.122

      As usual, after my updates finished installing and I clicked the “Restart Now” button the final installation / configuration reached “Working on updates – 30% Complete” before my system re-booted, ran to “Working on updates – 100% Complete“, and landed me back on my lock screen.

      Like other Win 10 v22H2 users posting in this thread have reported, I did not receive a .NET Framework 3.5, 4.8 and 4.8.1 update this month with my other March 2024 Patch Tuesday updates.

      There is no indication that Copilot was pushed out to my system this month (i.e., no Copilot for Windows button on the far right of my taskbar, no new setting at Settings | Personalization | Taskbar to enable / disable Copilot, and no app at Settings | Apps | Apps and Features that includes “copilot”).
      ————
      Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4170 * Firefox v123.0.1 * Microsoft Defender v4.18.24020.7-1.1.24020.9 * Malwarebytes Premium v4.6.10.316-1.0.2286 * Macrium Reflect Free v8.0.7783

      1 user thanked author for this post.
      Geo
    • #2650269

      Updated three Win10 22H2 installations: one hardware install on a Dell Studio XPS 1340 laptop (old), one in a Parallels 18 VM on 2013 Intel Ivy Bridge 15′ MacBook Pro, and one in a Parallels 18 VM on a 2017 Intel Kaby Lake 21.5″ iMac4K. Most of the UWP Apps and Edge have been removed, CoPilot is blocked, no new Outlook, no visible printer problems.
      MSRT
      2024-03 CU KB5035845 Build 19045.4170

      Updated three Win11 22H2 installations: one hardware install on a two-year-0ld low-end HP desktop (tor testing, one in a Parallels 19 VM on a 2020 M1 MacMini, and one in a Parallels 19 VM on a 2023 M2Max 16″ MacBookPro. Most of the UWP Apps and Edge have been removed, CoPilot is blocked, no new Outlook, no visible printer problems.
      MSRT (on HP desktop only, ARM on Mac Silicon does not seem to get this)
      2024-03 CU KB5035853 Build 22621.3296

      Updated one Win10 22H2 hardware installation on a Dell 5th gen Intel desktop for the Front Desk of the building where I live (24/7 use). I decided to hide KB5034441 on this one last month because I was unable to expand the WinRE partition and I didn’t want to take the chance of the updates going pear shaped. Edge and CoPilot are blocked.
      MSRT
      2024-03 CU KB5035845 Build 22621.4170

      No problems so far.

      1 user thanked author for this post.
    • #2652569

      Problem with all MS server updates this month: severe memory leak in service causing spontaneous restarts..
      https://m.slashdot.org/story/426397

      Basic research is what I am doing when I don't know what I am doing - Werner Von Braun

    • #2652645

      severe memory leak in service causing spontaneous restarts..

      Emergency fix released yesterday…

      https://www.bleepingcomputer.com/news/microsoft/microsoft-releases-emergency-fix-for-windows-server-crashes/

      • #2653554

        Emergency fix released yesterday…

        Yes. Thanks. I knew that, but I was posting from a phone in a hurry, so I made it brief. The article on slashdot mentions that there is a hotfix.

        It’s a bad error, but fortunately it is limited to specific circumstances/configurations that I don’t have.

        Basic research is what I am doing when I don't know what I am doing - Werner Von Braun

    • #2654758

      Finally, I opened Sysinternals Autoruns to disable the startup item.

      I did not see a startup item in Autoruns 14.11 for BingChatInstaller or BCILauncher.

      Please post the locations that you found for their startup items.  Thanks.

    • #2660682

      It’s my understanding that .NET Desktop Runtime 7.0 will lose support on May 14, 2024 – i.e., sooner than .NET Desktop Runtime 6.0 will on Nov 12, 2024. So, hopefully, a new version of SA will be requiring Long Term Support .NET Desktop Runtime 8.0, which doesn’t lose support until Nov 10, 2026.

      Hi WCHS:

      Thanks for the reminder. I should have remembered that since the developer of QuickInstaller v0.3.x recently changed the system requirement for this software from .NET Desktop Runtime v7.0.x. to .NET Desktop Runtime v8.0.x. a few weeks ago when QuickInstaller v0.3.8829.15130 was released on 04-Mar-2023.
      ———
      Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4291 * Firefox v124.0.2 * Microsoft Defender v4.18.24030.9-1.1.24030.4 * Malwarebytes Premium v4.6.12.323-1.0.2309 * Macrium Reflect Free v8.0.7783 * QuickInstaller (Preview) v0.3.8859.20616

    • #2660800

      It doesn’t work.

      Looks like the tool wasn’t installed…

      The path to the executable is C:\Program Files (x86)\dotnet-core-uninstall

      Why use ‘the tool’? Why not uninstall it via Control Panel>Programs and Features or Apps & features?

      There are use cases where the tool might be a better choice.

      https://learn.microsoft.com/en-us/dotnet/core/additional-tools/uninstall-tool?tabs=windows

      However, you can use whatever you like.

       

    Viewing 27 reply threads
    Reply To: March Madness begins

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information: