[SOLVED] Win10: Windows Update seems ok but sfc and dism failing

calanan · Nov 11, 2015

I've been trying to diagnose some odd behavior on this Windows 10 machine that very recently upgraded from Win 7 to Win 10, such as when I try to open "Add or remove programs" the settings window will open blank and hang as "not responding" (sometimes for up to 30 seconds) before just closing without any errors.

Although Windows Update appears to be running fine, I am seeing the following errors when I try to run either sfc /scannow or dism.exe /online /cleanup-image /restorehealth.

Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Windows Resource Protection could not start the repair service.

C:\WINDOWS\system32>dism.exe /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.10240.16384

Image Version: 10.0.10240.16384

Error: 193

%1 is not a valid Win32 application.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

Here are links to the dism.log Microsoft services and the CBS.log Microsoft services thanks!

BrianDrab · Nov 11, 2015

Hello and welcome

Due to the precise nature of your corruption, you will receive help from a user named CKing123. He's one of our senior trainees here who's in his final phrase of his studies and needs to gain some real world experience in specific areas of Windows Update. This means that he'll be assisting you, but that I will first need to double check and approve his fixes before he posts them to you. If anything this is a good thing for you because it means that you've got at least two of us watching over your thread, but it will unfortunately add a slight delay between each reply. I hope that you understand and can accept the need for us to train up new members in this way in order to carry on doing what we do here, however, if for any reason you object to this setup, I will happily take on your thread myself.

Thank you very much for your understanding. We'll be with you very shortly.

calanan · Nov 11, 2015

No worries, sounds good to me!

CKing123 · Nov 11, 2015

Hello calanan! Please do these things:

SFCFix Fix

This fix is very specific for calanan's computer. For everyone else, trying this fix on your own computer might damage your computer. If you are after assistance, create a new thread, and you will be assisted shortly.

Download SFCFix (by niemiro) and move the executable on your Desktop
Download the attached View attachment SFCFix Script.txt and move the archive to your Desktop
Note: Make sure that the file is named SFCFix Script.txt, do not rename it.
Save any work you have open, and close every programs
Drag the SFCFix Script.txt archive file over the SFCFix.exe executable and release it

SFCFix will launch, let it complete
Once done, a file will appear on your Desktop, called SFCFix.txt
Open the file, then copy and paste its content in your next reply

-CKing

calanan · Nov 11, 2015

Thanks, here you go:

SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-11-11 22:39:00.891
Microsoft Windows 8.1 - amd64
Using .txt script file at C:\Users\lamarcagirls\Desktop\SFCFix Script.txt [0]

FileScan::
[0: 1] C:\Windows.old\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_655452efe0fb810b\CbsCore.dll
File is untraceable.
Found: WxA9OcO6ehnd307LFc+7ETLz+R+V+BvdAzRFn3uMWXk=
Found: 6.1.7600.16385
Trace not available.

[1: 1] C:\Windows.old\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_655452efe0fb810b\wcp.dll
File is untraceable.
Found: BDbIty8TPh/ct1gzbyFP1pR4uszqBSHuo0k8Jw/czic=
Found: 6.1.7600.16385
Trace not available.

[2: 1] C:\Windows.old\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_0935b76c289e0fd5\CbsCore.dll
File is untraceable.
Found: d/zbXDLiK/141DiF/t7YU841GWy350cbh/tj4TBuTcE=
Found: 6.1.7600.16385
Trace not available.

[3: 1] C:\Windows.old\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_0935b76c289e0fd5\wcp.dll
File is untraceable.
Found: OL0kw2p/rM11tq62+MAQTwEwfylMEV8YXCEcTJS2NGk=
Found: 6.1.7600.16385
Trace not available.

[4: 1] C:\Windows.old\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\CbsCore.dll
File is untraceable.
Found: gvi8M4WhLwIXTFz+l+7imFpt4iWgBk0/6eWPSEhWjbc=
Found: 6.1.7601.17514
Trace not available.

[5: 1] C:\Windows.old\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_0b66cb34258c936f\CbsCore.dll
File is untraceable.
Found: cBpZqktVFC2+aSmnOkEmVDh3R52Cz/oyD2Ty0LsQKTM=
Found: 6.1.7601.17514
Trace not available.

[6: 1] C:\Windows.old\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_0b66cb34258c936f\wcp.dll
File is untraceable.
Found: biHjLGxOl/HJdtGTPgKu7vxTWXGbhqWwiYWpWP26bCs=
Found: 6.1.7601.17514
Trace not available.

