I now did 3 tests, all installed the latest RP udpate just fine, the only thing i didn't do was performing an online cleanup (/startcomponentcleanup or with /resetbase), running that test now.
Again, don't post unfounded claims. View this: https://forums.mydigitallife.net/th...channel-ni_release.85327/page-58#post-1743362
but thats exactly what i did..before had an instalation from an UUP .160 installed.... (update doesnt work and isnt fixable) did new installation with an MS .1 iso build (format C and upgraded to .105 and from there installed the .169 update... IT WORKS this what you posted is iso creation.. not installing with that iso (.160) and then trying to install .169 update
created 22621.160.1.3 UUP dump ISO fixed the 22621.160.1.3 ISO installed using the created 22621.160.1.3 ISO Installed the 22621.169.1.5 update. Made a gif from the install + update That's what i did...
nothing wrong with resetbase per-se, it should be great but the crap upgrade setup is filled with hard terminating errors that make no sense we just can't get a break from bloat across builds and lcus, must needlessly keep most patch history and orphaned differential bits
I guess disk cleanup/system files cleanup will cause these errors too, but i just wanted to proof it was about cleaning up and this was the example i chose to do it with.
vivetool /enable /id:36354489 (SV2Navpane) vivetool /enable /id:39145991 (NWMTest1) Im not so sure this one even does anything, theres another entry with same id that cant be enabled vivetool /enable /id:37634385 (TIFE) vivetool /enable /id:38634282 (Brain_PreviewPackageEnabled) vivetool /enable /id:35681102 (donotusefortesting) this entry might stop you from getting 2 homes?? vivetool 3.1