Windows Service Pack 1: Error Code 80070490

J

jol22

Well-known member
Joined
Jul 22, 2015
Posts
55
I have tried several times to install the Service Pack 1 update, and no matter which way I go about it, it fails each time with the error code 80070490. I have installed the system update readiness tool, and have tried several tutorials online, none of which worked. It is driving me insane, so I would really appreciate any help on the issue! I have Windows 7.

Here is the link to my CBS log:
https://www.dropbox.com/s/u4rhejp7jgahx2m/CBS.zip?dl=0

Here is what the SFCFix.txt says:

SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-07-26 11:35:24.509
Microsoft Windows 7 - x86
Not using a script file.


AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.


Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2015-07-26 11:45:40.518
----------------------EOF-----------------------
 
Hello and welcome to the forum :)

Please follow the instructions Here to run the System Update Readiness Tool. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:
C:\Windows\Logs\CBS\CheckSUR.log
C:\Windows\Logs\CBS\CheckSUR.persist.log
 
CHECK SUR LOG:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-07-30 14:45
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: 2107
No errors detected


CHECKSUR PESIST LOG:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-07-30 14:45
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: 2107
No errors detected
 
That all looks fine.

SFC /SCANNOW

  1. Click on the
    Win7Orb_zps4dae3b32.jpg
    button. Inside the search box type in CMD
  2. Right click on CMD => Choose Run as Administrator
  3. Inside the Command Prompt windows copy and paste the following command SFC /SCANNOW
  4. Please wait for this to Finish before continuing with the rest of the steps.

Convert CBS.log to CBS.txt

  1. Click on the
    Win7Orb_zps4dae3b32.jpg
    button => Inside the search box copy and paste the following command:
    Code: 
    cmd /c copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  2. Press Enter
  3. Once this has completed please go to your Desktop and you will find CBS.txt, please rename this file to CBS_{Insert forum username here}_{insert todays Date here}.txt For example "CBS_Go The Power_1803.txt"
  4. Please upload CBS_{Username}_{Date}.txt to this thread.

Please Note:: if the file is too big to upload to you next post please upload via Dropbox or One Drive
 
The log is not giving a huge deal of information about what is wrong.

Can you please go the following location C:\Windows\System32\config and look for the following files:
-COMPONENTS
-Any other files that start with the word COMPONENTS
-Or any files that have a similar name to COMPONENTS (it could be spelt different, have a number, a symbol etc)
If you find any please create a folder on your desktop and copy and paste all these files into this folder.
Next can you please zip this folder -> Please name this zip file to COMPONENTS_{Insert forum username here}_{insert todays Date here}.zip For example "COMPONENTS_Go The Power_1803.Zip"
Once done, upload them for me to analyze. The file may be too big to attach to this post, please use either Dropbox or One Drive.

Please run Windows update again, let it fail, once it fails, upload a new CBS log straight away. Windows updates will often store a lot of useful data inside the CBS log when it fails.
 
Do you have the CBS log as well? :)

Please run Windows update again, let it fail, once it fails, upload a new CBS log straight away. Windows updates will often store a lot of useful data inside the CBS log when it fails.
Click to expand...
 
Am I able to have any further help with this problem, as I desperately need this sorted.
 
Hi jol22 -

Sorry for the delay. Go The Power had something come up and asked if I could step in. If you still need assistance please do the following.

