[SOLVED] Win 10: Feature update to Windows 10, version 1803: Error 0x800700c1

O

oliz

Member
Joined
Dec 30, 2018
Posts
15
Unable to install Feature update to Windows 10, version 1803. Tried so many ways but still failed. I ran the SFC and DISM that show below.
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




Error: 193


An initialization error occurred.
For more information, review the log file.


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


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 found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.


CBS.zip - Google Drive
 
Hello and welcome

Due to the precise nature of your corruption, you will receive help from a user named Bruce1270. He's one of our senior trainees here who's in his final phase 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.
 
Hello and welcome to sysnative. My name is Bruce1270 and I will be assisting you.

I will need to get your COMPONENTS hive. Please do the following

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.
 
Hi

Please do the following

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.



  1. Please download the file SFCFix.zip to your desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  2. Save any open documents and close all open windows.
  3. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  4. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  5. SFCFix will now process the script.
  6. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  7. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put tags around the log to break up the text.
 

Attachments

SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-01-05 20:54:02.243
Microsoft Windows 10 Build 15063 - amd64
Using .zip script file at C:\Users\Oliver Zhao\Desktop\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\winsxs\manifests\x86_microsoft-windows-ie-ieshims_31bf3856ad364e35_11.0.15063.1356_none_df0d44f4b3795735.manifest


Successfully copied file C:\Users\Oliver Zhao\AppData\Local\niemiro\Archive\manifests\x86_microsoft-windows-ie-ieshims_31bf3856ad364e35_11.0.15063.1356_none_df0d44f4b3795735.manifest to C:\WINDOWS\winsxs\manifests\x86_microsoft-windows-ie-ieshims_31bf3856ad364e35_11.0.15063.1356_none_df0d44f4b3795735.manifest.


Successfully restored ownership for C:\WINDOWS\winsxs\manifests\x86_microsoft-windows-ie-ieshims_31bf3856ad364e35_11.0.15063.1356_none_df0d44f4b3795735.manifest
Successfully restored permissions on C:\WINDOWS\winsxs\manifests\x86_microsoft-windows-ie-ieshims_31bf3856ad364e35_11.0.15063.1356_none_df0d44f4b3795735.manifest
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.1.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2019-01-05 20:54:02.572
Script hash: WAtVE0qptPyyIFn3xGjHg7AME6kzLi7RkkGu40QtQT0=
----------------------EOF-----------------------
 
Excellent.

Please also run this script.

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.



  1. Please download the file SFCFix.zip to your desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  2. Save any open documents and close all open windows.
  3. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  4. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  5. SFCFix will now process the script.
  6. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  7. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put tags around the log to break up the text.
 

Attachments

SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-01-06 11:30:35.716
Microsoft Windows 10 Build 15063 - amd64
Using .zip script file at C:\Users\Oliver Zhao\Desktop\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\winsxs


Successfully created directory tree \\?\C:\WINDOWS\winsxs\winsxs\amd64_microsoft-windows-m..namespace-downlevel_31bf3856ad364e35_10.0.15063.0_none_d878b3e9b9e90743.


Successfully copied file C:\Users\Oliver Zhao\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-m..namespace-downlevel_31bf3856ad364e35_10.0.15063.0_none_d878b3e9b9e90743\api-ms-win-core-processenvironment-l1-2-0.dll to C:\WINDOWS\winsxs\winsxs\amd64_microsoft-windows-m..namespace-downlevel_31bf3856ad364e35_10.0.15063.0_none_d878b3e9b9e90743\api-ms-win-core-processenvironment-l1-2-0.dll.


Successfully restored ownership for C:\WINDOWS\winsxs
Successfully restored permissions on C:\WINDOWS\winsxs
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.1.0 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2019-01-06 11:30:39.533
Script hash: fRTChuhS2d1tZ96rnUeiHLDRYoLHmjUDIlYL83G+Og0=
----------------------EOF-----------------------
 
Ok. Please run the following

SFC Scan

1. To open an elevated command prompt, use the Windows+X keyboard combination.
2. From the menu returned, click on Command Prompt (Admin). Accept any UAC prompts.
3. When command prompt opens, copy and paste the following command into it, press enter

sfc /scannow

Wait for this to finish before you continue

4. copy and paste %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
5. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload to SendSpace and just provide the link here.
 
I can't create a CBS.txt. Am I suppose to go to the location and copy it?


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 found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.


C:\WINDOWS\system32>%windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
The process cannot access the file because it is being used by another process.
 
Hi, sorry there was an error in my script so SFC has not fixed the issue.

Please run the following amended script.

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.



  1. Please download the file SFCFix.zip to your desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  2. Save any open documents and close all open windows.
  3. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  4. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  5. SFCFix will now process the script.
  6. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  7. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put tags around the log to break up the text.
 

Attachments

SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-01-08 08:28:48.185
Microsoft Windows 10 Build 15063 - amd64
Using .zip script file at C:\Users\Oliver Zhao\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-core-processenvironment-l1-2-0.dll


Successfully copied file C:\Users\Oliver Zhao\AppData\Local\niemiro\Archive\amd64_microsoft-windows-m..namespace-downlevel_31bf3856ad364e35_10.0.15063.0_none_d878b3e9b9e90743\api-ms-win-core-processenvironment-l1-2-0.dll to C:\WINDOWS\winsxs\amd64_microsoft-windows-m..namespace-downlevel_31bf3856ad364e35_10.0.15063.0_none_d878b3e9b9e90743\api-ms-win-core-processenvironment-l1-2-0.dll.


Successfully restored ownership for C:\WINDOWS\winsxs\amd64_microsoft-windows-m..namespace-downlevel_31bf3856ad364e35_10.0.15063.0_none_d878b3e9b9e90743\api-ms-win-core-processenvironment-l1-2-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-core-processenvironment-l1-2-0.dll
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.1.0 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2019-01-08 08:28:48.510
Script hash: MnLP7BOq066hq4y4ibrJQvHCHfPFmNeXrhZ1setXCIk=
----------------------EOF-----------------------
 
It works, so what's next?


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.

View attachment CBS.zip
 
Please do the following

FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

Then

Please try the update again. If it fails, please attach the CBS.log.
 

Attachments

Hi, first thank you so much for solving the problem that confused me for several months, and after Windows Resource Protection did not find any integrity violations, Windows automatically update to version 1803. So am I still should do the following?
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top