[SOLVED] Unable to install KB3080079 with windows update error code 80070490

deletedmember64575

Active member
Joined
Jul 18, 2018
Posts
32
Admin,

I have a windows 2008 R2 SP1 server that is constantly failing in installing KB3080079. Every time, the resulting error code is 80070490. I've tried resetting windows update components, sfc /scannow, dism /online /cleanup-image /restorehealth, etc. and none have helped me in resolving the issue. I tried installing the KB manually, via BigFix, Microsoft update and through our WSUS and they all fail with the same error code. However, I was able to install other security updates for this month without any issues. I've read a few forums on here that were able to get the issue resolved after a while, so decided to join and see if the site can help me. Thanks.
 
Logs from Step #4

SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-07-31 12:50:17.602
Microsoft Windows Server 2008 R2 Service Pack 1 - amd64
Not using a script file.

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

Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2018-07-31 12:51:11.515
----------------------EOF-----------------------

CBS Folder
 
That worked!

Remove Update Manually
1. Click on the Start 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:4015549

4. Let me know if it says it was successful or if there are any errors.
 
FRST Registry Search
1. Click your Start button and choose Control Panel.
2. In the upper right corner ensure the View by: is set to Category.
3. Select the Programs group.
4. Click the Turn Windows features on or off link. This will bring up the Windows Features dialog. Wait until this dialog populates with information.
Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps.
5. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
6. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
7. Copy and paste
KB4015549 into the Search box and click the Search Registry button.
8. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.
9. You may close any remaining open windows now.
 
You are correct. My apologies!

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
6. Try updates and if any fail, attach CBS.log.
 

Attachments

I've attached the fixlog.txt file. View attachment 37490

The update got installed but it did delete all the update history. We have another server that has the same issue. This server is a clone of another server which is why both are affected. Can i apply the same fix to the other one?

And, may I ask what was the issue and fix?
 
No, you may not apply it, because the issue may be different. I cannot suggest a fix without seeing the logs.

The issue were the remnants of an older update which had to be removed manually in order for this to work!

Please start a separate thread for that Server machine! Glad to have helped!
 

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

Back
Top