[SOLVED] Kb3070102 won't install - 80070490 error

E

ElCap

Member
Joined
Jul 22, 2015
Posts
10
My PC has been trying to load KB3070102 for days now but resolutely will not install it - it downloads and fails with an 80070490 error. I have tried the Fixit tool, tried the Readiness tool and done the sfc /scannow thing (1 error).

From a read around it seems it ma be a manifest/packages relate issue – the CBS seemed to come up with three issues.
And that’s where I got to and I am stuck!
Your assistance is most welcome!
 
Hi ElCap :)

My name is Aura and I'll be assisting you with your issue. Is it possible for you to archive the whole C:\Windows\Logs\CBS folder and upload it on Dropbox, Google Drive or OneDrive so I can download it?
 
Dropbox link for CBS.log: https://www.dropbox.com/s/ghu4n54ibt2j72h/CBS ElCap 24 Jul 15.txt?dl=0

You only uploaded the CBS.log which doesn't contain any traces of the SFC scan anymore, since the log is volatile. Follow the instructions below please.

EndqYRa.png
System File Checker (SFC)
Follow the instructions below to run a SFC scan on your system and to provide the CBS log in your next reply;
  • 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: 
    sfc /scannow
    Note: There's a space between "sfc" and "/scannow";
  • Once the scan is complete, enter the command below and press on Enter
    Code: 
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  • A file called cbs.txt will have appeared on your Desktop. Upload the file on Dropbox, Google Drive or OneDrive and post the download URL for it here;
Note: Please note that the CBS.log is volatile, which means that if you don't upload it after the SFC scan is completed, it won't contains the information from the scan anymore. So archive it and upload it as soon as you can.
 
Thes files in your CBS.log (utc.app.json and telemetry.ASM-WindowsDefault.json) are falsely reported as corrupt by SFC. Microsoft is aware of this situation and they said that this issue will be fixed in a later update. These files aren't corrupt and they won't affect anything on your system. You can leave it be without any consequences. For more information, see the Microsoft Article below.

https://support.microsoft.com/en-us/kb/3022345

This update contains the following files that are occasionally updated by the Diagnostic Tracking Service:

telemetry.ASM-WindowsDefault.json
utc.app.json

The two files are marked as static files in the update. When an advanced user runs the System File Checker Tool (sfc.exe), the files are unintentionally flagged as corrupted. There is no impact or actual corruption on a device running this update, and a later service update will resolve this issue.
Click to expand...

I doubt these are responsible for your issues. We'll run SURT and grab the CheckSUR.log to see if there's anything interesting in it. If not, we can try to fix them and see if it'll allow the update to go throught, but I doubt.

IGJdB0T.png
System Update Readiness Tool (SURT) - Scan
Follow the instructions below to run a scan with the System Update Readiness Tool (SURT) and provide a log;
  • Download the right version of SURT for your system;
    • Your version of Windows is:
  • Once downloaded, execute the installer, and go throught the installation (this process can take around 15-20 minutes);
  • On completion, a log will be created in C:\Windows\Logs\CBS\CheckSUR.log;
  • Attach this log in your next reply;
Alternatively, if these instructions are unclear for you, you can follow the tutorial below.

System Update Readiness Tool (SURT)
 
Alright so there's indeed stuff that needs to be fixed. Follow the instructions below please.

Retrieve Components Hive

  • Please download the Freeware RegBak from here: Acelogix Software - Download products
     You will find it at the bottom of the page that the link brings you to.
  • Go ahead and install this program and accept all the defaults. After the last install screen the program should open.
  • Click the New Backup button. Accept the defaults and simply click Start.
  • When it says Finished successfully, click the Close button.
  • This will bring you back to the main screen of the program. You will see one entry in this list with the date that you did it. Right-click on this line-item and select Explore Backup...
  • This will bring you into the folder where the backup was made. You should see a Users folder and a Windows folder along with a couple other files. Double-click on the Windows folder to open it. Then open the System32 folder and then config folder. You should see around 6 files in here, one of which is named COMPONENTS.
  • Copy the COMPONENTS file to your Desktop. If the COMPONENTS file does not exist, please fetch it instead from C:\Windows\System32\config\COMPONENTS.
  • Now right click on the COMPONENTS file that is on your desktop and select Send to > Compressed (zipped) folder.
  • Then please upload the zip file (COMPONENTS.zip) to your favourite file sharing website (it will be too big to upload here). Examples of services to upload to are Dropbox or One Drive or SendSpace and then just provide the link in your reply.
  • You can close any open windows you have as well as the RegBack program now.
 
I'll also need the CBS Hive. Follow the instructions below please.

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.
 
Sorry for the delay. 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;
  • 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

IGJdB0T.png
System Update Readiness Tool (SURT) - Scan
Follow the instructions below to run a scan with the System Update Readiness Tool (SURT) and provide a log;
  • Download the right version of SURT for your system;
    • Your version of Windows is:
  • Once downloaded, execute the installer, and go throught the installation (this process can take around 15-20 minutes);
  • On completion, a log will be created in C:\Windows\Logs\CBS\CheckSUR.log;
  • Attach this log in your next reply;
