KB5004296 Windows 10 Insider RP 19043.1149 (21H1) or 19044.1149 (21H2) Insider

Page 12 of 14 FirstFirst ... 21011121314 LastLast

  1. Posts : 50,055
    Windows 10 Home 64bit 21H1 and insider builds
       #110

    Dark Knight said:
    Thank you, that is all they had to say, but I guess that one sentence would be a waste of a web page eh ?
    Yes, it is confusing. Intel licenced the technology from AMD, hence amd64.
      My Computer


  2. Posts : 3,352
    Windows 10 Pro x64
       #111

    Dark Knight said:
    Thank you, that is all they had to say, but I guess that one sentence would be a waste of a web page eh ?
    I've always wondered why it's named that way. If x86 stands alone, why shouldn't x64? Reserve more specific names for non-standard versions. But that's far from being the least logical computer related naming example.
      My Computer


  3. Posts : 74
    Windows 10 Pro 22H2
       #112

    Success with the 21H2 in place repair install to v1149

    KB5004296 just kept failing and would not install, was trying everything to correct and nothing suggested worked. Best of all got to keep everything! files, apps , programs.
      My Computer


  4. Posts : 50,055
    Windows 10 Home 64bit 21H1 and insider builds
       #113

    Dark Knight said:
    Success with the 21H2 in place repair install to v1149

    KB5004296 just kept failing and would not install, was trying everything to correct and nothing suggested worked. Best of all got to keep everything! files, apps , programs.
    Repair install sounds scary but it's not and it often clears up problems other methods can't
      My Computer


  5. Posts : 1,961
    Windows 10 Pro x64
       #114

    " Repair install sounds scary "..............avoid all these problems , just use the best solution you can get ; Macrium.......!
      My Computer


  6. Posts : 50,055
    Windows 10 Home 64bit 21H1 and insider builds
       #115

    pietcorus2 said:
    " Repair install sounds scary "..............avoid all these problems , just use the best solution you can get ; Macrium.......!
    Agreed and I do image regularly but these things can creep up on you and it's sometimes difficult to know how far back you need to restore. In this case you would probably have to go back one or more CU's to get clear of the problem and then you would have the pain of bringing everything up to date. In this case I would have taken the repair install route after making an image of course.
      My Computer


  7. Posts : 210
    Windows 10 Pro
       #116

    Also getting error 0x800f0990 when attempting to install this CU, several times. Microsoft should ditch Windows Update, because it's completely unreliable and only works when it feels like so. I tried installing the .cab file, it got stuck at 20% and disc usage was 0%, so I don't think it was doing anything. Last hope is downloading 19043.1149 iso from UUP dump and doing an in-place install and cross my fingers.
      My Computer


  8. Posts : 568
    Windows 11 Pro
       #117

    My laptop stayed on 1147 but my desktop went to 1149 and both are 5000 series ryzen based systems.
      My Computers


  9. Posts : 90
    Windows 10 x64
       #118

    HRPuffnstuff said:
    My laptop stayed on 1147 but my desktop went to 1149 and both are 5000 series ryzen based systems.
    Had the same issue and my laptop only stayed at 1147. I changed the insider channel to RP and then updated to 1149.
      My Computer


  10. Posts : 210
    Windows 10 Pro
       #119

    After spending the whole yesterday afternoon, I finally managed to install the update. For some reason the script (feature update option) from UUP dump created a 19041.1 image of Home + Home Single Language SKUs, which was the installed build, instead of 19043.1149. After going back to 19041.1 in this machine, I was finally able to install KB5004296 via Windows Update. FWIW, this is the script I downloaded:
    Code:
    19043.1149_amd64_pt-br_core_9acda6c6_convert_virtual.zip
    And this was the outdated image created:
    Code:
    19041.1.191206-1406.VB_RELEASE_CLIENTMULTI_X64FRE_PT-BR
    This is strange because I downloaded a script for a Pro iso to install in my desktop, and the image created was 19043.1149, as expected. I really don't know what caused the script to not integrate the updates. Any idea on what might have happened?
    I don't feel comfortable knowing that UUP dump script didn't work, if Windows Update didn't unbug itself after the in-place installation, the laptop would still be at an outdated build, I believe it was at 10943.1052 IIRC.
      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 14:15.
Find Us




Windows 10 Forums