Windows update fails error 80070490

[tom982]

Hi digdug,

That's great Thanks for the log, no problem there. Let's try fixing the registry key that you couldn't find with a .reg file:

Backing Up Your Registry

1. The steps that I am about to suggest involve modifying the registry. Modifying the registry can be dangerous so we will make a backup of the registry first.
   Modification of the registry can be EXTREMELY dangerous if you do not know exactly what you are doing so follow the steps that are listed below EXACTLY. if you cannot perform some of these steps or if you have ANY questions please ask BEFORE proceeding.
   
2. Download ERUNT
   (ERUNT (Emergency Recovery Utility NT) is a free program that allows you to keep a complete backup of your registry and restore it when needed.)
3. Install ERUNT by following the prompts
   (use the default install settings but say no to the portion that asks you to add ERUNT to the start-up folder, if you like you can enable this option later)
4. Start ERUNT
   (either by double clicking on the desktop icon or choosing to start the program at the end of the setup)
5. Choose a location for the backup
   (the default location is C:\WINDOWS\ERDNT which is acceptable).
6. Make sure that at least the first two check boxes are ticked
7. Press OK
8. Press YES to create the folder.

Registry Modifications

1. Go to Start > Run to bring up the run box
2. In the box, type notepad.exe and press OK to open Notepad
3. Copy (Ctrl+C) all of the text in the following box and paste (Ctrl+V) it into Notepad
   
   

   Windows Registry Editor Version 5.00
   
   [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_0.0.0.0_none_2ffc2dd73a76a803]
   "Package_4_for_KB951618~31bf3856ad364e35~x86~~6.0.1.1"=-

4. Go to File > Save As... and save it to your Desktop named Fix.reg. Make sure you change the Save as type to All Files (*.*)
5. Locate Fix.reg on your Desktop and double-click on it to merge it with your registry
6. Answer Yes when prompted about merging with the registry

Then try updating again and copy and paste the contents of your CheckSUR log again please

C:\Windows\Logs\CBS\CheckSUR.persist.log

Tom

 

[digdug304]

Hey tom,

Did as you asked and after the .reg file was merged i was able to install a few more updates.

Also like you asked i've attached the CheckSUR.log file to the post like normal

Thanks

 

[tom982]

Hi Digdug,

That's great Sounds like we're making progress. I'm not all together sure what makes Windows write a new log to that CheckSUR log, but it doesn't appear that a new one has been made since 11/06. I know it definitely writes a new log when the tool is run, but I expected it to make a new log when updates failed. Back to the drawing board I'll do a bit more research on this, but until then, I think the only way is to use the same instructions as before:

Having Trouble Installing Windows Updates? Use the System Update Readiness Tool for Windows | Windows 7 Maintenance | Windows Tools, Help & Guides

Fingers crossed it doesn't freeze up again! Then attach the CheckSUR.persist.log again please

Tom

 

[digdug304]

hello tom,

To come back from the grave (sorry family emergency and just recently got done) have you found anything that might help my predicament? also i have tried to reinstall
the System update readiness tool multiple times to no avail.

I can redo steps since ive been away for awhile to try again if it will help.

Thanks in advance and sorry again for disappearing

 

[tom982]

hello tom,

To come back from the grave (sorry family emergency and just recently got done) have you found anything that might help my predicament? also i have tried to reinstall
the System update readiness tool multiple times to no avail.

I can redo steps since ive been away for awhile to try again if it will help.

Thanks in advance and sorry again for disappearing

Hi digdug,

It's no problem whatsoever. I completely understand people have lives outside of here (including us helpers!) so I'm more than happy to wait for someone to return. Glad to hear you've sorted your problems though. It's really good timing actually, I've just returned (about 2 hours ago) from holiday so I wouldn't have been able to help you even if you were here

I'll have to read through this thread again, but I should be able to reply by tomorrow at the latest.

Tom

 

[digdug304]

