KB5001330 Windows 10 Insider Beta 19043.928 21H1 and RP 19042.928 20H2 Insider

Page 3 of 8 FirstFirst 12345 ... LastLast

  1. Posts : 3,297
    Windows 10 Pro x64
       #20

    Installed smoothly on Beta channel machine and 3 non-Insider machines already upgraded to 21H1. No problems on any of them so far.
      My Computer


  2. Posts : 17,620
    Win 10 Home 10.0.19044.1706 (x64) [21H2]
       #21

    Worked on this machine, which was already on 19043.906



    KB5001330 Windows 10 Insider Beta 19043.928 21H1 and RP 19042.928 20H2-image1.png



    KB5001330 Windows 10 Insider Beta 19043.928 21H1 and RP 19042.928 20H2-image2.png



    KB5001330 Windows 10 Insider Beta 19043.928 21H1 and RP 19042.928 20H2-image3.png




    Seems it overwrote the March 2021 updates.
      My Computer


  3. Posts : 56,050
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #22

    Ghot said:
    Worked on this machine, which was already on 19043.906



    KB5001330 Windows 10 Insider Beta 19043.928 21H1 and RP 19042.928 20H2-image1.png



    KB5001330 Windows 10 Insider Beta 19043.928 21H1 and RP 19042.928 20H2-image2.png



    KB5001330 Windows 10 Insider Beta 19043.928 21H1 and RP 19042.928 20H2-image3.png




    Seems it overwrote the March 2021 updates.
    Cumulatives are known for doing that.
      My Computers


  4. Posts : 17,620
    Win 10 Home 10.0.19044.1706 (x64) [21H2]
       #23

    f14tomcat said:
    Cumulatives are known for doing that.


    I know. I WAS kind of amazed that it over wrote or re-installed the enablement package, which I had already installed about a month ago.
      My Computer


  5. Posts : 25
    Windows 10 X64
       #24

    Finished rather quickly... left me with winver "Version 20H2 (OS Build 19042.928)"
      My Computer


  6. Posts : 77
    Win 10 Pro
       #25

    For anyone (like me) who has been having unresolved issues with the last few months of CU's failing to install with errors such as:

    (0x8007000d)

    Here's a potential fix that may help others.
    After spending multiple days troubleshooting this issue, the problem was actually caused by a WMR (Holographic Desktop) update that was first pushed late January 2021.
    Running this DISM command then restarting your PC will resolve, and the CU should install without issue:

    dism /online /remove-capability /capabilityname:Analog.Holographic.Desktop~~~~0.0.1.0
      My Computer


  7. Posts : 1,105
    Windows 10 Pro x64-bit Build Latest
       #26

    Only now seeing this... Going for it!
      My Computer


  8. Posts : 203
    Windows 10 Pro 21H1
       #27

    Ghot said:
    I know. I WAS kind of amazed that it over wrote or re-installed the enablement package, which I had already installed about a month ago.
    Mine didn't, I still have the enablement package installed, dated March 26th
      My Computer


  9. Posts : 17,620
    Win 10 Home 10.0.19044.1706 (x64) [21H2]
       #28

    BrianInEngland said:
    Mine didn't, I still have the enablement package installed, dated March 26th


    Seems I got KB5000736 (the first time) from UUP Dump on March 1st.
    MS must have decided they didn't like the one from UUP Dump or that I shouldn't have a record of it.
      My Computer


  10. Posts : 203
    Windows 10 Pro 21H1
       #29

    Ghot said:
    Seems I got KB5000736 (the first time) from UUP Dump on March 1st.
    MS must have decided they didn't like the one from UUP Dump or that I shouldn't have a record of it.
    Mine shows installed on March 26th, but I did a UUP install on March 31st. Afterwards it downloaded the feature pack, but still shows the same date
      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 19:51.
Find Us




Windows 10 Forums