[SOLVED] Windows 10 update error 0x80070246

M

manbungo996

Member
Joined
May 10, 2018
Posts
11
Windows Update gives me Error 0x80070246 when attempting to install update KB4103727.

I've tried to run dism and sfc and both finished successfully, but that didn't fix my problem.

Note that I've removed a faulty RAM stick a couple of days ago, which caused many BSOD errors, so I suspect that there is a corrupted registry key.

Here's my components file to help determine what's wrong and hopefully someone will be able to help me Dropbox - components.zip

Thanks a lot. :D
 
Hello and welcome!

Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Open an elevated Command Prompt and try installing the update just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML file as well as your CBS.log
 
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. You can use the one you already have downloaded.
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.
6. Try updates and attach CBS.log if any fail.
 

Attachments

Fix result of Farbar Recovery Scan Tool (x64) Version: 10.05.2018
Ran by Martin (11-05-2018 12:43:58) Run:1
Running from C:\Users\Martin\Desktop
Loaded Profiles: Martin (Available Profiles: Martin)
Boot Mode: Normal
==============================================


fixlist content:
*****************
CreateRestorePoint:
cmd: REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS
[-HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\e9361bed1bc..223bf63cc78_31bf3856ad364e35_10.0.16299.125_af5763a8fdc9f041]
StartRegedit:
[HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\e9361bed1bc..223bf63cc78_31bf3856ad364e35_10.0.16299.125_af5763a8fdc9f041]
"appid"=hex:65,39,33,36,31,62,65,64,31,62,63,31,35,38,35,66,61,65,66,36,61,32,\
32,33,62,66,36,33,63,63,37,38,2c,20,43,75,6c,74,75,72,65,3d,6e,65,75,74,72,\
61,6c,2c,20,56,65,72,73,69,6f,6e,3d,31,30,2e,30,2e,31,36,32,39,39,2e,31,32,\
35,2c,20,50,75,62,6c,69,63,4b,65,79,54,6f,6b,65,6e,3d,33,31,62,66,33,38,35,\
36,61,64,33,36,34,65,33,35,2c,20,50,72,6f,63,65,73,73,6f,72,41,72,63,68,69,\
74,65,63,74,75,72,65,3d,61,6d,64,36,34,2c,20,76,65,72,73,69,6f,6e,53,63,6f,\
70,65,3d,4e,6f,6e,53,78,53
"CatalogThumbprint"="f3e10cc0cf0e8181233de9f817a64210912bf2cce955e0ab828d199f682545ce"
"p!CBS_package_913_for_kb4056892~31bf3856ad364e35~amd64~~10.0.1.9.4_3d017ac8c64479d9"=hex:4f,\
00,00,00,01,00,00,00,50,61,63,6b,61,67,65,5f,39,31,33,5f,66,6f,72,5f,4b,42,\
34,30,35,36,38,39,32,7e,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,7e,\
61,6d,64,36,34,7e,7e,31,30,2e,30,2e,31,2e,39,2e,34,30,35,36,38,39,32,2d,32,\
33,37,38,5f,6e,65,75,74,72,61,6c,32
"s!CBS_package_913_for_kb4056892~31bf3856ad364e35~amd64~~10.0.1.9.4_3d017ac8c64479d9"=hex:4f,\
00,00,00,00,00,00,00,50,61,63,6b,61,67,65,5f,39,31,33,5f,66,6f,72,5f,4b,42,\
34,30,35,36,38,39,32,7e,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,7e,\
61,6d,64,36,34,7e,7e,31,30,2e,30,2e,31,2e,39,2e,34,30,35,36,38,39,32,2d,32,\
33,37,38,5f,6e,65,75,74,72,61,6c
"p!CBS_package_1112_for_kb4093112~31bf3856ad364e35~amd64~~10.0.1.3._19c3708c6245fdfe"=hex:50,\
00,00,00,01,00,00,00,50,61,63,6b,61,67,65,5f,31,31,31,32,5f,66,6f,72,5f,4b,\
42,34,30,39,33,31,31,32,7e,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,\
7e,61,6d,64,36,34,7e,7e,31,30,2e,30,2e,31,2e,33,2e,34,30,39,33,31,31,32,2d,\
33,30,33,33,5f,6e,65,75,74,72,61,6c,32
"s!CBS_package_1112_for_kb4093112~31bf3856ad364e35~amd64~~10.0.1.3._19c3708c6245fdfe"=hex:50,\
00,00,00,00,00,00,00,50,61,63,6b,61,67,65,5f,31,31,31,32,5f,66,6f,72,5f,4b,\
42,34,30,39,33,31,31,32,7e,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,\
7e,61,6d,64,36,34,7e,7e,31,30,2e,30,2e,31,2e,33,2e,34,30,39,33,31,31,32,2d,\
33,30,33,33,5f,6e,65,75,74,72,61,6c
"i!CBS_package_1112_for_kb4093112~31bf3856ad364e35~amd64~~10.0.1.3._19c3708c6245fdfe"=hex:50,\
00,00,00,01,00,00,00,50,61,63,6b,61,67,65,5f,31,31,31,32,5f,66,6f,72,5f,4b,\
42,34,30,39,33,31,31,32,7e,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,\
7e,61,6d,64,36,34,7e,7e,31,30,2e,30,2e,31,2e,33,2e,34,30,39,33,31,31,32,2d,\
33,30,33,33,5f,6e,65,75,74,72,61,6c,32




