Yeah on a machine I did the cleanup-image without resetbase I couldn't install 264. But on a machine I didn't run the cleanup-image I could install 264 fine. Could explain why they released 264.
IS there a way to force dism to install 264, or what other options do I have other than starting fresh.
SO basically I am screwed for 264, as well as all future CU's? looks like ill have to start fresh. Good time as any now I can install my new 1tg SSD.
I think this update will be an optional update when it's released, like the past out-of-Patch-Tuesday updates for 1903. In 1809 (LTSC at least) the mid-month updates are installed automatically, when I check for updates
That error probably occur if they downgrade or removed a component in higher CU compared to previous CU https://forums.mydigitallife.net/posts/1282637/
Glad to report that after transferring all partitions from old drive to new ssd and installing it. Boot up and restored a point from Monday, I was able to install both 263 and then 264 without issues. I believe that the component cleanup was the culprit. Not a complete start over but at least I had a restore point from Monday. Thanks for you help @Enthousiast
Hmm higher component number in the CU is it or well from .263 to .264 here so if that's it I wonder if some component got reverted for some unspecified reason then but after doing that cleanup routine and it becomes permanent and can't be uninstalled (Well "ResetBase" I suppose, need to be more careful with that then.) and the update fails well should be temporary at least if that's the case whichever component it is. Shouldn't be too long until 19H2 pops up either could always jump to that if that persists ha ha, good to know what caused it to error out at least ha ha routines and the possibility if running into something even on the preview channel compared to fast or slow ring.
I didnt do component cleanup or reset base, however I CLEANED UP WINDOWS UPDATE in disk cleaner utility! so waiting for next cu or 19H2 service pack
Interesting and good to know that too, cleanup utility at least from how I understood it to work is about the same as DISM and cleanup of updates this way although without the /resetbase parameter so it is good to know it would have broken even without using that parameter which then seems like a oversight though I guess the scheduled maintenance and cleanup doesn't touch updates or if it does then within a few days everyone on .263 from the release preview branch would have been affected since that runs on a timer. Well the next monthly cumulative should hopefully fix it if Microsoft isn't going to publish a newer release preview channel update with whatever they changed in .264 fixed and updated to a newer version again and then that should install, not too sure on how this works but it should be temporary though I am curious on what they did change and why but it's not like there's any detailed notes for what these updates actually do affect and .263 seemed like a pretty extensive one for how many files it altered and how long it took to install it plus the service stack component as well also part of it. EDIT: But even on the release preview branch there is a chance of encountering problems even if it's less frequent than on the slow and fast ring build updates and the current split for 20H1 on fast ring and 19H2 on the slow ring. Shouldn't be too severe but I can't really say how much of this process works although I am thinking a re-published later update with newer components should install just fine once available.
Downgraded no, removed yes. It tries to get back to the .1 version which has already been removed from disk.