KB5005932 Windows Setup Update for Windows 10 v2004, v20H2, and v21H1 Win Update

Page 2 of 2 FirstFirst 12

  1. Posts : 237
    Windows 10 V1709
       #10

    Ghot said:
    Yeah I got that. Maybe that "fix" is more for arm64 anyhow. I mean the description is kind of weird.
    Anyone with an x86 or x64 can probably do an In-Place upgrade anyway.

    I'm just guessing though.
    The only file available in the MS catalog is for ARM64.

    KB5005932 Windows Setup Update for Windows 10 v2004, v20H2, and v21H1-image.png
      My Computer


  2. Posts : 23,253
    Win 10 Home ♦♦♦19045.4355 (x64) [22H2]
       #11

    fg2001gf10F said:
    The only file available in the MS catalog is for ARM64.

    KB5005932 Windows Setup Update for Windows 10 v2004, v20H2, and v21H1-image.png


    Yes. See post #1
      My Computer


  3. Posts : 237
    Windows 10 V1709
       #12

    Ghot said:
    Yes. See post #1
    I have 6 x64 machines, never had the problems described. I'll just ignore this for now.
      My Computer


  4. Posts : 2,557
    Windows 10 pro x64-bit
       #13

    For a while now, I have noticed that MS is releasing Updates that are not completely baked. Sometimes, release notes are late and now this. Is the pandemic really impacting things that bad or is it entirely something else?. Go figure!
      My Computers


  5. Posts : 1,750
    Windows 10 HOME 64-BIT
       #14

    Hmmmm, still ARM versions... Oh well... Never had probs with updates anyways! -- shrugs --
      My Computer


  6. Posts : 21,421
    19044.1586 - 21H2 Pro x64
       #15

    Am I understanding correctly that "Some devices cannot install new updates after installing KB5003214 (May 25, 2021) and KB5003690 (June 21, 2021)" (from the OP) , so the fix for them is to install this KB, then do an in-place upgrade?

    If PCs installed the July onward CUs, it seems they are not affected by this issue if I'm understanding this issue.
      My Computer


  7. Posts : 56,826
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #16

    steve108 said:
    Am I understanding correctly that "Some devices cannot install new updates after installing KB5003214 (May 25, 2021) and KB5003690 (June 21, 2021)" (from the OP) , so the fix for them is to install this KB, then do an in-place upgrade?

    If PCs installed the July onward CUs, it seems they are not affected by this issue if I'm understanding this issue.
    I know it sounds and looks twisted as Moebus Strip, but what they (MS) are trying to say is if the WU process has been failing on you, manually apply the .MSU quick update (to patch something), and you should be good to go. Maybe.

    They can't do this normally thru WU:

    This compatibility fix enables an in-place upgrade to be run on devices that cannot complete the installation of the latest cumulative update (LCU).
      My Computers


  8. Posts : 21,421
    19044.1586 - 21H2 Pro x64
       #17

    f14tomcat said:
    I know it sounds and looks twisted as Moebus Strip, but what they (MS) are trying to say is if the WU process has been failing on you, manually apply the .MSU quick update (to patch something), and you should be good to go. Maybe.
    Thanks TC for helping me understand this Moebus Strip,
    Just to clarify, you're saying to manually try and install the KB that was failing by downloading/installing the corresponding .MSU file, correct?

    Then if that fails to install and if my understanding of this KB5005932 is correct, one should install KB5005932 to initiate an automatic in-place upgrade.

    f14tomcat said:
    They can't do this normally thru WU:

    This compatibility fix enables an in-place upgrade to be run on devices that cannot complete the installation of the latest cumulative update (LCU).
    My current understanding after further reading is that if the subject KB5005932 is installed, the PC will initiate automatic an in-place upgrade sometime within 48 hours of installing this KB.

    Their use of the "enables" confused me. They mean installing the KB will automatically initiate an in-place upgrade. I thought they were saying the PC couldn't even take a manually initiated in-place upgrade without this KB, e.g. a previous KB disabled/broke the ability to do manual in-place upgrades.

    Since an in-place upgrade can take a while, depending on the PC, then it seems to me that the subject KB5005932 should not be installed on a PC unless it has a problem installing the LCU or one has another reason to initiate an automatic in-place upgrade.

    As of now, Microsoft Catalog is still showing this KB available for ARM as previously reported, but apparently it will be available for x64 and x32 in the future from what I've read.

    Thanks
      My Computer


  9. Posts : 56,826
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #18

    Whatever you say, Steve. All of that is way over my pay grade and I have many other things to worry about.
      My Computers


  10. Posts : 21,421
    19044.1586 - 21H2 Pro x64
       #19

    f14tomcat said:
    Whatever you say, Steve. All of that is way over my pay grade and I have many other things to worry about.
    You took a pay cut since your first response?
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 10:58.
Find Us




Windows 10 Forums