• August 2023 updates are out

    Home » Forums » Newsletter and Homepage topics » August 2023 updates are out

    Author
    Topic
    #2578487

    For Apple devices, while 16.6 was released back on July 24, your device may not have received them yet – or will be installing it shortly. As always,
    [See the full post at: August 2023 updates are out]

    Susan Bradley Patch Lady/Prudent patcher

    7 users thanked author for this post.
    Viewing 14 reply threads
    Author
    Replies
    • #2578506

      AKB 2000003 has been updated for Group B Win7 and Win8.1 on August 8, 2023.

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

      4 users thanked author for this post.
    • #2578489
      1 user thanked author for this post.
    • #2578490

      Detailed info of August 2023 patches over on ghacks.net

      No problem can be solved from the same level of consciousness that created IT- AE
      1 user thanked author for this post.
    • #2578518

      Hardened Windows user:

      KB5029263 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems
      KB5028948 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 22H2 for x64
      KB890830 Windows Malicious Software Removal Tool x64 – v5.116

      No hiccups.

      Now running Windows 11 Pro Version 22H2 (OS Build 22621.2134)

      Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
      We were all once "Average Users". 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.

      3 users thanked author for this post.
      • #2578531

        Same updates and outcome on my NAS.

        Now running Windows 11 Pro Version 22H2 (OS Build 22621.2134)

        Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
        We were all once "Average Users". 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.

    • #2578519

      Crash Test Dummy #1 here.

      Did the updates for “unsupported” PC2 in my signature with Windows 11 Home after making a Macrium Reflect backup first (of course).

      Had a .NET update, the usual Monthly Cumulative Update and a Microsoft Defender Update.

      Don’t know if there was a Malicious Software Removal Tool update because I have those blocked.

      No problems apparent so far. No “unsupported” message or anything like that. Will connect up “supported” PC1 tomorrow and see how that goes when I update it.

      PC1: Gigabyte B560M D2V Motherboard, Intel i5 11400 CPU, 16GB RAM, NVIDIA GeForce GTX 1650 Graphics Card, 1x Samsung 870 EVO 250GB SSD, 1x Samsung 860 EVO 250GB SSD, Windows 10 Professional 22H2 64bit.
      PC2: Asus H81M-PLUS Motherboard, Intel i3-4160 CPU, 16GB RAM, NVIDIA GeForce GTX 1050 Graphics Card, 1x Samsung 870 EVO 250GB SSD, 1x Samsung 860 EVO 250GB SSD, Windows 10 Home 22H2 64bit.

      • #2578530

        Carl, why do you block the Malicious Software Removal Tool updates; any specific reason?

        1 user thanked author for this post.
        • #2578547

          Not really any specific reason.

          Perhaps I don’t really trust MS with what they might consider to be “malicious software” because I seem to recall in the early days of Windows 10 a lot of people were having issues with non malicious software like CCleaner being removed by Windows with no warning whatsoever.

          I don’t think it was the Malicious Software Removal Tool that was doing it though – from memory it was happening during an upgrade to the latest Windows 10 version or upgrades to Windows 10 from Windows 7 or 8.1 but I would still prefer to be safe rather than sorry.

           

          PC1: Gigabyte B560M D2V Motherboard, Intel i5 11400 CPU, 16GB RAM, NVIDIA GeForce GTX 1650 Graphics Card, 1x Samsung 870 EVO 250GB SSD, 1x Samsung 860 EVO 250GB SSD, Windows 10 Professional 22H2 64bit.
          PC2: Asus H81M-PLUS Motherboard, Intel i3-4160 CPU, 16GB RAM, NVIDIA GeForce GTX 1050 Graphics Card, 1x Samsung 870 EVO 250GB SSD, 1x Samsung 860 EVO 250GB SSD, Windows 10 Home 22H2 64bit.

          1 user thanked author for this post.
          • #2578604

            FWIW, I always apply MSRT immediately, manually, and have never had a problem. I defer everything else though. (One reason for doing MSRT separately is that it takes a while and I prefer not to do it while real updates are being done.)

            1 user thanked author for this post.
      • #2578776

        PC1 in my signature (the “supported” one) now updated with no issues so far.

        Both PC’s now ‘locked down’ Windows Update wise until next month before the inevitable “Preview” updates start rolling out, I am not and do not want to be an unpaid tester for MS or anyone else. I can usually hide them with Windows Update Manager (wumgr) of course.

        One of these Patch Tuesdays I am looking forward to MS finally fixing the ‘bug’ which has been in Windows 10 for years and has carried over to Windows 11 where USB connected printers ‘disappear’ from the list of available printers if they’re not switched on for a week or so.

        The drivers are still there and the printer(s) reappear when they’re switched on again but it’s a bit of a nuisance when the default printer changes to Microsoft Print to PDF after the USB printer ‘disappears’ and you haven’t noticed and you then wonder why nothing happens when you try to print something (the default printer needs to be manually changed back to the USB printer after it ‘reappears’ when you turn it on).

        I do remember reading something a couple of years back where MS apparently have some idea as to why this happens but they don’t know how to fix it so far. Sounds about right.

        Perhaps they might want to consider devoting a bit more time and a few more staff to finding a solution to this instead of adding more and more pointless junk to Edge? But, I’ll leave my rant about browsers (Edge, Firefox and Chrome especially) and their never ending weekly ‘stream’ of  (mostly unwanted and useless) updates for another time and place.

         

        PC1: Gigabyte B560M D2V Motherboard, Intel i5 11400 CPU, 16GB RAM, NVIDIA GeForce GTX 1650 Graphics Card, 1x Samsung 870 EVO 250GB SSD, 1x Samsung 860 EVO 250GB SSD, Windows 10 Professional 22H2 64bit.
        PC2: Asus H81M-PLUS Motherboard, Intel i3-4160 CPU, 16GB RAM, NVIDIA GeForce GTX 1050 Graphics Card, 1x Samsung 870 EVO 250GB SSD, 1x Samsung 860 EVO 250GB SSD, Windows 10 Home 22H2 64bit.

    • #2578575

      The Exchange server updates are borking German language installations.  Unclear if others are affected but due to the lack of English (or other) language users complaining about it, might just be specific to them.

      • #2578586

        Posted that on the top of the site.  Not sure if it’s German only or just because they are rolling out patches already.

        Susan Bradley Patch Lady/Prudent patcher

    • #2578588
    • #2578609

      Windows 10 homeuser report for August 2023:

      W10 Pro 22H2 (x64 + x86) all patched without fuss.

      kb5029244 August CU
      kb5029649 NET3.5/ 4.8

      No adverse observations to report..
      SFC (no violations)
      No changes to O&O shutup settings after CU.
      Devices are running well after an [admin] Disk Clean-up with sage switches followed by a superseded purge of the component store and a manually invoked SSD trim.
      OS now sitting on build 19045.3324
      (imaged prior to updates, as ever)

      No problem can be solved from the same level of consciousness that created IT- AE
      2 users thanked author for this post.
      • #2578661

        Devices are running well after an [admin] Disk Clean-up with sage switches

        What are sage switches?

        1 user thanked author for this post.
        • #2578666

          What are sage switches?

          System Agent—sage, for use with Disk Cleanup.  Running “C:\Windows\System32\cleanmgr.exe /sageset:0” (without the quotes), or just “cleanmgr.exe /sageset:0”, cleanmgr opens an extended selection of items to cleanup with a checkbox by each one.  Selecting those you wish to include and then running that command will establish “sageset:0” (that’s zero) as a switch for cleanmgr.

          The other switch is “/sagerun:0” (without the quotes), that is to say, “C:\Windows\System32\cleanmgr.exe /sagerun:0” (or just “cleanmgr.exe /sagerun:0”.  That command will execute the extended cleanup list specified in the sageset:0 command, on all drives/partitions, not just C:\.  The number (0 in this case) doesn’t necessarily have to be 0, that’s your choice.  Click on the link for more information.

          I have a “C:\Windows\System32\cleanmgr.exe /sageset:0” shortcut on my desktop, with its properties set for Run as administrator.  I also have it as a Scheduled Task.

          Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
          We were all once "Average Users". 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.

          2 users thanked author for this post.
        • #2578679

          thanks for the explanation @bbearren.

          @WCHS
          I did a quick Write-up on how to use the facility within Disk Clean-up if this helps.
          Disk Clean-up on steroids so to speak, sans any 3rd party apps, portable or installed.

          No problem can be solved from the same level of consciousness that created IT- AE
          1 user thanked author for this post.
    • #2578629

      Now running Windows 11 Pro Version 22H2 (OS Build 22621.2134)

      2023-08 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5029263)

      2023-08 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 22H2 for x64 (KB5028948)

      2023-08 .NET 6.0.21 Security Update for x64 Client (KB5029688)

      2023-08 .NET 7.0.10 Security Update for x64 Client (KB5029689)

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

      All installed without any issues.

      --Joe

    • #2578641

      A Much Longer install than I ever recall (I Searched for Stuck Win Update per normal Max 40 min went beyond an Hour) — but Win 10 22H2 Pro uneventful beyond that.

      W10 Pro 22H2 / Hm-Stdnt Ofce '16 C2R / HP Envy Desk-Ethernet - SSD-HDD/ i5(8th Gen) 12GB / GP=2 + FtrU=Semi-Annual + Feature Defer = 1 + QU=0

      1 user thanked author for this post.
    • #2578680

      Disk Clean-up on steroids so to speak

      Isn’t Storage Sense Disk like Clean-up on steroids ?

      • #2578687

        Isn’t Storage Sense Disk like Clean-up on steroids ?

        I guess that depends on one’s point of view.

        Storage-Sense

        Perhaps a tie?

        Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
        We were all once "Average Users". 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.

        • #2578698

          In addition to running Storage Sense I have cleared 3GB in WinSXS

          • #2578712

            In addition to running Storage Sense I have cleared 3GB in WinSXS

            Files in this folder might appear to be stored in more than one place in the operating system, but there’s usually only one copy of the file and the rest of the copies are actually hard links. Some tools, such as the File Explorer, determine the size of directories without taking into account that the contained files might be hard linked, which might lead you to think that the WinSxS folder takes up more disk space than it really does.”

            Again, I guess it depends on one’s point of view:

            WinSXS

            And there’s this:

            CMD-WinSXS-1

            Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
            We were all once "Average Users". 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.

            • #2578862

              bbearren,

              Ok, this looked interesting so I tried it and got this:
              ComponentStore-Analyze

              So how to I fix this?

              Tried:

              • DISM /Online /Cleanup-Image /RestoreHealth
              • Running the StartComponentCleanup Scheduled Task under servicing.
                ComponentStore-Servicint

              All to no avail.

              Ideas?

              May the Forces of good computing be with you!

              RG

              PowerShell & VBA Rule!
              Computer Specs

            • #2578885

              RG, have you tried dism /online /cleanup-image /startcomponentcleanup from an elevated Command Prompt?

              BTW, it seems to me that the trigger for the Scheduled Task under Servicing is triggered by Windows Update.  I checked mine and it last ran Tuesday.  Of course, I could very well be wrong on that assumption.

              Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
              We were all once "Average Users". 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.

              1 user thanked author for this post.
            • #2578905

              We have a WINNER!

              Thanks bbearren.

              Winner

              May the Forces of good computing be with you!

              RG

              PowerShell & VBA Rule!
              Computer Specs

            • #2579043

              @RetiredGeek, you can also add the switch /resetbase to the /startcomponentcleanup commandline:
              dism /online /cleanup-image /startcomponentcleanup /resetbase

              The /resetbase switch will remove superseded versions of every component in the component store. This will mean that all existing service packs and updates can no longer be uninstalled after the command is completed.

              Dism.exe runs equally well in an elevated PowerShell, as you no doubt already know.

               

              Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
              We were all once "Average Users". 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.

    • #2578709

      We STILL do not have a patch for all affected version of Office/wordpad for last month’s security vulnerability in Office/html (if you remember it was patched in the M365 versions but not all) instead we have an advisory.

      I read about this defense-in-depth update for Microsoft Word 2016 (32-bit edition) , for Microsoft Excel 2016 (32-bit edition) , for Microsoft Office 2016 (32-bit edition) , and for Microsoft Office 2019 for 64-bit editions .

      They all seem to indicate that this update does not apply to the Retail C2R versions. I am guessing that this will be taken of, if needed, by updating 2016 and 2019 Word/Excel internally in these C2R versions by going to File>Account > Update Options > Enable updates. Is that right?

      As of now, I am Master-Patch-List current (July 24) on these C2R versions.

      • #2578856

        As of now, I am Master-Patch-List current (July 24) on these C2R versions.

        A little off topic – but have you been hit with the seemingly random “Try the New Outlook” button and its annoyances?

        I’m still trying to decide whether to update to current on my MS Office 2016 C2R.

        Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)
    • #2578724

      I guess it depends on one’s point of view

      winsxs1

      winsxs2

    • #2578826

      6 updates.

      Had another restart after 30% at 31% (due to .NET update).
      Updated to 100% + Clean up.

      All is ok.

      1 user thanked author for this post.
    • #2579020

      Hi Susan:

      Windows Update successfully installed the following August 2023 Patch Tuesday updates on my Win 10 Pro v22H2 laptop and I haven’t observed any negative effects so far:

      • KB5029244: 2023-08 Cumulative Update for Win 10 Version 22H2 for x64 (OS Build 19045.3324)
      • KB5029688: 2023-08 .NET 6.0.21 Update for x64 Client
      • KB5029649: 2023-08 Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Win 10 Version 22H2 for x64
      • KB890830 : Windows Malicious Software Removal Tool x64 – v5.116

      As usual, I saw the early “Restart Now” glitch shown in the attached image that always occurs when Windows Update delivers a .NET Framework update with my other my Patch Tuesday updates (see my 16-Jun-2023 post # 2566457 in Ready for June Updates? for a past example) but I checked at Settings | Update & Security | Windows Update and waited until the status of the KB5029244 Quality Update changed to “Pending Restart” before I restarted my system.

      After I clicked the “Restart Now” button the final installation / configuration re-booted my system at “30% Complete” before running to completion (see Alex5723’s post # 2578698 for a similar observation using WUMgr), but I have no idea what triggered the second re-boot. I don’t usually pay close attention to what happens once I’ve clicked “Restart Now” so this second system restart might have happened before and I just never noticed it.
      ————
      Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.3324 * Firefox v116.0.2 * Microsoft Defender v4.18.23070.1004-1.1.23070.1005 * Malwarebytes Premium v4.5.34.275-1.0.2102 * Macrium Reflect Free v8.0.7279

    Viewing 14 reply threads
    Reply To: August 2023 updates are out

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

    Your information: