I use DISM quite often but can't always remember the syntax

kelper · 2026-09-28T07:51:29-0400

This opening at 65% and exiting at70% with an error code of zero seems to have started today.

I booted to a command prompt and ran.

DISM /Image:C:\ /cleanup-image /restorehealth

and it ran normally to 100%

Can anyone explain? Not I, that's for sure. I can't code; I'm just an AI warrior with a hell of a lot of patience.

kelper · 2026-09-28T07:58:38-0400

WIN+X, A followed by DISM /Online /Cleanup-Image /restoreHealth also runs normally.

kelper · 2026-09-28T09:44:08-0400

Grok AI is much smarter. It told me to run

Get-Content C:\Windows\Logs\CBS\CBS.log -Tail 30

This shows Restorehealth is still running as cbs.log keeps updating. I'll wait to see if it ever ends.

gunrunnerjohn · 2026-09-28T12:15:12-0400

My \Restore Health runs for a very long time at 100% and then decides it can't find the repair files anywhere.

kelper · 2026-09-29T02:45:10-0400

Does anyone running RestoreHealth notice that the progress bar goes immediately to 65%? I had a long chat with ChatGPT about my CBS and DISM logs and asked for a summary.

What we established today about DISM

Your DISM installation is basically functioning. CheckHealth, ScanHealth and AnalyzeComponentStore all run successfully.
The servicing stack is present and current enough to operate. Your system has the Package_for_ServicingStack_9539 package installed, and DISM reports DismCore.dll version 10.0.26100.9549.
The apparent 70% failure of StartComponentCleanup is not, by itself, evidence of corruption. Other Windows 11 25H2 users on ElevenForum are reporting exactly the same behaviour: cleanup reaches 70% and then terminates, sometimes with “The operation completed successfully.”
Therefore, my earlier theory about a stale mounted WIM was probably a red herring. DISM /Get-MountedWimInfo reports no mounted images, so there is no evidence of an actively mounted WIM causing this.
The 0x8007007b / 0xc142011c messages in the DISM log relate to DISM's image/mount handling, but they do not establish that you currently have a damaged mounted image.
Your CBS log showed normal TrustedInstaller/CBS finalisation, rather than an obvious crash.
The important distinction is that 70% during Component Cleanup appears to be a known Windows 11 25H2 behaviour, whereas your RestoreHealth terminating early is a separate issue and still needs explaining.
Consequently, there is currently no good reason to try to “reset the servicing stack.” The evidence points instead towards investigating exactly what happens during RestoreHealth.

Bottom line: the 70% cleanup behaviour that initially looked suspicious is now looking much more like a Windows/DISM 25H2 quirk than a fault in your Windows installation. The unresolved problem is why RestoreHealth also quits early.

kelper · 2026-09-29T02:55:02-0400

The same issue happened in February.

KB5077181 Windows 11 Cumulative Update build 26100.7840 (24H2) and 26200.7840 (25H2) - Feb. 10

UPDATE 2/24: https://www.elevenforum.com/t/kb5077241-windows-11-cumulative-update-preview-build-26100-7922-24h2-and-26200-7922-25h2-feb-24.44824/ Microsoft Support: February 10, 2026 - KB5077181 (OS Builds 26200.7840 and 26100.7840) This cumulative update for Windows 11, version 25H2 and 24H2...

www.elevenforum.com

kelper · 2026-09-29T10:26:22-0400

The batch file is completely rewritten and tested. It runs hidden and notifies you on completion.

gunrunnerjohn · 2026-09-29T10:47:29-0400

kelper said:
The batch file is completely rewritten and tested. It runs hidden and notifies you on completion.

I'm not sure having it hidden is that good an idea, it's nice to see the progress if you want to check.

Asus272 · 2026-09-29T10:51:09-0400

kelper said:
The batch file is completely rewritten and tested. It runs hidden and notifies you on completion..

Nice coding job,,,, I will use it today on my 3 pc's running Windows 11 26200.9550.

