Need Help Using DISM Restorehealth from a mounted ISO file source

Question

Need Help Using DISM Restorehealth from a mounted ISO file source

Rachel Sampson 50

I am trying to repair corruption on my computer but the using the normal dism restorehealth command failed saying it couldn't find the source. I downloaded from the link under "Create Windows 11 Installation Media" From the Microsoft website. I went through the setup and chose to create an ISO. I mounted that ISO as a virtual device, then used the command

DISM /online /Cleanup-Image /RestoreHealth /Source:esd:F:\Sources\Install.esd:1and got the same error. Can someone please help me?

Edit: I tried after closing file explore in case that might be interfering somehow and got a new error. In the dism log there were errors saying

DISM API: PID=36844 TID=34132 Time_InternalToPublic failed - Time_InternalToPublic(hr:0x80070057)

7 answers

Your answer

Answer 1

To use DISM with a mounted ISO file as a source for the RestoreHealth command, ensure that you are using the correct syntax and that the source file is accessible. Here are some steps to help you troubleshoot the issue:

Verify the Mount Point: Ensure that the ISO is correctly mounted and that the drive letter (in your case, F:) is correct. You can check this by opening File Explorer and confirming that the contents of the ISO are accessible.
Correct Command Syntax: The command you provided seems to have a small syntax error. The correct format for using an ESD file should look like this:
```
   DISM /Online /Cleanup-Image /RestoreHealth /Source:esd:F:\Sources\Install.esd:1
```
Make sure to include a space after esd: and ensure that the path is correct.
Use the Correct Index: If the ESD file contains multiple images, ensure that the index number (the :1 part) corresponds to the correct version of Windows you want to restore. You can list the available images in the ESD file using the following command:
```
   DISM /Get-WimInfo /WimFile:F:\Sources\Install.esd
```
This will show you the available indexes and help you choose the correct one.
Check for Updates: Ensure that your Windows installation is updated. Sometimes, the repair process may fail if the target OS is patched to a higher level than the source.
Use Windows Update as a Source: If the above steps do not work, you can try running the command without specifying a source, allowing DISM to fetch files from Windows Update:
```
   DISM /Online /Cleanup-Image /RestoreHealth
```

If you continue to encounter issues, consider checking the CBS.log file for more detailed error messages that could provide further insight into the problem.

References:

Answer 2

Ramesh Srinivasan 72,520 Independent Advisor

Hi Rachel,

After running DISM, please upload the C:\Windows\Logs\CBS\CBS.log file in your next reply.

If you can't upload the file here, share it on OneDrive or GoFile.io and post the link here.

The CBS log contains details as to which component store files are corrupt.

Rachel Sampson 50 Reputation points

2026-02-04T02:44:18.2533333+00:00

DISM DISM.EXE:

2026-02-03 18:30:28, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->

2026-02-03 18:30:28, Info DISM DISM.EXE:

2026-02-03 18:30:28, Info DISM DISM.EXE: Host machine information: OS Version=10.0.26200, Running architecture=amd64, Number of processors=32

2026-02-03 18:30:28, Info DISM DISM.EXE: Instance information: Parent process=C:\Windows\System32\cmd.exe, Parent process PID=10900

2026-02-03 18:30:28, Info DISM DISM.EXE: Dism.exe version: 10.0.26100.5074

2026-02-03 18:30:28, Info DISM DISM.EXE: Executing command line: DISM /Online /Cleanup-Image /RestoreHealth /Source:esd:D:\Sources\Install.swm:1

2026-02-03 18:30:28, Info DISM DISM Manager: PID=28068 TID=23708 physical location path: C:\ - CDISMManager::CreateImageSession

2026-02-03 18:30:28, Info DISM DISM Manager: PID=28068 TID=23708 Event name for current DISM session is Global{5A93F229-0D24-46A8-A6B4-29A41A2CE166} - CDISMManager::CheckSessionAndLock

2026-02-03 18:30:28, Info DISM DISM Manager: PID=28068 TID=23708 Create session event 0x278 for current DISM session and event name is Global{5A93F229-0D24-46A8-A6B4-29A41A2CE166} - CDISMManager::CheckSessionAndLock

2026-02-03 18:30:28, Info DISM DISM Manager: PID=28068 TID=23708 Copying DISM from "C:\WINDOWS\System32\Dism" - CDISMManager::CreateImageSessionFromLocation

2026-02-03 18:30:28, Info DISM DISM Manager: PID=28068 TID=23708 No Sandbox was created, DISM running in-place. - CDISMManager::CreateImageSessionFromLocation

