[SOLVED] [10v1703b15063 x64] WU 0x800700C1, DISM error 193

Rkl122 · Jan 27, 2018

Hello, I'm new to this forum. My Windows Update fails with error 0x800700C1. I've tried to fix with sfc /scannow, DISM, and an inplace repair/install using WU assistant. All fail. DISM /onlline commands give a 193 error. Everything I've tried is contained in this thread:

HTML:

https://www.tenforums.com/installation-upgrade/102737-win-10-1703-how-fix-broken-dism-hence-windows-update.html

I have followed the pre-posting directions, and the CBS folder is attached. Note that SFCfix crashed, once at stage 6, once immediately. I chose the option to send the crash files to your server.

SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-01-27 16:43:46.691
Microsoft Windows 10 Build 15063 - amd64
Not using a script file.

SFCFix version 3.0.0.0 by niemiro has encountered an unhandled exception.
Currently storing 0 datablocks.
Finish time: 2018-01-27 16:44:56.312
----------------------EOF-----------------------

Possible relevant info: this computer is an 8 year old Dell, with an AMD graphics card.

Would appreciate any help. Thank you, -Ron

Sysnative Windows Update · Jan 27, 2018

Re: [Win 10x64 1703 b 15063.850]WinUpdate [error 0x800700C1], DISM [error 193]failure

Hello and welcome to Sysnative!

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

SFC Scan

Click on the Start button and in the search box, type Command Prompt
When you see Command Prompt on the list, right-click on it and select Run as administrator
When command prompt opens, copy and paste the following commands into it, press enter after each

sfc /scannow

Wait for this to finish before you continue

copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Rkl122 · Jan 28, 2018

Re: [Win 10x64 1703 b 15063.850]WinUpdate [error 0x800700C1], DISM [error 193]failure

As requested, thank you. SFC completed without error this time. I had to zip cbs.txt.

Code:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-01-28 09:14:34.554
Microsoft Windows 10 Build 15063 - amd64
Using .zip script file at C:\Users\RON\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-m..namespace-downlevel_31bf3856ad364e35_10.0.15063.0_none_d878b3e9b9e90743\api-ms-win-service-winsvc-l1-1-0.dll
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-m..namespace-downlevel_31bf3856ad364e35_10.0.15063.0_none_4ca6f0eece80ccd1\API-MS-Win-Eventing-Provider-L1-1-0.dll
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-edition-transmogrifier_31bf3856ad364e35_10.0.15063.0_none_26a4ac3873fd1da9\TransmogProvider.dll
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-d..ing-management-core_31bf3856ad364e35_10.0.15063.0_none_3c47ff3e638dd49c\FolderProvider.dll

Successfully copied file C:\Users\RON\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-m..namespace-downlevel_31bf3856ad364e35_10.0.15063.0_none_d878b3e9b9e90743\api-ms-win-service-winsvc-l1-1-0.dll to C:\Windows\winsxs\amd64_microsoft-windows-m..namespace-downlevel_31bf3856ad364e35_10.0.15063.0_none_d878b3e9b9e90743\api-ms-win-service-winsvc-l1-1-0.dll.
Successfully copied file C:\Users\RON\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-m..namespace-downlevel_31bf3856ad364e35_10.0.15063.0_none_4ca6f0eece80ccd1\API-MS-Win-Eventing-Provider-L1-1-0.dll to C:\Windows\winsxs\amd64_microsoft-windows-m..namespace-downlevel_31bf3856ad364e35_10.0.15063.0_none_4ca6f0eece80ccd1\API-MS-Win-Eventing-Provider-L1-1-0.dll.
Successfully copied file C:\Users\RON\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-edition-transmogrifier_31bf3856ad364e35_10.0.15063.0_none_26a4ac3873fd1da9\TransmogProvider.dll to C:\Windows\winsxs\amd64_microsoft-windows-edition-transmogrifier_31bf3856ad364e35_10.0.15063.0_none_26a4ac3873fd1da9\TransmogProvider.dll.
Successfully copied file C:\Users\RON\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-d..ing-management-core_31bf3856ad364e35_10.0.15063.0_none_3c47ff3e638dd49c\FolderProvider.dll to C:\Windows\winsxs\amd64_microsoft-windows-d..ing-management-core_31bf3856ad364e35_10.0.15063.0_none_3c47ff3e638dd49c\FolderProvider.dll.

Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-m..namespace-downlevel_31bf3856ad364e35_10.0.15063.0_none_d878b3e9b9e90743\api-ms-win-service-winsvc-l1-1-0.dll
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-m..namespace-downlevel_31bf3856ad364e35_10.0.15063.0_none_d878b3e9b9e90743\api-ms-win-service-winsvc-l1-1-0.dll
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-m..namespace-downlevel_31bf3856ad364e35_10.0.15063.0_none_4ca6f0eece80ccd1\API-MS-Win-Eventing-Provider-L1-1-0.dll
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-m..namespace-downlevel_31bf3856ad364e35_10.0.15063.0_none_4ca6f0eece80ccd1\API-MS-Win-Eventing-Provider-L1-1-0.dll
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-edition-transmogrifier_31bf3856ad364e35_10.0.15063.0_none_26a4ac3873fd1da9\TransmogProvider.dll
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-edition-transmogrifier_31bf3856ad364e35_10.0.15063.0_none_26a4ac3873fd1da9\TransmogProvider.dll
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-d..ing-management-core_31bf3856ad364e35_10.0.15063.0_none_3c47ff3e638dd49c\FolderProvider.dll
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-d..ing-management-core_31bf3856ad364e35_10.0.15063.0_none_3c47ff3e638dd49c\FolderProvider.dll
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2018-01-28 09:14:39.444
Script hash: Oib7KdjvjUbSNZDhu4y1LX13dfhqGRs2ko4FuFB5XsI=
----------------------EOF-----------------------

