New
#110
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 "..............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.
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 laptop stayed on 1147 but my desktop went to 1149 and both are 5000 series ryzen based systems.
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:
And this was the outdated image created:Code:19043.1149_amd64_pt-br_core_9acda6c6_convert_virtual.zip
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?Code:19041.1.191206-1406.VB_RELEASE_CLIENTMULTI_X64FRE_PT-BR
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.