Code: 
2015-08-16 15:12:37, Error                 CBS    Failed to resolve package 'Package_2_for_KB2839229~31bf3856ad364e35~x86~~6.1.1.0' [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

Remove Update Manually
 1. Click on the Start
Start%20Orb.jpg
button and in the search box, type Command Prompt
2. When you see Command Prompt on the list, right-click on it and select Run as administrator
3. When command prompt opens, copy and paste the following command into it, press enter
wusa /uninstall /KB:2839229

4. Let me know if it says it was successful or if there are any errors.
 
I ran the above and it says the Update KB2839229 is not installed.
 
Thank you. Now please do the following.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt 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
 

Attachments

SFCFix version2.4.5.0 by niemiro.
Start time:2015-09-05 18:11:46.789
Microsoft Windows7 - x86
Using .txt scriptfile at C:\Users\Jo\Desktop\SFCScript.txt [0]




FileScan::
[0: 1]C:\Windows\servicing\Packages\Package_2_for_KB2839229~31bf3856ad364e35~x86~~6.1.1.0.cat
File isuntraceable.
Found:e80LwOo6eyAzqLhjvdHTjDbn9+uePO9WzkzV9nMbOm4=
Version number not available.
Trace notavailable.



[1: 1]C:\Windows\System32\catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Package_2_for_KB2839229~31bf3856ad364e35~x86~~6.1.1.0.cat
File isuntraceable.
Found:e80LwOo6eyAzqLhjvdHTjDbn9+uePO9WzkzV9nMbOm4=
Version number not available.
Trace notavailable.



[2: 1]C:\Windows\servicing\Packages\Package_2_for_KB2839229~31bf3856ad364e35~x86~~6.1.1.0.mum
File isuntraceable.
Found:vqhSVbTiQ8azWOt2e3ooxIZJtMdPP9UXKRRcHtGJVio=
Version number not available.
Trace notavailable.
FileScan::directive completed successfully.




Successfullyprocessed all directives.
SFCFix version 2.4.5.0by niemiro has completed.
Currently storing0 datablocks.
Finish time:2015-09-05 18:12:36.514
Script hash:klmb1XuMS6D3MyYARVNngPSj4c1cBWAXeitp1TUH/ao=
----------------------EOF-----------------------
 
Thank you. This likely means the issue is in the registry. I need two more pieces of your registry to resolve. Can you do the following?

Step#1 - Export CBS Registry Key

  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type regedit
  2. When you see regedit on the list, right-click on it and select Run as administrator
  3. When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing

  4. Once selected, click File > Export....
  5. Change the Save as type: to Registry Hive Files (*.*)
  6. Name this file CBS (with no file extension) and save it to your Desktop.

Once done please upload this file via Dropbox or One Drive or SendSpace.

Step#2 - Export SideBySide

  1. Click on the Start button and in the search box, type regedit
  2. When you see regedit on the list, right-click on it and select Run as administrator
  3. When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
  4. Once selected, click File > Export....
  5. Change the Save as type: to Registry Hive Files (*.*)
  6. Name this file SxS (with no file extension) and save it to your Desktop.

Once done please upload this file via Dropbox or One Drive or SendSpace.
 
Thank you. Please do the following.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt 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


Then do a Clean Boot of your machine and attempt the SP upgrade again. Let me know how it goes.
 

Attachments

SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-09-06 17:26:07.310
Microsoft Windows 7 - x86
Using .txt script file at C:\Users\Jo\Desktop\SFCScript.txt [0]


RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\ceaee79a245..86185518be4_31bf3856ad364e35_6.1.7601.22318_bdd3ff182c35c141.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\d458a7807d6..965f6b9206e_31bf3856ad364e35_6.1.7601.18113_e82459dc8395017d.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\7bcd0bc0ea3a7b2033a8b863bdd1d38c36e7f7eb9e3cef56ce4cd5f6731b3a6e.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_d458a7807d6cba9a10648965f6b9206e_31bf3856ad364e35_6.1.7601.18113_none_e82459dc8395017d.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-csrsrv_31bf3856ad364e35_6.1.7601.18113_none_cb8d824703a0c682.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-appid_31bf3856ad364e35_6.1.7601.22318_none_59e0fbb029838c63.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-smss_31bf3856ad364e35_6.1.7601.22318_none_aecf9361908de017.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-smss_31bf3856ad364e35_6.1.7601.18113_none_ae40f33e7774c473.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.22318_none_6ec54d052b7f52c5.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.18147_none_6e1a3e46127af050.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-csrsrv_31bf3856ad364e35_6.1.7601.22318_none_cc1c226a1cb9e226.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ceaee79a245e3471199ec86185518be4_31bf3856ad364e35_6.1.7601.22318_none_bdd3ff182c35c141.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\ceaee79a245..86185518be4_31bf3856ad364e35_6.1.7601.22318_bdd3ff182c35c141.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\d458a7807d6..965f6b9206e_31bf3856ad364e35_6.1.7601.18113_e82459dc8395017d.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\7bcd0bc0ea3a7b2033a8b863bdd1d38c36e7f7eb9e3cef56ce4cd5f6731b3a6e.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_d458a7807d6cba9a10648965f6b9206e_31bf3856ad364e35_6.1.7601.18113_none_e82459dc8395017d.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-csrsrv_31bf3856ad364e35_6.1.7601.18113_none_cb8d824703a0c682.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-appid_31bf3856ad364e35_6.1.7601.22318_none_59e0fbb029838c63.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-smss_31bf3856ad364e35_7.1.7601.22318_none_a0400fa71b7488e6.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-smss_31bf3856ad364e35_7.1.7601.18113_none_9fb16f84025b6d42.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-smss_31bf3856ad364e35_6.1.7601.22318_none_aecf9361908de017.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-smss_31bf3856ad364e35_6.1.7601.18113_none_ae40f33e7774c473.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.22318_none_6ec54d052b7f52c5.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.18147_none_6e1a3e46127af050.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-csrsrv_31bf3856ad364e35_6.1.7601.22318_none_cc1c226a1cb9e226.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_d032a0e18f3cce6407050808e549fb50_31bf3856ad364e35_6.1.7601.18113_none_46dba1dcc36c9ad4.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ceaee79a245e3471199ec86185518be4_31bf3856ad364e35_6.1.7601.22318_none_bdd3ff182c35c141.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_132035e5d604be34975710ce1ed18cef_31bf3856ad364e35_6.1.7601.22318_none_faaf788fd4baa8b4.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_63a58a521f96ea70db1141e470bb5474_31bf3856ad364e35_6.1.7601.22318_none_d792e465586e19a9.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_2d2cff3683679dbb91d2bd1bc622d13a_31bf3856ad364e35_6.1.7601.22318_none_1f2437a354c30c4c.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\ceaee79a245..86185518be4_31bf3856ad364e35_6.1.7601.22318_bdd3ff182c35c141 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\d458a7807d6..965f6b9206e_31bf3856ad364e35_6.1.7601.18113_e82459dc8395017d with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\7bcd0bc0ea3a7b2033a8b863bdd1d38c36e7f7eb9e3cef56ce4cd5f6731b3a6e with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_d458a7807d6cba9a10648965f6b9206e_31bf3856ad364e35_6.1.7601.18113_none_e82459dc8395017d with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-csrsrv_31bf3856ad364e35_6.1.7601.18113_none_cb8d824703a0c682 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-appid_31bf3856ad364e35_6.1.7601.22318_none_59e0fbb029838c63 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-smss_31bf3856ad364e35_6.1.7601.22318_none_aecf9361908de017 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-smss_31bf3856ad364e35_6.1.7601.18113_none_ae40f33e7774c473 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.22318_none_6ec54d052b7f52c5 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.18147_none_6e1a3e46127af050 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-csrsrv_31bf3856ad364e35_6.1.7601.22318_none_cc1c226a1cb9e226 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_ceaee79a245e3471199ec86185518be4_31bf3856ad364e35_6.1.7601.22318_none_bdd3ff182c35c141 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
RegistryScript:: directive failed to complete successfully.


Failed to process all directives successfully.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 13 datablocks.
Finish time: 2015-09-06 17:26:23.223
Script hash: Q2JpXajUvwnRbYWj590jkp1TisEPvgMbAmt4b3SjjyI=
----------------------EOF-----------------------
 
Then after doing the clean boot and trying to install the update, it failed again with the same error code 80070490.
 
OK, let's see if there is a different reason this time. Please zip up and attach your entire C:\Windows\Logs\CBS folder. It may be too big to attach so you may have to upload to SendSpace and just provide the link here.
 
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