1

I have spent several days trying to get DISM to fix corrupted files.

C:\windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan. Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some of them. For online repairs, details are included in the CBS log file located at windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline repairs, details are included in the log file provided by the /OFFLOGFILE flag.

After days of dozens of attempts trying to get DISM to use different sources I was able to get it to work by copying the \Windows\Winsxs folder from another Windows 10 computer to a local folder on the affected computer. From there I was able to run dism /online /cleanup-image /restorehealth /source:c:\tempwinsxs and that fixed 100 of 109 corrupted files.

After that SFC seemed to run clean now:

C:\>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan. Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them. For online repairs, details are included in the CBS log file located at windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline repairs, details are included in the log file provided by the /OFFLOGFILE flag.

Then to repair the last 9 corrupted files I tried the following to no avail:

`dism /online /cleanup-image /restorehealth`
`dism /online /cleanup-image /restorehealth /source:c:\windows\winsxs` - tried using its own sxs files
`dism /online /cleanup-image /restorehealth /source:c:\tempwinsxs` - tried other computer sxs files again.
`dism /online /cleanup-image /restorehealth /source:F:\sources\install.esd:6` - from bootable USB, resource files can't be found
`dism /online /cleanup-image /restorehealth /source:ESD:F:\sources\install.esd:6` - from bootable USB (created from MediaTool: 1 month ago), resource files can't be found, log file shows "The alternate source path directory could not be accessed"
`dism /online /cleanup-image /restorehealth /source:wim:C:\temp\install.wim:1` - after converting bootable USB \sources\install.esd index 6 to wim file, resource files can't be found, log file shows "The alternate source path directory could not be accessed"

But nothing is fixing these 9 files (from CBS.log):

2025-05-29 12:00:30, Info                  CBS    (p)   CSI Payload Corrupt (n)         x86_netfx4-clr_dll_b03f5f7f11d50a3a_4.0.15840.200_none_7dcb9751327e3008\clr.dll
2025-05-29 12:00:30, Info                  CBS    (p)   CSI Payload Corrupt (n)         x86_microsoft-windows-s..-installers-onecore_31bf3856ad364e35_10.0.19041.2905_none_04121013a2785e4a\timezoneai.dll
2025-05-29 12:00:30, Info                  CBS    (p)   CSI Payload Corrupt (n)         x86_microsoft-windows-s..ingstack-base-extra_31bf3856ad364e35_10.0.19041.2905_none_375a8a9dc0658663\FeatureSettingsOverride.dll
2025-05-29 12:00:30, Info                  CBS    (p)   CSI Payload Corrupt (n)         x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.2905_none_21b500c8c45c6e6a\CbsMsg.dll
2025-05-29 12:00:30, Info                  CBS    (p)   CSI Payload Corrupt (n)         x86_microsoft-windows-s..-installers-onecore_31bf3856ad364e35_10.0.19041.3385_none_045af3d1a2407e83\luainstall.dll
2025-05-29 12:00:30, Info                  CBS    (p)   CSI Payload Corrupt (n)         amd64_microsoft-windows-3daudio-hrtfbins_31bf3856ad364e35_10.0.19041.3636_none_b843e5493baebe42\r\DefaultHrtfs.bin
2025-05-29 12:00:30, Info                  CBS    (p)   CSI Payload Corrupt (n)         amd64_microsoft-windows-s..-installers-onecore_31bf3856ad364e35_10.0.19041.2905_none_6030ab975ad5cf80\netfxconfig.dll
2025-05-29 12:00:30, Info                  CBS    (p)   CSI Payload Corrupt (n)         amd64_microsoft-windows-s..ingstack-base-extra_31bf3856ad364e35_10.0.19041.2905_none_9379262178c2f799\netfxconfig.dll
2025-05-29 12:00:30, Info                  CBS    (p)   CSI Payload Corrupt (n)         amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.2905_none_7dd39c4c7cb9dfa0\CbsCore.dll

The only DISM /source that worked was using the copied \windows\winsxs files from the other computer, but apparently that computer doesn't have the matching 9 source files needed for these last 9 corrupted files.

What options do I have left? How can I get these fixed?

========= Requested Further Info ==========

OS Name:    Microsoft Windows 10 Pro
Version:    10.0.19045 Build 19045

Update History: Feature Update to Windows 10, version 22H2 Successfully installed: 8/3/23

Feature update to Windows 10, version 21H2 Successfully installed 4/15/22

Quality Updates: 2025-05 Cumulative update for Win 10 v22H2, KB5058379, installed 5/28/2025

2025-04 .NET framework 3.5,4.8,4.8.1 for Win 10 V22H2, KB5057056, installed 5/21/2025

2025-04 .NET framework, 3.5, 4.8, 4.8.1 for Win 10 v22H2, KB5055683, installed 4/9/2025

It is also important to note that I think it was the KB5057056 update that contributed to things going sideways. My computer had rebooted in the middle of the night and when I got into it that morning everything was messed up. Many of my apps would no longer work:

