This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 26%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECD%3C/text%3E%3C/svg%3E)
Hi,
And the DISM log file indicates,
CSI transaction destroyed,
(because next is)
CBS No Edition family found.
Now, /startcomponentcleanup and /scannow can complete (!) succesfully but a net framework update and a cumulative update fail to install. (/analyzecomponentstore & /restorehealth don't complete succesfully)
Any particular suggestions if to evade in-place reinstallation or external media wipe-out of the drive?
(we count already: wim and esd source images in Windows Recovery, usb installation media with dism../source:..winsxs, windows update troublseshooter, wuaulct.exe and manual installation from MUCatalogue, extracted cab files, git script for WUpdate reset)
Actually in-place reinstallation failed even without turning win updates on, it reverted back to desktop before finishing the percentage in the purple screen.
I would like to point to this:
/get-packageinfo fails to read a MUM file in /servicing/packages with error 87; now this MUM file cannot be seen with /get-packages although it's still there in the Folder -other MUM files could be removed from the folder with /remove-package and come back in with /add-package.
Then I could simply /add-package this MUM file over the already existing in the folder and it simply completes and then it's able to provide info with /get-packageinfo although nothing had changed in the meantime with the folder /servicing/packages.
I mean even if it's a basic package without a capacity to be removed, it would allow dism to /get-packageinfo nonetheless?
Even though /checkhealth and /scanhealth report the image to be repairable.
Later on, WUpdate leaves only the first log with the download error to be visible in Settings.
And obviously it is an adjoining setback that Enable Windows Features in Control Panel has become inoperable by way of white blank when launched (no waiting... and it responds to closing). Possibly disabling temporarily there Net Framework 2 & 3.5 would resolve the situation with Windows Updates.