When you attempt to clean up the component store using the following DISM command on a Windows 11 24H2 or 25H2 system, the error code 1726 may occur.
DISM /Online /Cleanup-Image /StartComponentCleanup
Deployment Image Servicing and Management tool Version: 10.0.26100.5074 Image Version: 10.0.26200.7462 [== 5.8% ] Error: 1726 The remote procedure call failed. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
Resolution
Step 1: Backup the CBS registry key
Please backup the CBS key using the following command from admin Command Prompt:
reg export "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing" "C:\CBS.reg" /y
Step 2: Delete the following registry keys
Launch Regedit.exe.
Delete the following keys:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-SmbDirect-FOD-Package-Wrapper~31bf3856ad364e35~amd64~~10.0.26100.1742] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-SmbDirect-FOD-Package~31bf3856ad364e35~amd64~~10.0.26100.1742]
That should fix the DISM error 1726.
Step 3: Rerun the component store cleanup
Run:
DISM /Online /Cleanup-Image /StartComponentCleanup
To check the effectiveness of the cleanup, run this command:
DISM /Online /Cleanup-Image /AnalyzeComponentStore
Note: The above fix is specific to Windows 11 24H2 and 25H2 systems. It doesn’t apply to earlier builds or other Operating Systems. See also: WinSxS folder not cleaning up after Windows update – Microsoft Q&A
One small request: If you liked this post, please share this?
One "tiny" share from you would seriously help a lot with the growth of this blog. Some great suggestions:- Pin it!
- Share it to your favorite blog + Facebook, Reddit
- Tweet it!