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.
Cab file with KB5055518 stops at 3.0% in DISM which takes me back to the same conditions as at the very start of it;
Dealing with mum files was suggested afterwards by ms-partner posts to attempt smoothing out the NET Framework uncoordination (only NTFx3 & 2 was messed with).
I believe I should only be able to access Turn Windows Features On or Off but it's become inoperative.
The dates in format:table indicate, as I know by myself, the latest follow-up on updates which has been on the same track of auto-installed client-based Windows and leaving it configured as is -there had been no update problems since early 2024 .
And some events report
[Event Name: CbsPackageServicingFailure2
Problem signature:
P1: 10.0.19041.5789
P2: Package_for_ServicingStack_5676
P3: 19041.5676.1.3
--------------------------
Fault bucket 127929275990, type 5
Event Name: ScriptedDiagFailure
Response: Not available
Cab Id: 0
Problem signature:
P1: Microsoft Corporation.WindowsUpdateDiagnostic.9.3]
One could note that sometimes just before the log-in screen, WIndows works on updates up to a dead 35% and then drops it unfinished to display the log-in screen.
NetFxRepairTool.exe didn't fix this; and dotnetfx35.exe tool doesn't even complete a fair process (another method maybe?).
And WUTroubleshooter only in one circumstance while in this state of the computer, it reported
[InformationalWaaSMedicService
Issue found by :AutomaticCorruptionRepairPlugin }
-otherwise no other problem is found by the Troubleshooter than typical pending reboots or resetting security descriptor etc.
![](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(233.6, 74%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
Hi Claus,
Thank you for sharing the situation in detail.
Based on the screenshot you provided, the April monthly update appears stuck at 20% during installation. To help troubleshoot, could you clarify:
dism /online /get-packages /format:table
If the 2025 SSU (Servicing Stack Update) is already installed, you can proceed with a manual installation using DISM.
You mentioned using .mum files for add-package, but I’m unclear on the exact steps you followed. Could you share a screenshot of the process?
For clarity, the correct method for manual installation via DISM uses .cab files (not .mum). Here’s the recommended approach:
Steps to Manually Install the Update:
Download the April patch from the Microsoft Update Catalog.
Copy the .msu file to C:\temp
Create a new folder named CAB inside C:\temp
Open Command Prompt as Administrator and navigate to C:\temp
Extract the .msu to .cab using this command (replace update.msu with your actual filename):
expand -F:* update.msu C:\temp\cab
Install the update using DISM (replace filename.cab with the extracted file’s name):
DISM /Online /Add-Package /PackagePath:"C:\temp\cab\filename.cab"
Reboot your machine and verify if the patch installed successfully.
Let me know if you encounter any issues or need further assistance!