• September 30, 2022—KB5017389 (OS Build 22621.608) Preview

    Home » Forums » AskWoody support » Windows » Windows 11 » Windows 11 version 22H2 » September 30, 2022—KB5017389 (OS Build 22621.608) Preview

    • This topic has 16 replies, 5 voices, and was last updated 2 months ago.
    Author
    Topic
    #2484473

    https://support.microsoft.com/en-us/topic/september-30-2022-kb5017389-os-build-22621-608-preview-62f353a0-696a-49d8-a78f-a14910f30ae3

    OS Build 22621.608
    Windows 11 servicing stack update – 22621.378

    Highlights
    Addresses issues that cause updates to the Microsoft Store to fail.

    Updates the start date for daylight saving time in Chile. It will start on September 11, 2022 instead of on September 4, 2022.

    Addresses an issue that affects the font of three Chinese characters. When you format these characters as bold, the width size is wrong.

    Addresses an issue that forces the IE mode tabs in a session to reload.

    Addresses an issue that successfully opens a browser window in IE mode to display a PDF file. Later, browsing to another IE mode site within the same window fails.

    Adds more dynamic Widgets content to your taskbar with notification badging. When you open the Widgets board, a banner appears at the top of the board. It provides more information about what triggered the notification badge.

    Addresses an issue that affects Dual SIM calling. If you select no SIM on your phone and initiate a call on your device, Dual SIM functionality does not work.

    Addresses an issue that affects some apps that were not signed by the Microsoft Store. You must reinstall them after you upgrade the OS….more

    Viewing 0 reply threads
    Author
    Replies
    • #2485637

      KB5017389 (OS Build 22621.608) Preview fails to install on my PC.  I’ve tried it three times, it gets to about 65% after a couple of reboots then “Something went wrong” and backs out.  Installed updates in Windows update shows it to be installed, but also shows it as being ready to Download and install.

      To clean that mess up, I restored drive images for Windows 10, ran dism /online /cleanup-image /restorehealth and then sfc /scannow.  SFC found and corrected corrupted files.  Next I mounted the 22H2 ISO and ran an in-place upgrade.  I’m now back to Windows 11 Pro Version 22H2 (OS Build 22621.525), with my usual customizations.  I also blocked Preview updates via Group Policy.

      Windows update has KB5017389 parked and waiting to Download and install, but I’m leaving it there for the time being, and I’ll make some fresh drive images of this rejuvenated setup.

      Create a fresh drive image before making system changes/Windows updates, in case you need to start over!
      We all have our own reasons for doing the things that we do. We don't all have to do the same things.

      1 user thanked author for this post.
      • #2485724

        You used 22621.525 installation media?
        it’s apparently been created with Component Cleanup executed, and this prevent installing 22621.608 (missing source files for PSFX)

        if the next patch tuesday Cumulative Update also fail to install, then the only fix is to create updated 22621.608 installation media yourself (using 22621.328 as source), and perform in-place upgrade

        • #2485747

          You used 22621.525 installation media? it’s apparently been created with Component Cleanup executed, and this prevent installing 22621.608 (missing source files for PSFX)

          Evidently you completely misread my reply.  This …

          KB5017389 (OS Build 22621.608) Preview fails to install on my PC. I’ve tried it three times, it gets to about 65% after a couple of reboots then “Something went wrong” and backs out. Installed updates in Windows update shows it to be installed, but also shows it as being ready to Download and install.

          … occurred running Windows 11 Pro Version 22H2 (OS Build 22621.521).  Then,

          To clean that mess up, I restored drive images for Windows 10, ran dism /online /cleanup-image /restorehealth and then sfc /scannow. SFC found and corrected corrupted files. Next I mounted the 22H2 ISO and ran an in-place upgrade. I’m now back to Windows 11 Pro Version 22H2 (OS Build 22621.525), with my usual customizations. I also blocked Preview updates via Group Policy. Windows update has KB5017389 parked and waiting to Download and install, but I’m leaving it there for the time being, and I’ll make some fresh drive images of this rejuvenated setup.

          The “… now back to Windows 11 Pro Version 22H2 (OS Build 22621.525)” is clean, without the “Installed updates in Windows update shows it to be installed, but also shows it as being ready to Download and install” conundrum.  Not wanting to go through that yet another time, I’m holding off until “Preview” is not  part of the update nomenclature.

          I downloaded and used the ISO primarily because I had not yet obtained one for 22H2. Incidentally, this is the first Preview update that has failed for me.

          I’m not anticipating any further difficulties.

          Create a fresh drive image before making system changes/Windows updates, in case you need to start over!
          We all have our own reasons for doing the things that we do. We don't all have to do the same things.

          • #2485879

            You used 22621.525 installation media?

            Evidently you completely misread my reply.

            Isn’t the answer to that question, “Yes.”?

            Next I mounted the 22H2 ISO and ran an in-place upgrade.  I’m now back to Windows 11 Pro Version 22H2 (OS Build 22621.525),

            Windows 11 Pro version 22H2 build 22621.900 + Microsoft 365/Edge

            • #2485946

              Isn’t the answer to that question, “Yes.”?

              The answer is “No”.  The installation failures occurred while running Windows 11 Pro Version 22H2 (OS Build 22621.521).  No attempt at installation has occurred since the rebuild using Windows 11 Pro Version 22H2 (OS Build 22621.525) ISO, so no failures, either.

              Create a fresh drive image before making system changes/Windows updates, in case you need to start over!
              We all have our own reasons for doing the things that we do. We don't all have to do the same things.

            • #2485951

              The answer is “No”.

              I’m confused. Is “rebuild using Windows 11 Pro Version 22H2 (OS Build 22621.525) ISO” somehow different from “used 22621.525 installation media”?

              Windows 11 Pro version 22H2 build 22621.900 + Microsoft 365/Edge

            • #2485962

              Re-read the entire thread for clarity.  Incorrect assumptions were made in other members replies.

              You used 22621.525 installation media? it’s apparently been created with Component Cleanup executed, and this prevent installing 22621.608 (missing source files for PSFX)

              No installation failures occurred after …

              “rebuild using Windows 11 Pro Version 22H2 (OS Build 22621.525) ISO” somehow different from “used 22621.525 installation media”?

              … because no update has been attempted.  Prevention of installing 22621.608 from within 22621.525 has not occurred for the very simple reason …

              Windows update has KB5017389 parked and waiting to Download and install, but I’m leaving it there for the time being, and I’ll make some fresh drive images of this rejuvenated setup.

              I haven’t tried the update since the repair/reinstall.  What part of that do you not understand?

              Create a fresh drive image before making system changes/Windows updates, in case you need to start over!
              We all have our own reasons for doing the things that we do. We don't all have to do the same things.

            • #2485975

              Re-read the entire thread for clarity.

              I wish you’d practice what you preach.

              Incorrect assumptions were made in other members replies.

              You used 22621.525 installation media?
              it’s apparently been created with Component Cleanup executed, and this prevent installing 22621.608 (missing source files for PSFX)

              No installation failures occurred after …

              I don’t believe the part you bolded was a comment on anything you had done or were about to do. So, no incorrect assumptions other than yours.

              … because no update has been attempted.  Prevention of installing 22621.608 from within 22621.525 has not occurred for the very simple reason …

              But you did use 22621.525 installation media, right?

              I haven’t tried the update since the repair/reinstall.  What part of that do you not understand?

              I understand that perfectly. What made you think I did not?

              Windows 11 Pro version 22H2 build 22621.900 + Microsoft 365/Edge

            • #2485989

              I wish you’d practice what you preach.

              I do.  Perhaps you can explain this to me.

              You used 22621.525 installation media? it’s apparently been created with Component Cleanup executed, and this prevent installing 22621.608 (missing source files for PSFX)

              Note the bold.  “It’s” appears to reference “22621.525 installation media”.

              You used 22621.525 installation media? it’s apparently been created with Component Cleanup executed, and this prevent installing 22621.608 (missing source files for PSFX)

              Again, note the bold.  “apparently been created with Component Cleanup executed, and this prevent installing 22621.608 (missing source files for PSFX)”.  The inference is that 22621.525 is what prevented installing 22621.608.  However, I didn’t upgrade to 22621.525 until after the failed update under 22621.521.  Meaning that it was not possible for 22621.525 to have prevented installing 22621.608.

              Again, for the sake of clarity and to avoid confusion, I did not try to install KB5017389 while running 22621.525.  I tried to install it running 22621.521.  After the failed attempts, and with Windows update showing KB5017389 ready to download and install and also listed as successfully installed under Update history, I elected to restore drive images and revert to Windows 10, then run an in-place upgrade to Windows 11 Pro Version 22H2 (OS Build 22621.525).

              Create a fresh drive image before making system changes/Windows updates, in case you need to start over!
              We all have our own reasons for doing the things that we do. We don't all have to do the same things.

            • #2485995

              The inference is that 22621.525 is what prevented installing 22621.608.

              No one said that’s what you did (yet).

              I took it as a warning for the future.

              Windows 11 Pro version 22H2 build 22621.900 + Microsoft 365/Edge

        • #2485886

          You used 22621.525 installation media?
          it’s apparently been created with Component Cleanup executed, and this prevent installing 22621.608 (missing source files for PSFX)

          I downloaded the 22H2 ISO from Microsoft a week ago, believing it to be 22621.525. (Not for any particular purpose at present, but I also didn’t yet have an ISO for 22H2.) Is that still the latest available via https://www.microsoft.com/en-us/software-download/windows11 or has it been corrected?

          (Is there any logical reason Microsoft couldn’t publish the build number on that page when it gets updated?)

          Windows 11 Pro version 22H2 build 22621.900 + Microsoft 365/Edge

          • #2485900

            Yes, still 22621.525

            the failure to install 22621.608 on top of it isn’t persistent
            so the issue might not related to the installation media itself

            well, i guess they should publish it, similar to Insider ISO download page

            1 user thanked author for this post.
            b
            • #2485955

              Yes, still 22621.525

              No, still not 22621.525.

              the failure to install 22621.608 on top of it isn’t persistent so the issue might not related to the installation media itself

              There has been no attempt made to install 22621.608 on top of 22621.525.  Not even once.  That update is parked in Windows update ever since I did the repair install using the 22621,525 ISO.

              5017389-Windows-Update

              The ONLY installation failures occurred while running 22621.521.  No installation failures have occurred while running 22621.525 because no installation attempts have been made.  I did not want my Windows update listing the same update as being successfully installed as well as waiting for download and installation, hence the in-place upgrade (repair/reinstall).  22621.525 was the ISO available for download from Microsoft.

              Has reading with comprehension become a lost bit of education?

              Create a fresh drive image before making system changes/Windows updates, in case you need to start over!
              We all have our own reasons for doing the things that we do. We don't all have to do the same things.

              Attachments:
            • #2485981

              No, still not 22621.525.

              How can I find a more recent ISO build at Microsoft’s download page?

              Has reading with comprehension become a lost bit of education?

              Apparently.

              Windows 11 Pro version 22H2 build 22621.900 + Microsoft 365/Edge

            • #2485990

              the failure to install 22621.608 on top of it isn’t persistent so the issue might not related to the installation media itself

              There was no failure to install 22621.608 on top of 22621.525, because I was still on 22621,521 when the installation failed.

              Create a fresh drive image before making system changes/Windows updates, in case you need to start over!
              We all have our own reasons for doing the things that we do. We don't all have to do the same things.

            • #2486007

              Gentlemen.  Email sent privately.

              Susan Bradley Patch Lady

    Viewing 0 reply threads
    Reply To: September 30, 2022—KB5017389 (OS Build 22621.608) Preview

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

    Your information: