[SOLVED] Windows Update: 3 failing - error code 80070490

casewolf

Contributor
Joined
Jan 1, 2016
Posts
5
Hello all,


happy new year!


I stumbled across this great forum during my research in order to solve some problems with my small server that is living in my home office (Windows 7 64bit, Intel i7-2600k, SSD HDD + 2TB RAID 1)


During the last year I got several bluescreens and accumulated some updates, that wouldn't install. Now, during holidays, I got some time to investigate the issues. After having a deeper look at the machine, I decided to try to rescue what is left instead of performing a repair-installation.


This is, what I did so far:
- BIOS update
- Driver updates
- sfc /scannow -> found errors (I solved them by replacing the broken files) -> now all good regarding the protocol/log
- surt -> found errors -> solved most by replacing missing/corrupt manifest-files,
- SFCFix -> found the same errors left, couldn't repair them (2 registry problems with 2 package files, see below)


So now most of the problems are gone and the computer appears to be rock-solid.


But I still got issues with some updates that won't install (2 at first, now 3) - I would like that last bit also to be solved, for peace of mind...


After identifying the 2 failing updates:
KB2868626
KB2913602


See below:
Code:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-12-31 14:10


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages
(f)    CBS Registry Error    0x80070103    Package_112_for_KB2868626~31bf3856ad364e35~amd64~~6.1.1.2        failed to get owner for package.
(f)    CBS Registry Error    0x80070002    Package_3_for_KB2913602~31bf3856ad364e35~amd64~~6.1.1.0        failed to get CurrentState


Checking Component Store


Summary:
Seconds executed: 232
 Found 2 errors
  CBS Registry Error Total count: 2

I thought it would be a good idea to follow this article and try Method 1 and 2:
http://answers.microsoft.com/en-us/...rrors-in/5d510a6d-7fea-40a7-ad0a-c3d3a7d41434


After uninstalling both updates mentioned (Method 1 -Fixit- did not help), that led to the following result:
Code:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-12-31 18:01


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages
(f)    CBS Registry Error    0x80070002    Package_3_for_KB2913602~31bf3856ad364e35~amd64~~6.1.1.0        failed to get CurrentState


Checking Component Store


Summary:
Seconds executed: 217
 Found 1 errors
  CBS Registry Error Total count: 1

After that, I tried to manually re-install the updates, but to no avail. It fails with the message: "These updates are not designed for this system" (roughly translated from German). Strange. So my idea was not that good, me thinks now.


In the meantime, SURT kick-started an update list of over 40 updates that mostly installed trouble-free, excluding 3.


So now, I got 3 updates failing, the previous 2 won't show up (strangely...) in the list (neither in installed updates, nor under the currently needed ones):


KB2970228 (error code 80070490)
KB3087039 (error code 80070490)
KB3109094 (error code 80070490)


What could I do next? Thanks for any help, I appreciate any efforts!
 

Attachments

Hi casewolf :)

Do you still need assistance with this issue?
 
Hi casewolf :)

Do you still need assistance with this issue?

Hi Aura!

Yes please, I am still in need of assistance - much appreciated. I didn't want to mess around any further without professional help...

Thanks!
 
Alright :) Let's take care of the Registry error in CheckSUR first. Follow the instructions below please.

myjIXnC.png
SFCFix - Fix Time

WARNING! The following fix is specific to the user's system in this thread. No one else should follow the instructions below to apply that fix, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly.

Follow the instructions below to download and execute a SFCFix fix, and provide the log.
  • Download SFCFix and move the executable on your Desktop;
  • Download the attached SFCFixScript.txt and move the file to your Desktop;
    Note: Make sure that the file is named SFCFixScript.txt, do not rename it.
  • Save any work you have open, and close every programs;
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it;
    1p8eDnI.gif
  • SFCFix will launch, let it complete;
  • Once done, a file will appear on your Desktop, called SFCFix.txt;
  • Open the file, then copy and paste its content in your next reply;
SFCFixScript.txt
 
Hi Aura,

this is the result - looks good to me - should I try to re-run SURT now or SFCFix?

Cheers,
c.

Code:
SFCFix version 2.4.5.0 by niemiro.Start time: 2016-01-04 22:21:15.812
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\Daniel\Desktop\SFCFixScript.txt [0]








RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_3_for_KB2913602~31bf3856ad364e35~amd64~~6.1.1.0.


WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_3_for_KB2913602~31bf3856ad364e35~amd64~~6.1.1.0.


Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_3_for_KB2913602~31bf3856ad364e35~amd64~~6.1.1.0.


Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_3_for_KB2913602~31bf3856ad364e35~amd64~~6.1.1.0.
RegistryScript:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2016-01-04 22:21:15.879
Script hash: tsU7QJOUB8xUj0gKJOOaoHx8ITlcWCgo3wEw2nLEFmI=
----------------------EOF-----------------------
 
Re-run SURT first. Once it returns a clear log, we'll proceed with a SFC scan and grab the CBS.log :)
 
The CBS.log is managed by a lot of Windows services, like SFC, DISM, Windows Update, etc. so depending on the system, the CBS.log can grow big or can stay at a relatively small size. It's really dynamic, which means that it can change every minute, hour, day, etc. At a certain size, it'll be automatically compressed and archived by Windows, and a new one will be created :) The good news is that your CBS.log doesn't show any sign of corrupt files after running SFC, so we can move on. We'll start by renaming your CBS.log, so it won't be that big when you'll upload it next time.

88fYBWt.png
Rename CBS.log file
Follow the instructions below to rename your CBS.log file.
  • On Windows Vista & 7, click on the Windows Start Menu, then enter cmd in the search box, right-click on the cmd icon and select
    Spcusrh.png
    Run as Administrator
  • On Windows 8, drag your cursor in the bottom-left corner, and right-click on the metro menu preview, then select Command Prompt (Admin);
  • On Windows 8.1, right click on the Windows logo in the bottom-left corner and select Command Prompt (Admin);
  • Enter the command below and press on Enter;
    Code:
    ren %windir%\Logs\CBS\CBS.log CBS_old.log
    Note: If it says that the file is actually in use, restart your computer and try the command again.
  • Once it's done, let me know;

Once this is done, try to install your Windows Updates. If they fail, upload the two files below for me to review please.

C:\Windows\WindowsUpdate.log
C:\Windows\Logs\CBS\CBS.log
 
No problem casewolf, you're welcome :) And thank you for your donation, it's really appreciated :)
 

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

Back
Top