Thanks for the update, I just came to know that the issue you posted is being reported by several other users so you aren't alone. Glad you got it sorted, though!
DISM Failing to Restore Health of Windows Images Following Installing KB5094126 on 25H2 Home
![](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(211.20000000000002, 93%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENH%3C/text%3E%3C/svg%3E)
Neil Hobbs
5
Reputation points
Yesterday, I installed the June 09 CU KB5094126, on my Windows 11 25H2 Home laptop. Following this, the following DISM command is failing to restore the health of the Windows Image on the laptop;
dism /online /cleanup-image /restorehealth
The process proceeds until it gets to 64.1%, and then it pauses and then jumps to 100% failing to successfully restore the health of the Image. When this happens, the Command Prompt displays the following;
Deployment Image Servicing and Management tool
Version: 10.0.26100.8521
Image Version: 10.0.26200.8655
[==========================100.0%==========================]
Error: 0x800f0915
The repair content could not be found anywhere.
Check the internet connectivity or use the "Source" option to specify the location of the files that are required to restore the image. For more information on specifying a source location, see https://go.microsoft.com/fwlink/?LinkId=243077.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
I attempted this three (3) times immediately following the installation of the CU yesterday and the same result each time.
Looking in the DISM log which is mentioned above, this the log from this failed session;
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=8584 DismApi.dll: - DismInitializeInternal
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=8584 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=8584 DismApi.dll: - DismInitializeInternal
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=8584 DismApi.dll: Host machine information: OS Version=10.0.26200, Running architecture=amd64, Number of processors=6 - DismInitializeInternal
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=8584 DismApi.dll: API Version 10.0.26100.8521 - DismInitializeInternal
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=8584 DismApi.dll: Parent process command line: "C:\WINDOWS\system32\cleanmgr.exe" /autocleanstoragesense /d C: - DismInitializeInternal
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=8584 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
2026-06-11 23:13:01, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=8584 Initialized GlobalConfig - DismInitializeInternal
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=8584 Initialized SessionTable - DismInitializeInternal
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=8584 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=8584 Waiting for m_pInternalThread to start - CCommandThread::Start
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=6484 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=6484 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=8584 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=8584 m_pInternalThread started - CCommandThread::Start
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=8584 Created g_internalDismSession - DismInitializeInternal
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=8584 Input parameters: ImagePath: DISM_{53BFAE52-B167-4E2F-A258-0A37B57FF845}, WindowsDirectory: (null), SystemDrive: (null) - DismOpenSessionInternal
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=8584 Lookup in table by path failed for: DRIVE_C - CTransactionalImageTable::LookupImagePath
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=8584 Waiting for m_pInternalThread to start - CCommandThread::Start
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=11640 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=8584 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=8584 m_pInternalThread started - CCommandThread::Start
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=11640 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=8584 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=11640 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2026-06-11 23:13:01, Info DISM API: PID=11244 TID=11640 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2026-06-11 23:13:01, Info DISM PID=11244 TID=11640 Scratch directory set to 'C:\Users\neilh\AppData\Local\Temp'. - CDISMManager::put_ScratchDir
2026-06-11 23:13:01, Info DISM PID=11244 TID=11640 DismCore.dll version: 10.0.26100.8521 - CDISMManager::FinalConstruct
2026-06-11 23:13:01, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2026-06-11 23:13:01, Info DISM PID=11244 TID=11640 Successfully loaded the ImageSession at "C:\WINDOWS\system32\Dism" - CDISMManager::LoadLocalImageSession
2026-06-11 23:13:01, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2026-06-11 23:13:01, Info DISM DISM Provider Store: PID=11244 TID=11640 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2026-06-11 23:13:01, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2026-06-11 23:13:01, Info DISM DISM Manager: PID=11244 TID=11640 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2026-06-11 23:14:00, Info DISM PID=14608 TID=11084 Scratch directory set to 'C:\Users\neilh\AppData\Local\Temp'. - CDISMManager::put_ScratchDir
2026-06-11 23:14:00, Info DISM PID=14608 TID=11084 DismCore.dll version: 10.0.26100.8521 - CDISMManager::FinalConstruct
2026-06-11 23:14:00, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2026-06-11 23:14:00, Info DISM PID=14608 TID=11084 Successfully loaded the ImageSession at "C:\Windows\System32\Dism" - CDISMManager::LoadLocalImageSession
2026-06-11 23:14:00, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2026-06-11 23:14:00, Info DISM DISM Provider Store: PID=14608 TID=11084 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2026-06-11 23:14:00, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2026-06-11 23:14:00, Info DISM DISM Manager: PID=14608 TID=11084 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2026-06-11 23:14:00, Info DISM DISM.EXE:
2026-06-11 23:14:00, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->
2026-06-11 23:14:00, Info DISM DISM.EXE:
2026-06-11 23:14:00, Info DISM DISM.EXE: Host machine information: OS Version=10.0.26200, Running architecture=amd64, Number of processors=6
2026-06-11 23:14:00, Info DISM DISM.EXE: Instance information: Parent process=C:\Windows\System32\cmd.exe, Parent process PID=3800
2026-06-11 23:14:00, Info DISM DISM.EXE: Dism.exe version: 10.0.26100.8521
2026-06-11 23:14:00, Info DISM DISM.EXE: Executing command line: dism /online /cleanup-image /restorehealth
2026-06-11 23:14:00, Info DISM DISM Manager: PID=14608 TID=11084 physical location path: C:\ - CDISMManager::CreateImageSession
2026-06-11 23:14:00, Info DISM DISM Manager: PID=14608 TID=11084 Event name for current DISM session is Global{23002C97-955F-4C58-A2E7-891130AE8EAC} - CDISMManager::CheckSessionAndLock
2026-06-11 23:14:00, Info DISM DISM Manager: PID=14608 TID=11084 Create session event 0x27c for current DISM session and event name is Global{23002C97-955F-4C58-A2E7-891130AE8EAC} - CDISMManager::CheckSessionAndLock
2026-06-11 23:14:00, Info DISM DISM Manager: PID=14608 TID=11084 Copying DISM from "C:\WINDOWS\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
2026-06-11 23:14:00, Info DISM DISM Manager: PID=14608 TID=11084 No Sandbox was created, DISM running in-place. - CDISMManager::CreateImageSessionFromLocation
2026-06-11 23:14:00, Info DISM DISM Manager: PID=14608 TID=11084 Successfully loaded the ImageSession at "C:\WINDOWS\System32\Dism" - CDISMManager::LoadRemoteImageSession
2026-06-11 23:14:00, Info DISM DISM Image Session: PID=3396 TID=3752 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2026-06-11 23:14:00, Info DISM DISM OS Provider: PID=3396 TID=3752 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
2026-06-11 23:14:00, Info DISM DISM OS Provider: PID=3396 TID=3752 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
2026-06-11 23:14:00, Info DISM DISM Provider Store: PID=3396 TID=3752 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2026-06-11 23:14:00, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2026-06-11 23:14:00, Info DISM DISM Provider Store: PID=3396 TID=3752 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2026-06-11 23:14:00, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2026-06-11 23:14:00, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2026-06-11 23:14:00, Info DISM DISM Manager: PID=14608 TID=11084 Image session successfully loaded from location: C:\WINDOWS\System32\Dism - CDISMManager::CreateImageSession
2026-06-11 23:14:00, Info DISM DISM.EXE: Target image information: OS Version=10.0.26200.8655, Image architecture=amd64
2026-06-11 23:14:00, Info DISM DISM.EXE: Image session version: 10.0.26100.8521
2026-06-11 23:14:00, Info DISM DISM Transmog Provider: PID=3396 TID=3752 Current image session is [ONLINE] - CTransmogManager::GetMode
2026-06-11 23:14:00, Info DISM DISM Transmog Provider: PID=3396 TID=3752 Audit Mode: [No] - CTransmogManager::Initialize
2026-06-11 23:14:00, Info DISM DISM Transmog Provider: PID=3396 TID=3752 GetProductType: ProductType = [WinNT] - CTransmogManager::GetProductType
2026-06-11 23:14:00, Info DISM DISM Transmog Provider: PID=3396 TID=3752 Product Type: [WinNT] - CTransmogManager::Initialize
2026-06-11 23:14:00, Info DISM DISM Transmog Provider: PID=3396 TID=3752 Product Type ServerNT : [No] - CTransmogManager::Initialize
2026-06-11 23:14:00, Info DISM DISM OS Provider: PID=3396 TID=3752 Determined System directory to be C:\Windows\System32 - CDISMOSServiceManager::get_SystemDirectory
2026-06-11 23:14:00, Info CSI 00000001 Shim considered [l:123]'??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.26100.8648_none_a50ef8e3775e8e5e\wcp.dll' : got STATUS_SUCCESS
2026-06-11 23:14:00, Info DISM DISM Driver Manager: PID=3396 TID=3752 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2026-06-11 23:14:00, Info DISM DISM Package Manager: PID=3396 TID=3752 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2026-06-11 23:14:00, Info DISM DISM Package Manager: PID=3396 TID=3752 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\CBS\CBS.log - CDISMPackageManager::Initialize
2026-06-11 23:14:00, Info DISM DISM Package Manager: PID=3396 TID=3752 Loaded servicing stack for online use. - CDISMPackageManager::CreateCbsSession
2026-06-11 23:14:00, Info CSI 00000001 Shim considered [l:123]'??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.26100.8648_none_a50ef8e3775e8e5e\wcp.dll' : got STATUS_SUCCESS
2026-06-11 23:14:00, Info DISM DISM Package Manager: PID=3396 TID=3752 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2026-06-11 23:14:00, Info DISM DISM Package Manager: PID=3396 TID=3752 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2026-06-11 23:14:00, Info DISM DISM Package Manager: PID=3396 TID=3752 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2026-06-11 23:14:00, Info DISM DISM Package Manager: PID=3396 TID=3752 CBS session options=0x40100! - CDISMPackageManager::Internal_Finalize
2026-06-11 23:35:53, Info DISM DISM Package Manager: PID=3396 TID=7616 Error in operation: The repair content could not be found anywhere. (CBS HRESULT=0x800f0915) - CCbsConUIHandler::Error
2026-06-11 23:35:53, Error DISM DISM Package Manager: PID=3396 TID=3752 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f0915)
2026-06-11 23:35:53, Error DISM DISM Package Manager: PID=3396 TID=3752 The repair content could not be found anywhere. The image may be corrupted. Check the internet connection or try to restore the image using the /source option. - GetCbsErrorMsg
2026-06-11 23:35:53, Error DISM DISM Package Manager: PID=3396 TID=3752 Failed processing package changes with session options - CDISMPackageManager::Internal_ProcessChangesWithOptions(hr:0x800f0915)
2026-06-11 23:35:53, Error DISM DISM Package Manager: PID=3396 TID=3752 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f0915)
2026-06-11 23:38:29, Error DISM DISM Package Manager: PID=3396 TID=3752 The repair content could not be found anywhere. The image may be corrupted. Check the internet connection or try to restore the image using the /source option. - GetCbsErrorMsg
2026-06-11 23:38:29, Error DISM DISM Package Manager: PID=3396 TID=3752 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f0915)
2026-06-11 23:38:29, Error DISM DISM Package Manager: PID=3396 TID=3752 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0915)
2026-06-11 23:38:29, Info DISM DISM Package Manager: PID=3396 TID=3752 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2026-06-11 23:38:29, Info DISM DISM Package Manager: PID=3396 TID=3752 Finalizing CBS core. - CDISMPackageManager::Finalize
2026-06-11 23:38:29, Info DISM DISM Manager: PID=14608 TID=11084 Closing session event handle 0x27c - CDISMManager::CleanupImageSessionEntry
2026-06-11 23:38:29, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2026-06-11 23:38:29, Info DISM DISM.EXE:
2026-06-11 23:38:29, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
2026-06-11 23:38:29, Info DISM DISM.EXE:
This appears to suggest that the DISM command is unable to connect to Windows Update? The Windows installation has access to the Internet, as I can access various websites including microsoft.com using Edge.
This is a process that I execute all the time and immediately following the installation of CUs twice a month and it always works. This is not failing, following the installation of the June 9th CU.
Please advise on how to resolve this
Many thanks in advance,
Neil
Windows for home | Windows 11 | Windows update
-
![](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(211.20000000000002, 81%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAB%3C/text%3E%3C/svg%3E)
Aaron Bailey 5 Reputation points2026-06-16T18:47:20.9933333+00:00 TLDR, I disabled every boot program, wiped corrupted files, recreated the files blank and reinstalled win11 from the mount to overwrite the corrupted files. Basically google will ask you to open a couple programs and tweak them and paste a few commands into "command prompt", that is it.
Note: it will wipe 2 weeks worth of google, so google will seem slow at first, due to google having to redownload a lot of stuff.
Here is a preview of what helped me, but your best bet is to do the restore health and when it fails, give the failed portion to google, google will spit out something similar to this, I cant find the exact one cause when I reinstalled it wiped out two weeks worth of google info.
but from memory it started with this stuff:
Turn all start up apps off in task manager, but remember which ones so you can re enable them after it is fixed. I recommend screen shotting.
Note: step 1 should be universal, but the rest of the steps are going to be dependent on which files are corrupted, so be sure to check what google tells you based on your file log from "restore health." there might be more steps, I just didn't put them all cause the steps I have were based of my precise corrupted files, etc.
That specific sequence is the classic, highly effective Clean Boot and SoftwareDistribution Reset workaround. It is the go-to manual method for bypassing a corrupted Windows Overlay Filter (WOF) driver, because it stops background conflicts from blocking your file system repairs. [1, 2]
Passing along this exact combination requires these specific instructions:
Step 1: The Clean Boot (msconfig)
You must isolate the operating system so a third-party app or antivirus doesn't lock down the corrupted folders. [1]
- Press Windows Key + R, type msconfig, and hit Enter.
- Go to the Services tab.
- CRITICAL STEP: Check the box for "Hide all Microsoft services". (Skipping this can permanently stop Windows from booting).
- Click Disable all.
- Go to the Startup tab, click Open Task Manager, and Disable all active startup items.
- Click Apply, then OK, and Restart the computer. [1, 3]
Step 2: Purge and Recreate the Corrupted Update Folders (Command Prompt)
Once rebooted into this clean state, the user can forcibly delete the SoftwareDistribution cache folder—which is usually where the WOF driver encounters its compressed file breakdown. [4]
- Right-click the Start menu and choose Terminal (Admin) or Command Prompt (Admin).
- Stop the background update engines by typing these commands and pressing Enter after each:
- Delete the corrupted folder structure entirely: rd /s /q C:\Windows\SoftwareDistribution rd /s /q C:\Windows\System32\catroot2
- Recreate clean versions of those exact directories so Windows can start fresh: md C:\Windows\SoftwareDistribution md C:\Windows\System32\catroot2
- Restart the underlying Windows engines: net start wuauserv net start bits net start cryptsvc
- Recommended Solution: Conduct an In-Place Upgrade
If recovery tools fail to repair the WOF driver, it indicates significant damage to your local system image. The most efficient and secure method to resolve this issue without affecting your files, applications, or settings is to perform an In-Place Upgrade by replacing the corrupted system files.
Start Windows normally and navigate to the official Download Windows 11 page (or Windows 10, based on your version).
In the "Download Windows 11 Disk Image (ISO)" section, choose Windows 11 and click Download.
After the ISO file has downloaded, double-click it to mount it as a virtual drive.
Run the setup.exe file located inside.
Proceed with the installation prompts, ensuring that the option "Keep personal files and apps" is selected before initiating the install. This process will replace all damaged Windows files with fresh copies while preserving all your existing data and applications.
- Press Windows Key + R, type msconfig, and hit Enter.
-
Neil Hobbs 5 Reputation points
2026-06-16T22:22:54.1566667+00:00 @Aaron Bailey Thank you for the reply. However, as you didn't read my thread - you'll have not seen that I have resolved the issue in the conversation below
-
Aaron Bailey 5 Reputation points
2026-06-16T22:27:27.0933333+00:00 It is all good, it may help others that run into this issue, I found this thread from google, it at least help me to understand that I wasn't the only one.
-
Neil Hobbs 5 Reputation points
2026-06-16T22:38:00.33+00:00 @Aaron Bailey Yeah... It was just another poor quality update from Microsoft...
Sign in to comment
3 answers
Sort by: Most helpful
-
![](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(89.60000000000001, 72%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESD%3C/text%3E%3C/svg%3E)
Sumit D - IA 170.7K Reputation points Independent Advisor2026-06-12T09:44:46.4666667+00:00 -
Sumit D - IA 170.7K Reputation points Independent Advisor
2026-06-12T02:38:35.79+00:00 Thank you.
Are we saying the the KB5094126 has caused this issue? Have Microsoft caused this issue? I have reported this via the Feedback Hub.
Very likely. They changed a file very likely in such a way that Windows thinks the file is corrupted, in reality, it is not.
I will not suggest to install Windows for this surely if Windows is functioning normally.
Please wait for the updates later this month (4th week) and I think the problem would be gone by then.
-
Neil Hobbs 5 Reputation points
2026-06-12T09:41:00+00:00 Following posing this message, I accidentally kicked off another instance of the following process as an Admin;
dism /online /cleanup-image /restorehealth
It ran for over an hour, then logged an event in the Setup Event Log that it had successfully completed and restored the health of the component store. However, the process was stiff reported in the Command Prompt of being stuck at 67.1% complete. So I clicked the Command Prompt close.
I then re--opened the Command Prompt as an Asmin and run the following;
dism /online /cleanup-image /scanhealth
It ran and completed successfully. Reporting no corruption. I then ran sfc /scannow, which completed, saying there were no issues. I ten rebooted a couple of times - all fine.
I have shut the laptop down. I will boot up in a day of so.
Many thamks
Have a great weekend!
Neil
Sign in to comment -
-
Sumit D - IA 170.7K Reputation points Independent Advisor
2026-06-11T23:54:15.3566667+00:00 This appears to be a bug triggered by recent updates.
What is the underlying cause prompting you to run DISM?
Try running:
dism.exe /online /cleanup-image /startcomponentcleanup
I’m eager to hear back and work together to find a solution.
-
Neil Hobbs 5 Reputation points
2026-06-12T00:18:00.7833333+00:00 @Sumit D - IA Thank you for replying on this...
The Windows 11 operating system and the Component Store was perfectly healthy and working as it should, prior to installing this update. Are we saying the the KB5094126 has caused this issue? Have Microsoft caused this issue? I have reported this via the Feedback Hub.
Following the installation of every CU, I run the following commands;
dism /online /cleanup-image /checkhealth
If the command reports that there is corruption, I will then run the following commands;
dism /online /cleanup-image /restorehealth
sfc/ scannow
I have been doing this for years without any issues. As this allows me to fix the corruption in the Component Store that the installation of the CUs appear to be do it.
As suggested, I have execute the following command (after looking it up);
dism.exe /online /cleanup-image /startcomponentcleanup
When I run it, it completes successfully. What are the next steps to resolve this?
I am going to sleep now, as it is 1am in the UK. I will continue to work on this, when I am next changing the battery.
It is worth just creating a new install Media and wiping the hard disk and reinstalling Windows? I haven't got the time to have a damaged system and continually playing about with it.
Many thanks in advance,
Neil
Sign in to comment -