2026-02-03 18:30:28, Info DISM DISM Manager: PID=28068 TID=23708 Successfully loaded the ImageSession at "C:\WINDOWS\System32\Dism" - CDISMManager::LoadRemoteImageSession

2026-02-03 18:30:28, Info DISM DISM Image Session: PID=28076 TID=21904 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore

2026-02-03 18:30:28, Info DISM DISM OS Provider: PID=28076 TID=21904 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect

2026-02-03 18:30:28, Info DISM DISM OS Provider: PID=28076 TID=21904 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect

2026-02-03 18:30:28, Info DISM DISM Provider Store: PID=28076 TID=21904 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect

2026-02-03 18:30:28, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log

2026-02-03 18:30:28, Info DISM DISM Provider Store: PID=28076 TID=21904 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger

2026-02-03 18:30:28, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log

2026-02-03 18:30:28, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log

2026-02-03 18:30:28, Info DISM DISM Manager: PID=28068 TID=23708 Image session successfully loaded from location: C:\WINDOWS\System32\Dism - CDISMManager::CreateImageSession

2026-02-03 18:30:28, Info DISM DISM.EXE: Target image information: OS Version=10.0.26200.7623, Image architecture=amd64

2026-02-03 18:30:28, Info DISM DISM.EXE: Image session version: 10.0.26100.5074

2026-02-03 18:30:28, Info DISM DISM Transmog Provider: PID=28076 TID=21904 Current image session is [ONLINE] - CTransmogManager::GetMode

2026-02-03 18:30:28, Info DISM DISM Transmog Provider: PID=28076 TID=21904 Audit Mode: [No] - CTransmogManager::Initialize

2026-02-03 18:30:28, Info DISM DISM Transmog Provider: PID=28076 TID=21904 GetProductType: ProductType = [WinNT] - CTransmogManager::GetProductType

2026-02-03 18:30:28, Info DISM DISM Transmog Provider: PID=28076 TID=21904 Product Type: [WinNT] - CTransmogManager::Initialize

2026-02-03 18:30:28, Info DISM DISM Transmog Provider: PID=28076 TID=21904 Product Type ServerNT : [No] - CTransmogManager::Initialize

2026-02-03 18:30:28, Info DISM DISM OS Provider: PID=28076 TID=21904 Determined System directory to be C:\Windows\System32 - CDISMOSServiceManager::get_SystemDirectory

2026-02-03 18:30:28, Info CSI 00000001 Shim considered [l:123]'??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.26100.7295_none_a53f7c7777395343\wcp.dll' : got STATUS_SUCCESS

2026-02-03 18:30:28, Info DISM DISM Driver Manager: PID=28076 TID=21904 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize

2026-02-03 18:30:28, Info DISM DISM Package Manager: PID=28076 TID=21904 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize

2026-02-03 18:30:28, Info DISM DISM Package Manager: PID=28076 TID=21904 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\CBS\CBS.log - CDISMPackageManager::Initialize

2026-02-03 18:30:28, Info DISM DISM Package Manager: PID=28076 TID=21904 Loaded servicing stack for online use. - CDISMPackageManager::CreateCbsSession

2026-02-03 18:30:28, Info CSI 00000001 Shim considered [l:123]'??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.26100.7295_none_a53f7c7777395343\wcp.dll' : got STATUS_SUCCESS

2026-02-03 18:30:28, Info DISM DISM Package Manager: PID=28076 TID=21904 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine

2026-02-03 18:30:28, Info DISM DISM Package Manager: PID=28076 TID=21904 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine

2026-02-03 18:30:28, Info DISM DISM Package Manager: PID=28076 TID=21904 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine

2026-02-03 18:30:28, Warning DISM DISM Package Manager: PID=28076 TID=21904 CBS AddSource failed with HRESULT=0x8007007b! - CDISMPackageManager::Internal_Finalize

2026-02-03 18:30:28, Info DISM DISM Package Manager: PID=28076 TID=21904 CBS session options=0x40100! - CDISMPackageManager::Internal_Finalize

2026-02-03 18:30:39, Error DISM DISM Package Manager: PID=28076 TID=21904 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800706be)

2026-02-03 18:30:39, Error DISM DISM Package Manager: PID=28076 TID=21904 Failed processing package changes with session options - CDISMPackageManager::Internal_ProcessChangesWithOptions(hr:0x800706be)

2026-02-03 18:30:39, Error DISM DISM Package Manager: PID=28076 TID=21904 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800706be)

2026-02-03 18:30:39, Error DISM DISM Package Manager: PID=28076 TID=21904 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800706be)