*****************


Restore point was successfully created.


========= REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS =========


The operation completed successfully.




========= End of CMD: =========


"HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\e9361bed1bc..223bf63cc78_31bf3856ad364e35_10.0.16299.125_af5763a8fdc9f041" => removed successfully


====> Registry


==== End of Fixlog 12:44:24 ====
 
So, I started the update and the status went to "Installing - 25%" (that it usually reached before failing) and then went back to 10%, then suddenly went to 100%, was stuck there for a while and ultimately failed, giving me Error 0x80073712

View attachment CBS.zip
 
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.


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

Attachments

SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-05-11 13:39:03.647
Microsoft Windows 10 Build 16299 - amd64
Using .txt script file at C:\Users\Martin\Desktop\SFCFixScript.txt [0]








RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_175981b1042175ff5ea5c95a171760b0_31bf3856ad364e35_10.0.16299.371_none_652792ca270d59b7.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\175981b1042..95a171760b0_31bf3856ad364e35_10.0.16299.371_652792ca270d59b7.


Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_175981b1042175ff5ea5c95a171760b0_31bf3856ad364e35_10.0.16299.371_none_652792ca270d59b7.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\175981b1042..95a171760b0_31bf3856ad364e35_10.0.16299.371_652792ca270d59b7.


Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_175981b1042175ff5ea5c95a171760b0_31bf3856ad364e35_10.0.16299.371_none_652792ca270d59b7.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\175981b1042..95a171760b0_31bf3856ad364e35_10.0.16299.371_652792ca270d59b7.
RegistryScript:: directive completed successfully.








Successfully processed all directives.






Failed to generate a complete zip file. Upload aborted.




SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2018-05-11 13:42:41.428
Script hash: FBVOqCm0YoJ4VDwFzKn57ArQ4ZIjiZ7Dyb4aHMw4iWY=
----------------------EOF-----------------------
 
Ran it, the status went to 25% and down to 10% as before, but from there on it continued to progress normally and is now asking for a restart in order to update.

So I guess that did it :dance:

Thank you so much, definitely donating to this site.
 
Soooo there's a problem again. It did go through the KB4103727 update successfully, however when I restarted, a new update was available - Feature update to Windows 10, version 1803, and it was downloading, when all of a sudden it gave an Error 0x80244018 :/
 
1. Download the Media Creation Tool and save this to your desktop. Go ahead and run this as well. Note: Click the Download tool now button when you get to this link.
2. Accept the License Agreement
3. Download the ISO file to your desktop.
4. Double-click on the ISO and then run the setup to try and upgrade your machine.

We want to get the ISO so that you don't have to keep downloading which can take hours. If it fails, provide the same logs.
 
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