I don't have the Dism issue that you and others have reported. I was reading your thread this morning and asking the question to myself what is the difference between my 3 pc's and yours?

The only thing I can come up with is, I have a Linux partiton my C: drive on 2 of them.
I have fast startup turned off in bios and hibernate turned off in all 3 of their power plans. I turn my equipment off at night.
I turned fast startup and hibernate off because Windows would corrupt Grub in the EFI boot partition during their monthly update.
Problem resolved.

kelper · 2026-09-29T10:57:43-0400

gunrunnerjohn said:
I'm not sure having it hidden is that good an idea, it's nice to see the progress if you want to check.

but it might run for an hour! I can give you a transparent version if you promise to test it and give feedback?

CLS · 2026-09-29T11:06:07-0400

does dism /online /cleanup-image /restorehealth reset custom settings I have made in windows 11?

kelper · 2026-09-29T11:14:52-0400

CLS said:
does dism /online /cleanup-image /restorehealth reset custom settings I have made in windows 11?

no

kelper · 2026-09-29T11:43:32-0400

@gunrunnerjohn

Here's one just for you. You can minimise the window and you will receive a notification on completion

PerpetualCycle · 2026-09-29T12:26:36-0400

Ghot said:
Option 3 just finished. Took 21 mins to run on my machine.
Gonna rerun option 2 to see if option 3 did the job...

LOL... still says Component Store is repairable, but that's normal too.

If you have used vivetool or the registry to enable new features this behavior will happen. If you remove them it should work,

kelper · 2026-09-29T12:46:54-0400

Option 3 took one hour on my system. The whole operation was hidden until I got the notification and I was not distracted. This suits me.

Asus272 · 2026-09-29T12:51:02-0400

Good review of the problem and some new suggestions that I haven't seen before.....

When DISM (Deployment Image Servicing and Management) fails or behaves unexpectedly on Windows 11, it is almost always due to missing payload files, Windows Update service glitches, UI/progress display quirks, or component store corruption.

1. Progress Bar Stops at 65% or 70%

Normal Servicing Behavior: During /AnalyzeComponentStore, /StartComponentCleanup, or /RestoreHealth, the DISM progress bar often jumps to 65% or 70% and appears stuck. This is a long-standing display behavior where DISM handles heavy WinSxS indexing in bulk.
Background Processing: Even if the command prompt stops updating progress, DISM is often still active in the background updating C:\Windows\Logs\CBS\CBS.log.
Known 24H2/25H2 Servicing Quirks: Certain Windows 11 updates have known cosmetic or minor servicing stack glitches where /StartComponentCleanup exits early at 70% with return code 0 or temporary errors.

2. Common Error Causes & Fixes

Cause A: Missing Repair Source Files (Errors 0x800f081f, 0x800f0906, 0x800f0915)

When running /RestoreHealth, DISM queries Windows Update to download clean versions of damaged WinSxS components. If Windows Update is disabled, blocked, or missing the exact build files, DISM fails.
Fix: Specify a mounted Windows 11 ISO as a repair source.

Download a matching Windows 11 ISO and right-click to Mount it (e.g., assigned to drive E:).
Open Terminal / Command Prompt (Admin) and run:
DOS

DISM /Online /Cleanup-Image /RestoreHealth /Source:E:\sources\install.wim /LimitAccess

(Replace install.wim with install.esd if your ISO uses ESD compression).

Cause B: Windows Update / SoftwareDistribution Cache Corruption

If the local update cache or network engines are corrupt, DISM cannot connect to Microsoft servers to pull repair payloads.
Fix: Reset the servicing and update caches.

Open Command Prompt (Admin) and stop update services:
DOS

net stop wuauserv
net stop bits
net stop cryptsvc
Rename or clear the update cache folders:
DOS

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
Restart services and retry:
DOS

net start wuauserv
net start bits
net start cryptsvc

Cause C: Offline Image vs. Online Environment Locks

Running DISM inside an active, running OS (/Online) means security applications, anti-virus locks, or active background services can occasionally block access to system files.
Fix: Run DISM offline via Windows Recovery Environment (WinRE).