2026-02-03 18:30:39, Error DISM DISM Package Manager: PID=28076 TID=21904 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800706be)

2026-02-03 18:30:39, Info DISM DISM Package Manager: PID=28076 TID=21904 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine

2026-02-03 18:30:39, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800706BE

2026-02-03 18:30:39, Info DISM DISM Package Manager: PID=28076 TID=27688 Finalizing CBS core. - CDISMPackageManager::Finalize

2026-02-03 18:30:39, Info DISM DISM Manager: PID=28068 TID=23708 Closing session event handle 0x278 - CDISMManager::CleanupImageSessionEntry

2026-02-03 18:30:39, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.

2026-02-03 18:30:39, Info DISM DISM.EXE:

2026-02-03 18:30:39, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->

2026-02-03 18:30:39, Info DISM DISM.EXE:

2026-02-03 18:30:55, Info DISM PID=9000 TID=4044 Scratch directory set to 'C:\Users\Rachel\AppData\Local\Temp'. - CDISMManager::put_ScratchDir

2026-02-03 18:30:55, Info DISM PID=9000 TID=4044 DismCore.dll version: 10.0.26100.7019 - CDISMManager::FinalConstruct

2026-02-03 18:30:55, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log

2026-02-03 18:30:55, Info DISM PID=9000 TID=4044 Successfully loaded the ImageSession at "C:\Windows\System32\Dism" - CDISMManager::LoadLocalImageSession

2026-02-03 18:30:55, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log

2026-02-03 18:30:55, Info DISM DISM Provider Store: PID=9000 TID=4044 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger

2026-02-03 18:30:55, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log

2026-02-03 18:30:55, Info DISM DISM Manager: PID=9000 TID=4044 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession

2026-02-03 18:30:55, Info DISM DISM.EXE:

2026-02-03 18:30:55, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->

2026-02-03 18:30:55, Info DISM DISM.EXE:

2026-02-03 18:30:55, Info DISM DISM.EXE: Host machine information: OS Version=10.0.26200, Running architecture=amd64, Number of processors=32

2026-02-03 18:30:55, Info DISM DISM.EXE: Instance information: Parent process=C:\Windows\System32\cmd.exe, Parent process PID=10900

2026-02-03 18:30:55, Info DISM DISM.EXE: Dism.exe version: 10.0.26100.5074

2026-02-03 18:30:55, Info DISM DISM.EXE: Executing command line: DISM /Online /Cleanup-Image /RestoreHealth /Source:swm:D:\Sources\Install.swm:1

2026-02-03 18:30:55, Info DISM DISM Manager: PID=9000 TID=4044 physical location path: C:\ - CDISMManager::CreateImageSession

2026-02-03 18:30:55, Info DISM DISM Manager: PID=9000 TID=4044 Event name for current DISM session is Global{EEBE3E11-F4BC-4F54-8008-8ECA1A650AEA} - CDISMManager::CheckSessionAndLock

2026-02-03 18:30:55, Info DISM DISM Manager: PID=9000 TID=4044 Create session event 0x278 for current DISM session and event name is Global{EEBE3E11-F4BC-4F54-8008-8ECA1A650AEA} - CDISMManager::CheckSessionAndLock

2026-02-03 18:30:55, Info DISM DISM Manager: PID=9000 TID=4044 Copying DISM from "C:\WINDOWS\System32\Dism" - CDISMManager::CreateImageSessionFromLocation

2026-02-03 18:30:55, Info DISM DISM Manager: PID=9000 TID=4044 No Sandbox was created, DISM running in-place. - CDISMManager::CreateImageSessionFromLocation

2026-02-03 18:30:55, Info DISM DISM Manager: PID=9000 TID=4044 Successfully loaded the ImageSession at "C:\WINDOWS\System32\Dism" - CDISMManager::LoadRemoteImageSession

2026-02-03 18:30:55, Info DISM DISM Image Session: PID=26940 TID=29148 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore

2026-02-03 18:30:55, Info DISM DISM OS Provider: PID=26940 TID=29148 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect

2026-02-03 18:30:55, Info DISM DISM OS Provider: PID=26940 TID=29148 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect

2026-02-03 18:30:55, Info DISM DISM Provider Store: PID=26940 TID=29148 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect

2026-02-03 18:30:55, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log

2026-02-03 18:30:55, Info DISM DISM Provider Store: PID=26940 TID=29148 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger

2026-02-03 18:30:55, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log

2026-02-03 18:30:55, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log

2026-02-03 18:30:55, Info DISM DISM Manager: PID=9000 TID=4044 Image session successfully loaded from location: C:\WINDOWS\System32\Dism - CDISMManager::CreateImageSession

