Problem with Windows Update; 80070490 error on two updates

S

Sessh

Member
Joined
Nov 13, 2016
Posts
13
Hello, I was hoping that someone could help me out here. The computer this is occurring on is brand new and initially had problems with Windows Update working properly, but KB3172605 fixed that. Many other updates worked in a group of 19 in my first major update, but two of them failed. Those two are KB3078601 and KB3109094 which both give me an 80070490 error. My machine is running Windows 7 Professional 64-bit. The computer has no other issues and I have been avoiding even trying to update NET framework to 4.6.1 until these other two are sorted out. After some reading, I've also decided that the rollup update should be avoided and has also not been installed.

I have tried many solutions including:

- Running the Windows Update Diagnostic Tool which couldn't fix the issue
- sfc /scannow and following that up with SFCFix which turned up no issues
- Tried installing Windows Update KB947821 which was successful, but did not fix the issue
- Tried resetting Windows Update

Nothing has worked and since I am completely out of options now, I've come here for your help which I will hopefully receive.
 
I installed NET Framework 4.6.1 with no problems at all, but those other two still refuse to update.

Also, I am having problems uploading my CBS folder. When I try to attach it using the paperclip icon, it uploads, but does not appear in the list for me to attach. I then followed the instructions in the Posting Instructions thread assuming my CBS folder was too large and those instructions produced this in the SFCFix.txt it created.

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-11-15 19:32:19.139
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\User\Desktop\SFCFixScript.txt [0]








Collect::
File upload aborted - no thread.
Collect:: directive failed to complete successfully.








Failed to process all directives successfully.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2016-11-15 19:32:58.991
Script hash: zyFfBWbS3fxgTqdEHaWo9HHm8G4WJRx4eoZYPA0zvak=
----------------------EOF-----------------------
Click to expand...
 
Hi there Sessh!

Let's start with the System Update Readiness Tool.

System Update Readiness Tool (SURT)

Download and run the System Update Readiness Tool for your version of Windows here: System Update Readiness Tool

NOTE: If you aren't sure if your Windows installation is 32-bit or 64-bit, check here: How to determine whether a computer is running a 32-bit version or 64-bit version of the Windows operating system

This tool will take some time to complete - when it has finished, attach C:\Windows\Logs\CBS\CheckSUR.log with your reply.
 
zcomputerwiz said:
Hi there Sessh!

Let's start with the System Update Readiness Tool.

System Update Readiness Tool (SURT)

Download and run the System Update Readiness Tool for your version of Windows here: System Update Readiness Tool

NOTE: If you aren't sure if your Windows installation is 32-bit or 64-bit, check here: How to determine whether a computer is running a 32-bit version or 64-bit version of the Windows operating system

This tool will take some time to complete - when it has finished, attach C:\Windows\Logs\CBS\CheckSUR.log with your reply.
Click to expand...

I already ran this tool and uploaded my CBS folder to your servers (it was too big to attach here), so I will just give you the CheckSUR.log in the folder I uploaded to the server.

View attachment CheckSUR.log
 
Code: 
	CSI C Mark Deployment Missing	0x00000000	c!avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_49391d6d8244622b	x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_a338d8ea2df29efb	
	CSI C Mark Deployment Missing	0x00000000	c!policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_ef17e13d91c55d96	amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_499a1b14d5902dfc	
	CSI C Mark Deployment Missing	0x00000000	c!policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_36c51814a641869c	x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_914751ebea0c5702	
	CSI C Mark Deployment Missing	0x00000000	c!avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_020285fe6d6e0580	amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2	
	CSI C Mark Deployment Missing	0x00000000	c!policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_364e78aca69bba41	x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_962753dde6e08635	
	CSI C Mark Deployment Missing	0x00000000	c!avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_49afbcd581ea2e86	x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8

Let's try removing the incomplete keys.

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 file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - 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 SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. 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.

View attachment SFCFix.zip

Once SFCFix has completed, run SURT again and attach C:\Windows\Logs\CBS\CheckSUR.log
 
I have done as you asked. Here's the information and file you requested:

Code: 
SFCFix version 3.0.0.0 by niemiro.Start time: 2016-11-21 15:11:10.084
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\User\Desktop\SFCFix.zip [0]








RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_a338d8ea2df29efb.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_499a1b14d5902dfc.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_914751ebea0c5702.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_962753dde6e08635.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8.


Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_a338d8ea2df29efb.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_499a1b14d5902dfc.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_914751ebea0c5702.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_962753dde6e08635.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8.


Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_a338d8ea2df29efb with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_499a1b14d5902dfc with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_914751ebea0c5702 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_962753dde6e08635 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8 with error code ERROR_FILE_NOT_FOUND.
RegistryScript:: directive failed to complete successfully.








Failed to process all directives successfully.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 6 datablocks.
Finish time: 2016-11-21 15:11:10.624
Script hash: gLn6XP2EXN2DPVksfnLcMggvCpk6PCz4SKxX8Hx/3iA=
----------------------EOF-----------------------

Might as well add that those two updates still fail to install with the same error code.
 

Attachments

Very good. Please zip and attach C:\Windows\Logs\CBS\CBS.log
If the zip is larger than 8MB, please use a file sharing service such as OneDrive, DropBox, SendSpace, etc. and include the link with your reply.
 
Looks like there may be a problem with KB3192403.

Let's try reinstalling it:

Install Update with DISM

  1. Download the update MSU here: http://www.microsoft.com/downloads/details.aspx?FamilyId=9d24bc12-bec3-4720-a58e-1bec1bb04012
  2. Copy the MSU file to a convenient location (such as C:\temp).
  3. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  4. When you see Command Prompt on the list, right-click on it and select Run as administrator
  5. When command prompt opens, copy and paste the following commands into it, press enter after each

    cd C:\temp

    replace C:\temp with your path if different

    expand {update name}.msu -f:* C:\temp

    replace {update name} with the name of the MSU file downloaded in step 1

    DISM.exe /Online /Add-Package /PackagePath:C:\temp\{update name}.cab

  6. You should receive the message:
    The operation completed successfully.
  7. Make sure to allow the computer to restart if prompted.

    If you receive any other message:
  8. Right-click on the Command Prompt window and click Select All, this will invert all of the colours by selecting the text, now press enter. All of this text is now copied.
  9. Paste (Ctrl+V) it into your next post please.
 
Code: 
Microsoft Windows [Version 6.1.7601]Copyright (c) 2009 Microsoft Corporation.  All rights reserved.


C:\Windows\system32>cd/


C:\>cd temp win


C:\Temp Win>expand windows6.1-kb3192403-x64.msu -f:* C:\Temp Win
Microsoft (R) File Expansion Utility  Version 6.1.7600.16385
Copyright (c) Microsoft Corporation. All rights reserved.


windows6.1-kb3192403-x64.msu: Destination directory required for a multi-file CAB.




C:\Temp Win>

Been awhile since I worked in DOS; used to love it. Anyway, I even tried creating a Temp folder inside the Temp Win (I already have a "Temp" folder in C: when USB3 stuff was installed) and extracting it there, but same message. Am I doing something wrong? It seems a destination directory is being given either way.
 
Try putting the last C:\Temp Win in quotes, so the command should read:

Code: 
expand windows6.1-kb3192403-x64.msu -f:* "C:\Temp Win"

The DISM command will require similar modification:

Code: 
DISM.exe /Online /Add-Package /PackagePath:"C:\temp win\windows6.1-kb3192403-x64.cab"
 
The update completed successfully and I just rebooted. Should I try those two updates again?
 
One of the two was already installed and the other installed without issues. I updated the rest of the security updates for Framework 4.6.1 and the November Quality Rollup without issues. Everything is up to date. Thanks a lot, Z!

I am a WinXP veteran, but this is my first Windows 7 PC. Did things get messed up because of something I did or did something just go wrong with one of the updates?
 
Glad to help! :thumbsup2:

I think something went wrong with one of the updates, not anything you did :)
 
You must log in or register to reply here.
Back
Top