@Schroedinger2015 yes, they removed some components in .329, and also .327 had a corrupt component I will post a fix in a few hours
Your fixes seem to work but i am having a hard time with the conclusion that every post 18362.239 update contains the same faults.
no, they are different types of faults Most of the time problems occur because new update reverts components back to .1 — I guess this happens because they're built from a different branch The only two actually corrupt updates i noticed were .10013 (amd64_microsoft-windows-c..cal.desktop.cortana had a corrupt reverse delta bc it had less files than .1 version of same components) .327 (amd64_hyperv-compute-guestcomputeservice component is incorrectly marked as new instead of updated — and that's on top of the trouble with .329 reverting some components back to .1) In short, the new forward-reverse delta system generates more trouble than it's worth. “Agile” development at its finest. IIRC they have solved the .263 problem in later updates by re-adding the relevant component. I think solving .10013 and .327 requires either a servicing stack/WU update or a change in how the updates are built bc the process does not know the old update has bugs That's to say, i haven't noticed these problems in any public updates, only RP ones
I'll be waiting for your fix. I tried the one you posted in the other thread and I assume is not for 18363 but for 18362.
IDK why you can't see the image in my post but just to let you know, it's the same error that am getting too.
New 1903 Dotnetfx Rollup/CU: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-446#post-1544495
18362.329.1.11 SSU/CU appeared on Catalog, added to https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-446#post-1544495
there is no 18363 build of windows there is a package which changes the displayed number in winver and enables some features, but the actual build is still 18362
Do you have remove offline holographic ? If is removed then is problem... Also I have this error when remove holographic packages.
Does anyone have any information regarding 10015 19h2... I have looked but haven't seen anything officially from Microsoft. Lots of us here had problems installing the CU updates which only error out. The same problems causing the error most likely screwed up DISM functioning because I couldn't do any DISM upgrades to my ISO's. I downloaded the 18363.327 ISO and going to try right now to upgrade from 18362.10015 to 18363.327 because I don't want to be left out of an upgrade channel when final build hits. For MS to fork the 19h2 (3 different ways) and not address 10015 besides were looking into it responses, I'm not feeling really confident on a solution. If the upgrade works, I will let you guys know. Any info anybody has, would be great as well... Thanx UPDATE: Upgrade from 18362.10015 to 18363.327 went without a hitch... Windows update had a couple CU's to get current... Everything is good except Windows is saying something about driver issues with Intel Optane (however it's spelled). I just looked at Intel's site to see if there's any updates, but there's none. System still seems to be running fine with that error. Intel Optane fix: Uninstall Intel Optane Extension