Hey Tom,
Thanks as usual and take your time with this im in no rush like before so relax after the vacation :D

 

[tom982]

Hey digdug,

Right, I've had a quick look through this thread just as a refresher to make sure we don't try anything that I've already suggested.

Could you attach your CheckSUR.persist.log file again please? It should contain the latest log with all of the outstanding problems

C:\Windows\Logs\CBS\CheckSUR.persist.log

Tom

 

[digdug304]

Hey Tom,

Here is what you asked I believe its the same as before since I havent done anything since the last suggestion.

Thanks again for working with me on this

 

[tom982]

Hello digdug,

I just wanted to make sure we had the latest copy of the log. I dread to think of the problems I would cause by fixing non existent problems!

Right, back on to the complicated stuff. Could you do the following for me please:

Command Prompt

1. Open your start menu 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 commands into it, press enter after each
   
   regedit /e tom982componentsexport.txt "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_0.0.0.0_none_2ffc2dd73a76a803"
   
   start notepad.exe tom982componentsexport.txt
   
   
4. This will create a text file called tom982.txt in the root folder of your main drive (e.g. C:\tom982.txt). Please copy and paste the contents of this into your next post.

Tom

 

[digdug304]

Hey Tom,

As requested here is what you asked for before also going to attach it as .txt case this is hard to read....

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_0.0.0.0_none_2ffc2dd73a76a803]
"Package_30_for_KB936330~31bf3856ad364e35~x86~~6.0.1.18000.936330-187_neutral_GDR"="6.0.6001.18000@16"
"Package_4_for_KB951618~31bf3856ad364e35~x86~~6.0.1.1.951618-17_neutral_GDR"="6.0.6000.16700@2"
"Package_2_for_KB947562~31bf3856ad364e35~x86~~6.0.1.1.947562-13_neutral_LDR"="6.0.6001.22132@2"
"Package_2_for_KB947562~31bf3856ad364e35~x86~~6.0.1.1.947562-14_neutral_GDR"="6.0.6001.18032@2"
"Package_6_for_KB947562~31bf3856ad364e35~x86~~6.0.1.1.947562-43_neutral_LDR"="6.0.6000.20788@2"
"Package_6_for_KB947562~31bf3856ad364e35~x86~~6.0.1.1.947562-44_neutral_GDR"="6.0.6000.16651@2"
"Package_2_for_KB954366~31bf3856ad364e35~x86~~6.0.1.3.954366-13_neutral_LDR"="6.0.6001.22233@2"
"Package_2_for_KB954366~31bf3856ad364e35~x86~~6.0.1.3.954366-14_neutral_GDR"="6.0.6001.18112@2"
"Package_6_for_KB954366~31bf3856ad364e35~x86~~6.0.1.3.954366-47_neutral_LDR"="6.0.6000.20885@2"
"Package_6_for_KB954366~31bf3856ad364e35~x86~~6.0.1.3.954366-48_neutral_GDR"="6.0.6000.16721@2"
"Package_2_for_KB972036~31bf3856ad364e35~x86~~6.0.2.0.972036-13_neutral_LDR"="6.0.6001.22509@2"
"Package_2_for_KB972036~31bf3856ad364e35~x86~~6.0.2.0.972036-14_neutral_GDR"="6.0.6001.18320@2"
"Package_7_for_KB972036~31bf3856ad364e35~x86~~6.0.2.0.972036-47_neutral_LDR"="6.0.6002.22213@2"
"Package_7_for_KB972036~31bf3856ad364e35~x86~~6.0.2.0.972036-48_neutral_GDR"="6.0.6002.18101@2"
"Package_12_for_KB972036~31bf3856ad364e35~x86~~6.0.2.0.972036-83_neutral_LDR"="6.0.6000.21117@2"
"Package_12_for_KB972036~31bf3856ad364e35~x86~~6.0.2.0.972036-84_neutral_GDR"="6.0.6000.16917@2"
"Package_25_for_KB948465~31bf3856ad364e35~x86~~6.0.1.18005.948465-113_neutral_GDR"="6.0.6002.18005@16"
"Package_3_for_KB976264~31bf3856ad364e35~x86~~6.0.1.1.976264-13_neutral_LDR"="6.0.6002.22303@2"
"Package_3_for_KB976264~31bf3856ad364e35~x86~~6.0.1.1.976264-14_neutral_GDR"="6.0.6002.18179@2"

 

