Thanks for your reply @abbodi1406 So I did indeed restore from an image backup to retry with an inplace-upgrade, for which I created a proper 18362.329 iso. (18362.329.190828-1651.19H1_RELEASE_SVC_PROD3_CLIENTMULTI_X64FRE_DE-DE.ISO) And the results are quite surprising: Code: c:\Windows\WinSxS before (fresh 18362.327): 6,1GB c:\Windows\WinSxS after applying abbodi's hack and cleaning up: 7,8GB c:\Windows\WinSxS after inplace-upgrade to 18362.329 and cleaning up: 3,3GB c:\Windows before (fresh 18362.327): 10,7GB c:\Windows after applying abbodi's hack and cleaning up: 12,9GB c:\Windows after inplace-upgrade to 18362.329 and cleaning up: 5.8GB Windows Update works and finds no longer any uninstalled updates. Code: Microsoft Windows [Version 10.0.18362.329] (c) 2019 Microsoft Corporation. Alle Rechte vorbehalten. C:\Windows\System32>systeminfo <...> Hotfix(es): 4 Hotfix(e) installiert. [01]: KB4511555 [02]: KB4503308 [03]: KB4515530 [04]: KB4512941 <...> I am still very surprised and confused by the huge differences in numbers compared to .327 vs .329 so I assume that windirstat gets a little confused by WinSxS, how could that be almost a 50% difference in size? In the end I have compared the filesizes of the compressed backups of the entire installations and this gives some more realistic numbers. Code: Highly compressed backup (after applying abbodi's hack and cleaning up): +1.04GB Highly compressed backup (after inplace-upgrade to 18362.329 and cleaning up): -0.14GB This does indeed mean that .329 is considerably smaller than .327, this appears to be a very optimized CU (or atleast it finally replaces a tons of patches that were not yet cumulated). Absolutely nothing like 50% smaller, but definitely noticable. The highly compressed +1.04GB (compared to .327) shows that the extra 2.2GB diskspace (as reported earlier) was indeed a real number. I admire the smart work you've put into your hack, but these numbers speak for themselves. And it will also make me sleep much better, I didn't feel comfortable with reinjecting ancient stuff from a base build that is months old. I can only advise people to try an inplace-upgrade first and see if this fixes the problem (it did for me).
@abbodi1406 thanks for the fix, however i tried both uup .1 and iso .30. and cu still errors out. WfW 1903.239 (installed from cleaned&resetbase wim) thanks for any help!
abbodi's fix has always worked so far, on many machines I tried. Are you sure to have followed in the exact way the needed steps of his own guide ?
I had the same problem, but I was able to install the CU manually which lifted me to .239 as well. As can be read in my earlier post, I reverted and decided for an inplace-upgrade instead, which results in no errors at all.
About Cortana was maxing out one cpu core after installing kb4512941 and search didn't work issue: (docs.microsoft.com/en-us/windows/release-information/status-windows-10-1903#676msgdesc) I had same problem, fixed by turning from 0 to 1 the value of: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Search\BingSearchEnabled
SLOW Ring: 18362.10019: https://forums.mydigitallife.net/th...lease_svc_19h2_rel.79895/page-12#post-1545899