FYI:

Code:

Microsoft Windows [Version 10.0.15063]
(c) 2017 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.

C:\Windows\system32>
C:\Windows\system32>copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
        1 file(s) copied.

Sysnative Windows Update · Jan 28, 2018

Great! Try DISM now.

Rkl122 · Jan 28, 2018

Well this is further than I got on my own :) I'm attaching the zipped cbs.log. I see it has errors associated with this last DISM session. I could look up how to "use the source option," but I'll await your instructions. I will also reboot my computer now.

Code:

Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\Windows\system32>Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

[==========================100.0%==========================]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source | Microsoft Docs.

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

C:\Windows\system32>

Sysnative Windows Update · Jan 28, 2018

I see the issue. Please standby while I gather the files:

Code:

(p)    CBS MUM Corrupt            Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0
(p)    CSI Payload Corrupt            wow64_microsoft-windows-w..owsupdateclient-aux_31bf3856ad364e35_10.0.15063.0_none_b05c1ac02a894d97\wups.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt    (Fixed)    amd64_netfx-system.management_b03f5f7f11d50a3a_10.0.15063.0_none_db2db1946c97c2bc\System.Management.dll
(p)    CSI Payload Corrupt            wow64_microsoft-windows-w..ient-printuisupport_31bf3856ad364e35_10.0.15063.0_none_88fd44c55c50c95b\wudriver.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            wow64_microsoft-windows-inputservice_31bf3856ad364e35_10.0.15063.0_none_d55254dca6b9e13e\InputService.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_microsoft-windows-c..riencehost.appxmain_31bf3856ad364e35_10.0.15063.0_none_13cc520b866eaf57\text.js
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_netfx4-sos_dll_b03f5f7f11d50a3a_4.0.14917.0_none_492466401c9a67be\SOS.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_netfx4-sos_dll_b03f5f7f11d50a3a_4.0.14917.0_none_01772f69081e3eb8\SOS.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_mscorlib_b77a5c561934e089_4.0.14917.0_none_3b72063c9001e313\mscorlib.dll
Repair failed: Missing replacement payload.

Rkl122 · Jan 28, 2018

Standing by....

Rkl122 · Jan 29, 2018

Well guess what. Problem solved. 1703 automatically upgraded itself today to 1709 (build 16299.125). After the upgrade, I ran the dism command shown below and checked DISM.log. Attached. There are no errors in it, but there are three warnings. Are these anything to be concerned about?

Seems like that single script (above) went a long way. Thank you!

Code:

Microsoft Windows [Version 10.0.16299.125]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.16299.15

Image Version: 10.0.16299.125

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\WINDOWS\system32>

This experience seems to contradict the conclusion drawn in related threads that a 193 error can only be resolved by a reinstall. Would appreciate any insight as to what that script actually did, and what caused this problem in the first place.

Many thanks, -Ron

Sysnative Windows Update · Jan 29, 2018

Thanks for letting me know. Everything is in order. I will mark the thread as solved!

Search

Search

[SOLVED] [10v1703b15063 x64] WU 0x800700C1, DISM error 193

Rkl122

Member

Attachments

Sysnative Windows Update

Inactive

Attachments

Rkl122

Member

Attachments

Sysnative Windows Update

Inactive

Rkl122

Member

Attachments

Sysnative Windows Update

Inactive

Rkl122

Member

Rkl122

Member

Attachments

Sysnative Windows Update

Inactive