Alternatively, if these instructions are unclear for you, you can follow the tutorial below.

System Update Readiness Tool (SURT)

Therefore your next reply should contain:
  • Copy/pasted SFCFix log;
  • Copy/pasted CheckSUR log (SURT output);
 
SFC file:

SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-07-26 11:08:30.608
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\Nick\Desktop\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-FailoverCluster-Core-WOW64-Package~31bf3856ad364e35~amd64~~0.0.0.0.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-ServerCore-WOW64-Package~31bf3856ad364e35~amd64~~0.0.0.0.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_8_for_KB2698365~31bf3856ad364e35~amd64~~6.1.1.2\Owners.

WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-FailoverCluster-Core-WOW64-Package~31bf3856ad364e35~amd64~~0.0.0.0.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-FailoverCluster-Core-WOW64-Package~31bf3856ad364e35~amd64~~0.0.0.0.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-ServerCore-WOW64-Package~31bf3856ad364e35~amd64~~0.0.0.0.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-ServerCore-WOW64-Package~31bf3856ad364e35~amd64~~0.0.0.0.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c].
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_8_for_KB2698365~31bf3856ad364e35~amd64~~6.1.1.2\Owners.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_8_for_KB2698365~31bf3856ad364e35~amd64~~6.1.1.2\Owners.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-FailoverCluster-Core-WOW64-Package~31bf3856ad364e35~amd64~~0.0.0.0.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-ServerCore-WOW64-Package~31bf3856ad364e35~amd64~~0.0.0.0.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c].
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\wow64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_4340b53dcf6f3927.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_8_for_KB2698365~31bf3856ad364e35~amd64~~6.1.1.2\Owners.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 8 datablocks.
Finish time: 2015-07-26 11:08:30.824
Script hash: 31jXzEuVa4fyL+rPM8gGNCWb+tTYZnSANhMUfHdjmY0=
----------------------EOF-----------------------






CheckSUR file:


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-07-26 11:14

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist
(f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c Package_2_for_KB3057839~31bf3856ad364e35~amd64~~6.1.1.3 Package registry presence failed, possibly an orphaned package on package watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 432
Found 1 errors
CBS Watchlist Component Missing Total count: 1
Customer Experience report successfully uploaded. Thank you for participating. For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.



Thanks.
 
I messed up my script above by one character, my apologies. 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;
  • 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

IGJdB0T.png
System Update Readiness Tool (SURT) - Scan
Follow the instructions below to run a scan with the System Update Readiness Tool (SURT) and provide a log;
  • Download the right version of SURT for your system;
    • Your version of Windows is:
  • Once downloaded, execute the installer, and go throught the installation (this process can take around 15-20 minutes);
  • On completion, a log will be created in C:\Windows\Logs\CBS\CheckSUR.log;
  • Attach this log in your next reply;
Alternatively, if these instructions are unclear for you, you can follow the tutorial below.

System Update Readiness Tool (SURT)

Therefore your next reply should contain:
  • Copy/pasted SFCFix log;
  • Copy/pasted CheckSUR log (SURT output);
 
SFCfix log:

SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-07-26 16:29:26.301
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\Nick\Desktop\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c.

WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-win32k_31bf3856ad364e35_0.0.0.0_none_38ec0aeb9b0e772c.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 8 datablocks.
Finish time: 2015-07-26 16:29:26.378
Script hash: 6492Ts0zLxWZmoRaSzx0wCnlaIjQ7itXKEB/bXbpPf4=
----------------------EOF-----------------------



CheckSUR log:


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-07-26 16:33

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 208
No errors detected
Customer Experience report successfully uploaded. Thank you for participating. For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.


Thanks.



 
Alright, now that SURT comeback clean, time to run SFC again.

EndqYRa.png
System File Checker (SFC)
Follow the instructions below to run a SFC scan on your system and to provide the CBS log in your next reply;
  • 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: 
    sfc /scannow
    Note: There's a space between "sfc" and "/scannow";
  • Once the scan is complete, enter the command below and press on Enter
    Code: 
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  • A file called cbs.txt will have appeared on your Desktop. Upload the file on Dropbox, Google Drive or OneDrive and post the download URL for it here;
Note: Please note that the CBS.log is volatile, which means that if you don't upload it after the SFC scan is completed, it won't contains the information from the scan anymore. So archive it and upload it as soon as you can.
 
The only errors left are from the KB3068708, which is normal. They are false positives. Can you try to reinstall the update again now?
 
I have just rebooted after a successful install of this update.

Can I express my gratitude for your patience, professionalism and help - all of which are genuinely appreciated. Thank you!
 
The simple fact that you are satisfied with my assistance is more than enough for me :) I'm glad to have been of help.
 
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