[7: 1] C:\Windows.old\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\wcp.dll
File is untraceable.
Found: w4Omm1z4NNvuTHtWQ3QLpdu978xYoVwbDBKtCKrI3f8=
Found: 6.1.7601.17514
Trace not available.

[8: 1] C:\Windows.old\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\CbsCore.dll
File is untraceable.
Found: gLzJqYJ7q59JpgUFqjT4Jb5PywhHgxW/e/RiWS0fI64=
Found: 6.1.7601.17592
Trace not available.

[9: 1] C:\Windows.old\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\CbsCore.dll
File is untraceable.
Found: /qXLzQYebzR2cOntcmHx/zQzSAFYov8K68jfU5MLcAA=
Found: 6.1.7601.17592
Trace not available.

[10: 1] C:\Windows.old\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\wcp.dll
File is untraceable.
Found: KZNX0ZmWYLdWeVcnq6tSgoLoSSpbx0DQC5Gxd7xpgdQ=
Found: 6.1.7601.17592
Trace not available.

[11: 1] C:\Windows.old\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\wcp.dll
File is untraceable.
Found: eCOJ85xM2eE9X5hHrDPfgrv672z45hUGmNRi8dwnBVk=
Found: 6.1.7601.17592
Trace not available.

[12: 1] C:\$Windows.~BT\Updates\Critical\afb58a1f-0ce3-4874-b83f-5adf9756bd95\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.16439_none_b542b323a998dec7\wcp.dll
File is untraceable.
Found: uvlSVTksQbO5VkO+bA6ibifqyHwtxDpIYNTznwmVdBw=
Found: 10.0.10240.16439
Trace not available.

[13: 1] C:\$Windows.~BT\Updates\Critical\afb58a1f-0ce3-4874-b83f-5adf9756bd95\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.16439_none_11614ea761f64ffd\wcp.dll
File is untraceable.
Found: gnhBcAJmhmbRb+ftqkO/mO3LH91smEJCnxg/pAVOCZs=
Found: 10.0.10240.16439
Trace not available.

[14: 1] C:\$Windows.~BT\Updates\Critical\afb58a1f-0ce3-4874-b83f-5adf9756bd95\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.16439_none_11614ea761f64ffd\cbscore.dll
File is untraceable.
Found: A1wwMjk9Ob3BA8w66h8XcTZvLpBAwC/DdKuHFctSgpA=
Found: 10.0.10240.16439
Trace not available.

[15: 1] C:\$Windows.~BT\Updates\Critical\afb58a1f-0ce3-4874-b83f-5adf9756bd95\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.16439_none_b542b323a998dec7\cbscore.dll
File is untraceable.
Found: 3ZQi5KyPR0SxvvGYZo682Lbx411+uOPDwt7jwYQJkmA=
Found: 10.0.10240.16439
Trace not available.

[16: 1] C:\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.16439_none_b542b323a998dec7\CbsCore.dll
File is untraceable.
Found: 3ZQi5KyPR0SxvvGYZo682Lbx411+uOPDwt7jwYQJkmA=
Found: 10.0.10240.16439
Trace not available.

[17: 1] C:\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.16439_none_b542b323a998dec7\wcp.dll
File is untraceable.
Found: uvlSVTksQbO5VkO+bA6ibifqyHwtxDpIYNTznwmVdBw=
Found: 10.0.10240.16439
Trace not available.

[18: 1] C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.16439_none_11614ea761f64ffd\CbsCore.dll
File is untraceable.
Found: A1wwMjk9Ob3BA8w66h8XcTZvLpBAwC/DdKuHFctSgpA=
Found: 10.0.10240.16439
Trace not available.

[19: 1] C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.16439_none_11614ea761f64ffd\wcp.dll
File is untraceable.
Found: gnhBcAJmhmbRb+ftqkO/mO3LH91smEJCnxg/pAVOCZs=
Found: 10.0.10240.16439
Trace not available.

[20: 1] C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.16464_none_116100d161f6ab1d\CbsCore.dll
File is untraceable.
Found: DYvK5MxnIpJPDCKx26s71vsrcv1LiX4/fmQLJ0HAX0M=
Version number not available.
Trace not available.

[21: 1] C:\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.16464_none_b542654da99939e7\CbsCore.dll
File is untraceable.
Found: xw2OhVPNSvc7axwN91OTDyGjlcfUk5eo3I6ri31YRQo=
Version number not available.
Trace not available.

[22: 1] C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.16464_none_116100d161f6ab1d\wcp.dll
File is untraceable.
Found: uhiGWS01vfTx759kYGGmr+vw4aHVY3fVWeQBqVgyChM=
Version number not available.
Trace not available.