2026-02-03 18:30:55, Info DISM DISM.EXE: Target image information: OS Version=10.0.26200.7623, Image architecture=amd64

2026-02-03 18:30:55, Info DISM DISM.EXE: Image session version: 10.0.26100.5074

2026-02-03 18:30:55, Info DISM DISM Transmog Provider: PID=26940 TID=29148 Current image session is [ONLINE] - CTransmogManager::GetMode

2026-02-03 18:30:55, Info DISM DISM Transmog Provider: PID=26940 TID=29148 Audit Mode: [No] - CTransmogManager::Initialize

2026-02-03 18:30:55, Info DISM DISM Transmog Provider: PID=26940 TID=29148 GetProductType: ProductType = [WinNT] - CTransmogManager::GetProductType

2026-02-03 18:30:55, Info DISM DISM Transmog Provider: PID=26940 TID=29148 Product Type: [WinNT] - CTransmogManager::Initialize

2026-02-03 18:30:55, Info DISM DISM Transmog Provider: PID=26940 TID=29148 Product Type ServerNT : [No] - CTransmogManager::Initialize

2026-02-03 18:30:55, Info DISM DISM OS Provider: PID=26940 TID=29148 Determined System directory to be C:\Windows\System32 - CDISMOSServiceManager::get_SystemDirectory

2026-02-03 18:30:55, Info CSI 00000001 Shim considered [l:123]'??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.26100.7295_none_a53f7c7777395343\wcp.dll' : got STATUS_SUCCESS

2026-02-03 18:30:55, Info DISM DISM Driver Manager: PID=26940 TID=29148 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize

2026-02-03 18:30:55, Info DISM DISM Package Manager: PID=26940 TID=29148 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize

2026-02-03 18:30:55, Info DISM DISM Package Manager: PID=26940 TID=29148 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\CBS\CBS.log - CDISMPackageManager::Initialize

2026-02-03 18:30:55, Info DISM DISM Package Manager: PID=26940 TID=29148 Loaded servicing stack for online use. - CDISMPackageManager::CreateCbsSession

2026-02-03 18:30:55, Info CSI 00000001 Shim considered [l:123]'??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.26100.7295_none_a53f7c7777395343\wcp.dll' : got STATUS_SUCCESS

2026-02-03 18:30:55, Info DISM DISM Package Manager: PID=26940 TID=29148 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine

2026-02-03 18:30:55, Info DISM DISM Package Manager: PID=26940 TID=29148 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine

2026-02-03 18:30:55, Info DISM DISM Package Manager: PID=26940 TID=29148 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine

2026-02-03 18:30:57, Warning DISM DISM Package Manager: PID=26940 TID=29148 CBS AddSource failed with HRESULT=0x8007007b! - CDISMPackageManager::Internal_Finalize

2026-02-03 18:30:57, Info DISM DISM Package Manager: PID=26940 TID=29148 CBS session options=0x40100! - CDISMPackageManager::Internal_Finalize

2026-02-03 18:39:17, Error DISM DISM Package Manager: PID=26940 TID=29148 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800706be)

2026-02-03 18:39:17, Error DISM DISM Package Manager: PID=26940 TID=29148 Failed processing package changes with session options - CDISMPackageManager::Internal_ProcessChangesWithOptions(hr:0x800706be)

2026-02-03 18:39:17, Error DISM DISM Package Manager: PID=26940 TID=29148 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800706be)

2026-02-03 18:39:17, Error DISM DISM Package Manager: PID=26940 TID=29148 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800706be)

2026-02-03 18:39:17, Error DISM DISM Package Manager: PID=26940 TID=29148 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800706be)

2026-02-03 18:39:17, Info DISM DISM Package Manager: PID=26940 TID=29148 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine

2026-02-03 18:39:17, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800706BE

2026-02-03 18:39:17, Info DISM DISM Package Manager: PID=26940 TID=32376 Finalizing CBS core. - CDISMPackageManager::Finalize

2026-02-03 18:39:17, Info DISM DISM Manager: PID=9000 TID=4044 Closing session event handle 0x278 - CDISMManager::CleanupImageSessionEntry

2026-02-03 18:39:17, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.

2026-02-03 18:39:17, Info DISM DISM.EXE:

2026-02-03 18:39:17, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->

2026-02-03 18:39:17, Info DISM DISM.EXE:
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Answer 3

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Answer 4

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Answer 5

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Share via

Need Help Using DISM Restorehealth from a mounted ISO file source

7 answers

Your answer