[tom982]

Need to pop out now, but I'll be back in a few hours. Just to save me finding it again, here's the problematic value:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_0.0.0.0_none_2ffc2dd73a76a803]
"Package_4_for_KB951618~31bf3856ad364e35~x86~~6.0.1.1.951618-17_neutral_GDR"="6.0.6000.16700@2"

Please don't touch this until I get back

Tom

 

[digdug304]

No worries don't think I'll use the computer in question for a bit till this is worked out

Thanks again for helping out like I'm always saying

 

[tom982]

Hi digdug,

Backing Up Your Registry

1. The steps that I am about to suggest involve modifying the registry. Modifying the registry can be dangerous so we will make a backup of the registry first.
   Modification of the registry can be EXTREMELY dangerous if you do not know exactly what you are doing so follow the steps that are listed below EXACTLY. if you cannot perform some of these steps or if you have ANY questions please ask BEFORE proceeding.
   
2. Download ERUNT
   (ERUNT (Emergency Recovery Utility NT) is a free program that allows you to keep a complete backup of your registry and restore it when needed.)
3. Install ERUNT by following the prompts
   (use the default install settings but say no to the portion that asks you to add ERUNT to the start-up folder, if you like you can enable this option later)
4. Start ERUNT
   (either by double clicking on the desktop icon or choosing to start the program at the end of the setup)
5. Choose a location for the backup
   (the default location is C:\WINDOWS\ERDNT which is acceptable).
6. Make sure that at least the first two check boxes are ticked
7. Press OK
8. Press YES to create the folder.

Registry Modifications

1. Go to Start > Run to bring up the run box
2. In the box, type notepad.exe and press OK to open Notepad
3. Copy (Ctrl+C) all of the text in the following box and paste (Ctrl+V) it into Notepad
   
   Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_0.0.0.0_none_2ffc2dd73a76a803] "Package_4_for_KB951618~31bf3856ad364e35~x86~~6.0.1.1.951618-17_neutral_GDR"=-
4. Go to File > Save As... and save it to your Desktop named Fix.reg. Make sure you change the Save as type to All Files (*.*)
5. Locate Fix.reg on your Desktop and double-click on it to merge it with your registry
6. Answer Yes when prompted about merging with the registry

Tom

 

[digdug304]

Alright Tom,

Did like you said backed up the regestry and modified it with the fix.reg

what would you like done now?

Digdug

 

[tom982]

That's great, thanks

Could you re run the SURT please? Then attach the log:

C:\Windows\Logs\CBS\CheckSUR.persist.log

Tom

 

[digdug304]

Hey Tom,

Just saying i re-downloaded the "System update readiness tool" the SURT that you meant i hope and am trying to install it again but its hanging on install i'll leave it alone for an hour or so and if nothing then i'll say so.

digdug

 

[digdug304]

Hey Tom,

Once again here you are it actually installed this time though after about 40 mins

digdug

 

[tom982]

Hi digdug,

It's really odd how it keeps re-appearing. Let's try a different approach then.

Try uninstalling the update: KB951618. You can search for it on the list:

Remove an update

Then run the SURT again please, and attach the log as usual. You don't have to download it each time you want to use it, you can just use the saved file as many times as you like

Tom

 

[digdug304]

Hey Tom,

My computer is saying I don't have any updates installed on this computer which I'm

pretty sure there is....

Attached a picture of what I am talking about


digdug

 

[digdug304]

Just bumping cause not sure if any news on what may have happened...