[23: 1] C:\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.16464_none_b542654da99939e7\wcp.dll
File is untraceable.
Found: qnTEcTXZeIiq0bK9Rr+AyxyD7vYIu9RuGAv+OKdzgzU=
Version number not available.
Trace not available.

[24: 1] C:\Windows.old\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.18766_none_0b32a93025b365c1\CbsCore.dll
File is untraceable.
Found: 7s7tr3yITjDLG036wNgVisWXJEuy1uVz0XY/Uxfwswg=
Found: 6.1.7601.18766
Trace not available.

[25: 1] C:\Windows.old\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.18766_none_675144b3de10d6f7\CbsCore.dll
File is untraceable.
Found: khIT46dz9v0p/nBi9+uVO8dzQfy8VpfRdly9IaroNrE=
Found: 6.1.7601.18766
Trace not available.

[26: 1] C:\Windows.old\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.18766_none_0b32a93025b365c1\wcp.dll
File is untraceable.
Found: rsTXSHCDBM9D2vRfbGpAkcVGyJ088auv80X2nsCgNuo=
Found: 6.1.7601.18766
Trace not available.

[27: 1] C:\Windows.old\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.18766_none_675144b3de10d6f7\wcp.dll
File is untraceable.
Found: ghZETeAEZdzI3SlUXdZZ3LAXK5xMEBk8hg2LFqvLSwg=
Found: 6.1.7601.18766
Trace not available.

[28: 1] C:\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.16565_none_b543677da9985065\CbsCore.dll
File is untraceable.
Found: H1FyWSYxPlo+zwsMa+oeKUceVh2j31Q+VpLrTuR4We0=
Found: 10.0.10240.16565
Trace not available.

[29: 1] C:\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.16565_none_b543677da9985065\wcp.dll
File is untraceable.
Found: VwUohFLUfDMCsWqq3fYVvSUqMbwmodgCdCzTnmJfbu0=
Found: 10.0.10240.16565
Trace not available.

[30: 1] C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.16565_none_1162030161f5c19b\CbsCore.dll
File is untraceable.
Found: p3Qf4T/KJnFd7MQgxkRYBVMeOtRkCYWbQ2f0QC7La+0=
Found: 10.0.10240.16565
Trace not available.

[31: 1] C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.16565_none_1162030161f5c19b\wcp.dll
File is untraceable.
Found: 47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=
Version number not available.
Trace not available.

[32: 1] C:\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.16384_none_b5413773a99a53d2\CbsCore.dll
File is untraceable.
Found: NeJALSJ8255MFsvsKWGvmIFOFvXHRh3HNwxFo8N5t3k=
Version number not available.
Trace not available.

[33: 1] C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.16384_none_115fd2f761f7c508\CbsCore.dll
File is untraceable.
Found: SzYjGoEC81eR8i0QB+pcjGf+DrLemZ2XO25PiEgSMso=
Version number not available.
Trace not available.

[34: 1] C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.16384_none_115fd2f761f7c508\wcp.dll
File is untraceable.
Found: GcE28sC6U6lnyEv/pzc0rj6dhSxyX0vADRXtskXL/n8=
Version number not available.
Trace not available.

[35: 1] C:\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.16384_none_b5413773a99a53d2\wcp.dll
File is untraceable.
Found: C0D/zucUbvGaINe/tHYj4BkN7rvQASga5h8paJF+kRA=
Version number not available.
Trace not available.
FileScan:: directive completed successfully.

Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2015-11-11 22:39:17.833
Script hash: MQ+MgyiVGKB7mwUNfV3zT/j/tgzZhPqF18oFoNiQUlA=
----------------------EOF-----------------------

CKing123 · Nov 12, 2015

Thanks! We figured out why SFC and DISM were not working. Here is the fix that should allow you to run them:

SFCFix Fix

This fix is very specific for calanan's computer. For everyone else, trying this fix on your own computer might damage your computer. If you are after assistance, create a new thread, and you will be assisted shortly.

Download SFCFix (by niemiro) and move the executable on your Desktop
Download the attached View attachment SFCFix.zip and move the archive to your Desktop
Note: Make sure that the file is named SFCFix.zip, do not rename it.
Save any work you have open, and close every programs
Drag the SFCFix.zip archive file over the SFCFix.exe executable and release it

SFCFix will launch, let it complete
Once done, a file will appear on your Desktop, called SFCFix.txt
Open the file, then copy and paste its content in your next reply

After it finishes, we will run SFC scan again

SFC Scan
1. Right-click on the Start

button and select Command Prompt (Admin)
2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter

Code:

sfc /scannow

3. Once it finishes, copy and paste the following into the command-prompt window and press Enter.