Hold Shift while clicking Restart in the Start Menu.
Go to Troubleshoot > Advanced Options > Command Prompt.
Identify your Windows drive letter (e.g., C: or D:) and run:
DOS

DISM /Image:C:\ /Cleanup-Image /RestoreHealth

3. Recommended Step-by-Step Recovery Sequence

To ensure system files are verified properly, execute commands in this exact order:

Scan Health:
DOS

DISM /Online /Cleanup-Image /ScanHealth
Restore Health:
DOS

DISM /Online /Cleanup-Image /RestoreHealth
Run System File Checker (SFC): Always run SFC after DISM finishes successfully so SFC can use the newly restored component store to repair corrupted system files:
DOS

sfc /scannow

(Note: If DISM continues to fail across all methods, use Settings > System > Recovery > Fix problems using Windows Update or perform an In-Place Repair Upgrade using a Windows 11 ISO).

kelper · 2026-09-29T12:56:50-0400

@Asus272

Which AI did you use? The issue of RestoreHealth starting at 65% and quitting at 70% seems to have been fixed today, at least for me.

Ghot · 2026-09-29T13:03:08-0400

PerpetualCycle said:
If you have used vivetool or the registry to enable new features this behavior will happen. If you remove them it should work,

In the past I did, but I restored from a backup from before then.
So no, no turning on Features before MS turned them on.

ComponentCleanup and ResetBase both worked after the update before .9550

For example...
This time
And this one

But just now, run manually copy/paste...

I'm OCD bro. I check these things before I post them. ^^

@kelper 's DISM GUI thingy works fine. MS's DISM thingy is a broke down mess... again.
H*ll, even the Disk Cleanup 190MB+ bug came back with xxxxx.9457

FrancoDT · 2026-09-29T13:17:27-0400

Ghot said:
In the past I did, but I restored from a backup from before then.
So no, no turning on Features before MS turned them on.

ComponentCleanup and ResetBase both worked after the update before .9550

For example...
This time
And this one

But just now, run manually copy/paste...

View attachment 184634

I'm OCD bro. I check these things before I post them. ^^

@kelper 's DISM GUI thingy works fine. MS's DISM thingy is a broke down mess... again.
H*ll, even the Disk Cleanup 190MB+ bug came back with xxxxx.9550

I see I'm not the only one seeing StartCompenentCleanup finish at 70% on build 26300.9550 now.

Asus272 · 2026-09-29T13:43:10-0400

kelper said:
@Asus272

Which AI did you use? The issue of RestoreHealth starting at 65% and quitting at 70% seems to have been fixed today, at least for me.and

I used Ask Gemini... I use this forum of course as my main resource... but like to get other opinions and go from there... Trust but verify as the saying goes...

I use DISM quite often but can't always remember the syntax

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

What we established today about DISM​

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

Attachments

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Active member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

Attachments

My Computers My Computers

At a glance

At a glance

Syzygy

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Active member

1. Progress Bar Stops at 65% or 70%​

2. Common Error Causes & Fixes​

Cause A: Missing Repair Source Files (Errors 0x800f081f, 0x800f0906, 0x800f0915)​

Cause B: Windows Update / SoftwareDistribution Cache Corruption​

Cause C: Offline Image vs. Online Environment Locks​

3. Recommended Step-by-Step Recovery Sequence​

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

My Computers

My Computers

My Computers

My Computers

What we established today about DISM

My Computers

My Computers

My Computers

My Computers

My Computers

My Computers

My Computer

My Computers

My Computers

My Computers

My Computers

1. Progress Bar Stops at 65% or 70%

2. Common Error Causes & Fixes

Cause A: Missing Repair Source Files (Errors 0x800f081f, 0x800f0906, 0x800f0915)

Cause B: Windows Update / SoftwareDistribution Cache Corruption

Cause C: Offline Image vs. Online Environment Locks

3. Recommended Step-by-Step Recovery Sequence

My Computers

My Computers

My Computers

My Computers

My Computers