Chrome ("this app can't run on your PC"), 
Classic Outlook w/ 7 biz accounts - nothing happend BUT this one appears restored now.  Thank God!
Adobe Photoshop: (AdobeOwl.dll/cg.dll is not design to run on windows or it contains an error")
Android Studio: won't start, no error message

MS Visual Studio Code (user) MS Help Viewer 2.3 Composer - PHP Dependency Manager ... a handful of others ...

This is when I started doing a deeper dive into things. And after the 1st reboot during my troubleshooting the HP Bios detected a system Hadrdrive critical failure error on my 2tb SSD harddrive, the tests kept failing but without much detail. But I could still continue with boot and startup Windows. So my take is the update forced the reboot on the computer at the same time it had the SSD issue - don't know if one caused the other - and maybe the update was writing system files that needed to go into the SSD sector that was now corrupt causing many things to not work. The computer had last rebooted a few days prior without any SSD hardware issue or alerts.

From there I ran a system level chkdsk /F /R /X that ran on next bootup. That helped clean some things up and then I immediately backed up all data before I started working on the SFC and DISM commands. Which brought me to this point.

Still at large: The 9 listed above corrupted files and all of the mentioned apps are still not working. Once I get everything normalized and fixed (including apps) I am going to get a new SSD drive, mirror my installation then install the new drive. So far the SSD error, only detected by BIOS at bootup, seems to have had no further impact - but its just a matter of time before it goes.

The 9 listed corrupted files that haven't been able to be fixed yet came from the CBS.log file. Guess I don't understand the relationship of that log file versus the DISM.log file.

@DrMoishe Pippik - aside from the aforementioned apps still not working, everything else seems normal.

Relevant info (I think) from the DISM.log on last run:

2025-05-29 17:34:27, Info                  DISM   DISM Provider Store: PID=15172 TID=15092 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2025-05-29 17:34:27, Warning               DISM   DISM Provider Store: PID=15172 TID=15092 Failed to load the provider: C:\Users\rolin\AppData\Local\Temp\D12EC7E3-7D7F-41D8-9001-EF207D7DB879\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2025-05-29 17:34:27, Info                  DISM   DISM Provider Store: PID=15172 TID=15092 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2025-05-29 17:34:27, Info                  DISM   DISM Provider Store: PID=15172 TID=15092 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
... <snip> ...
2025-05-29 17:35:05, Info                  DISM   DISM Provider Store: PID=15172 TID=15092 Connecting to the provider located at C:\Users\rolin\AppData\Local\Temp\D12EC7E3-7D7F-41D8-9001-EF207D7DB879\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2025-05-29 17:35:05, Info                  DISM   DISM Provider Store: PID=15172 TID=15092 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2025-05-29 17:35:05, Info                  CSI    00000001 Shim considered [l:126]'\??\C:\windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.5853_none_7de3a0ec7cad0695\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2025-05-29 17:35:05, Info                  CSI    00000002 Shim considered [l:123]'\??\C:\windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.5853_none_7de3a0ec7cad0695\wcp.dll' : got STATUS_SUCCESS
2025-05-29 17:35:05, Info                  DISM   DISM Package Manager: PID=15172 TID=15092 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2025-05-29 17:35:05, Info                  CSI    00000001 Shim considered [l:126]'\??\C:\windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.5853_none_7de3a0ec7cad0695\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2025-05-29 17:35:05, Info                  CSI    00000002 Shim considered [l:123]'\??\C:\windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.5853_none_7de3a0ec7cad0695\wcp.dll' : got STATUS_SUCCESS
2025-05-29 17:35:05, Info                  DISM   DISM Package Manager: PID=15172 TID=15092 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
2025-05-29 17:35:05, Info                  DISM   DISM Package Manager: PID=15172 TID=15092 Loaded servicing stack for online use only. - CDISMPackageManager::CreateCbsSession

NEXT: Since posting this and your comments from yesterday I have not take any actions as of yet. I wanted to provide the requested information first and provide more context/detail as to everything that happened to ensure the recommended actions are still the proper course to take.

You mentioned my DISM commands had syntax errors; could you please elaborate? I read dozens of threads, how-tos, etc for DISM and tried so many command iterations - it was quite frustrating.

APPS NOT WORKING - In Settings -> Apps & Features many of the apps that aren't working show the same icon (which appears to be a mini screen shot of File Explorer) or show no icon at all. I am now testing all apps to ensure the open. Most of the ones that aren't working don't have a "Repair" feature either. There are a few that are showing the correct icon but still aren't working (Android Studio, Photoshop).

========== UPDATE #2 ===========

I ran the following: dism /online /cleanup-image /StartComponentCleanup /RestoreHealth and it had no impact, the same 9 files were not repaired and still show as corrupted.

Regarding apps not working, Classic Outlook is the only one that restored through this entire process. Thankfully, all my email and configurations were still there. I went through every app and this is the list that still isn't working:

HP Audio (Repair/Reset didn't work)
Copilot (Repair didn't work)
Adobe PhotoShop CS
Android Studio
Github desktop
Google Chrome
Microsoft Store
my HP
MySQL workbench
PC Healthcheck
Photos (Repair didn't work)
Phone Link
Visual Studio Code
rolinger
  • 141

0 Answers0