Code:

copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

4. Once this has completed please go to your Desktop and you will find CBS.txt => Right-click on this file and choose Send To...Compressed (zipped folder). Please upload this zipped file CBS.zip to this thread

Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.

-CKing

calanan · Nov 12, 2015

Thanks, here you go.

sfcfix.txt

SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-11-12 21:08:25.814
Microsoft Windows 8.1 - amd64
Using .zip script file at C:\Users\lamarcagirls\Desktop\SFCFix.zip [0]

PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.16565_none_1162030161f5c19b\wcp.dll

Successfully copied file C:\Users\lamarcagirls\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.16565_none_1162030161f5c19b\wcp.dll to C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.16565_none_1162030161f5c19b\wcp.dll.

Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.16565_none_1162030161f5c19b\wcp.dll
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10240.16565_none_1162030161f5c19b\wcp.dll
PowerCopy:: directive completed successfully.

Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2015-11-12 21:08:27.061
Script hash: Tae/Y6ULxULADNb8DGNvfJnEInLLLZzE9L5SL6klKnU=
----------------------EOF-----------------------

Output of sfc /scannow

Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Windows Resource Protection could not perform the requested operation.

CBS.zip Microsoft services

- mike

CKing123 · Nov 13, 2015

Hello calanan! I think we found the issue here, but to be able to fix it, we need the Components Hive:

Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to SendSpace and just provide the link here.

-CKing

calanan · Nov 13, 2015

Thanks, here is the zip (hope you don't mind, I used my OneDrive)

Microsoft services

CKing123 · Nov 14, 2015

Hello calanan

It appears that your COMPONENTS hive is corrupt beyond repair.

We need to do a repair install of Windows 10 using the Media Creation Tool:

Please download Media Creation Tool
Run the tool
Choose Upgrade This PC
Click Next
Follow the instructions

When it asks you about keeping your files, Make sure to choose to keep everything

If you have any questions, let us know!

This will fix Component Store corruption

-CKing

calanan · Nov 14, 2015

Ugh, ok thanks. Will this work similarly to a first-time upgrade or even a refresh in that any desktop apps will be removed?

CKing123 · Nov 14, 2015

It will work like an in-place upgrade, so basically it keeps your files and programs and upgrades Windows to Windows 10

-CKing

calanan · Nov 14, 2015

Thanks, one last question: For this PC running Win 10 Home (Version 10.0.10240 Build 10240) I should use the "Upgrade now" button that downloads the file "GetWindows10-sds_____________.exe" rather than downloading MediaCreationTool.exe and running it directly?

Just want to be certain before pulling the trigger, thanks!

CKing123 · Nov 14, 2015

calanan said:
Thanks, one last question: For this PC running Win 10 Home (Version 10.0.10240 Build 10240) I should use the "Upgrade now" button that downloads the file "GetWindows10-sds_____________.exe" rather than downloading MediaCreationTool.exe and running it directly?

Just want to be certain before pulling the trigger, thanks!

Download the MediaCreationTool.exe

The GetWindows10-sds is for 7/8.1 (although they can also install using MediaCreationTool)

-CKing

calanan · Nov 14, 2015

Thanks, running MCT now, will follow up later. You folks are the best!

calanan · Nov 14, 2015

Looks good, sfc finished without errors. Is there anything else I should check?

Microsoft Windows [Version 10.0.10586]
(c) 2016 Microsoft Corporation. All rights reserved.

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 did not find any integrity violations.

CKing123 · Nov 14, 2015

calanan said:
Looks good, sfc finished without errors. Is there anything else I should check?

Microsoft Windows [Version 10.0.10586]
(c) 2016 Microsoft Corporation. All rights reserved.

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 did not find any integrity violations.

Click to expand...

The corruptions are fixed, but if you are having other issues, then tell us!

-CKing

Search

Search

[SOLVED] Win10: Windows Update seems ok but sfc and dism failing

calanan

Contributor

BrianDrab

Emeritus

calanan

Contributor

CKing123

Sysnative Staff, Windows Update Senior Analyst

calanan

Contributor

CKing123

Sysnative Staff, Windows Update Senior Analyst

calanan

Contributor

CKing123

Sysnative Staff, Windows Update Senior Analyst

calanan

Contributor

CKing123

Sysnative Staff, Windows Update Senior Analyst

calanan

Contributor

CKing123

Sysnative Staff, Windows Update Senior Analyst

calanan

Contributor

CKing123

Sysnative Staff, Windows Update Senior Analyst

calanan

Contributor

calanan

Contributor

CKing123

Sysnative Staff, Windows Update Senior Analyst