[SOLVED] Error 0x80004005 updating KB4499164 and KB4481252

PascalAH · May 31, 2019

Hi guys,

First time posting for help on this sort of forum, but am at my wits end. Reinstalling or replacing this server is not an option at this point.

We've got a server (running 2008 R2 Standard) that's failing to update these two updates (KB4481252 and KB4499164 - the latter of which is a big concern considering recent news) and I've tried just about everything I can possible think of/find in order to resolve. Multiple updates including KB890830, KB4490628 and KB4499406 installed successfully on the same patch release day these started failing to install, 22/05. (Gives you an idea how long I've been investigating this!)

General and more specific error-code related steps I've already taken:

*Triggered our inhouse Windows Update Fix script (contains compiled bits of 'reset windows update components', clear 'WU AutoUpdate registry key' fixes etc. that we've used for years to great success)
*Done a manual reset of Windows Update Components as per Microsoft's guides.
*Cleared SoftwareDistribution.
*Attempted updating through our global patch management software, Centrastage/Datto Endpoint Management.
*Attempted installing manually by downloading and running the two updates from the Windows Update catalog.
*Attempted installing via WUSA and DISM (as well as trying to 'uninstall' the non-installed KB in case there were remnants)
*Ran Windows Update Troubleshooter.
*Ran WURT/CheckSur and found no errors.
*Ran SFC - no integrity violations were found.
*Ran a dism /checkhealth - no issues found.
*Investigated reports that error can stem from disabled peerdissvc, but Branchcache role is not installed on this server and the service is not present.
*Disabled the anti-virus, Sophos, from running on the machine temporarily.
*Tried with disabled Windows Firewall.
*Tried allowing both ports 443 and 80 inbound and outbound in Windows Firewall as a troubleshooting step.
*As per Microsoft articles, added 'http://*.microsoft.com' to trusted sites and loosened ActiveX settings for Trusted Sites as per their recommendations.
*Tried clearing AppCompFlags\Layers key as a solution that I found as a fix for similar issues relating to the same error code.
*Ran SFCFix.exe - reports no corruptions were detected. (see attached)
*Due to differing KB numbers it's difficult to tell exactly what the last security roll-up is, but I saw Feb's was definitely installed without a shadow of a doubt, so checked the KB for March's rollup (which wasn't showing installed) and tried to install. Same error code.
*Dug through the WindowsUpdate.log and followed down the path of numerous error codes I found in there including 0x80070490, 8007007e, 0x80070002 and 80070663.

SFCFix.txt attached and all files within CBS folder downloadable from https://eu.soonr.com/2/filelink/bsyna-bygkh5o-to6xg2el

SFC and DISM have both been run a couple of times this week, but let me know if you need a more current set.

If anyone's able to assist I'd be eternally grateful, as I'm absolutely stumped.

TIA!
Pascal

PascalAH · Jun 6, 2019

Hi guys,

Sorry for BUMPing, but any chance of some assistance on this? Am very nervous not having that rollup installed, especially with it being a TS.

TIA!

Pascal

PascalAH · Jun 24, 2019

Guessing this has been lost in the noise; I'm still really needing some assistance on this one if at all possible, and would greatly appreciate it.

Fingers crossed!

Sysnative Windows Update · Jun 24, 2019

Hello and welcome!

Due to the precise nature of your corruption, you will receive help from a user named writhziden. He's one of our senior trainees here who's in his final phase of his studies and needs to gain some real world experience in specific areas of Windows Update. This means that he'll be assisting you, but that I will first need to double check and approve his fixes before he posts them to you. If anything this is a good thing for you because it means that you've got at least two of us watching over your thread, but it will unfortunately add a slight delay between each reply. I hope that you understand and can accept the need for us to train up new members in this way in order to carry on doing what we do here, however, if for any reason you object to this setup, I will happily take on your thread myself.

Thank you very much for your understanding. We'll be with you very shortly.

PascalAH · Jun 25, 2019

softwaremaniac said:
Hello and welcome!

Due to the precise nature of your corruption, you will receive help from a user named writhziden. He's one of our senior trainees here who's in his final phase of his studies and needs to gain some real world experience in specific areas of Windows Update. This means that he'll be assisting you, but that I will first need to double check and approve his fixes before he posts them to you. If anything this is a good thing for you because it means that you've got at least two of us watching over your thread, but it will unfortunately add a slight delay between each reply. I hope that you understand and can accept the need for us to train up new members in this way in order to carry on doing what we do here, however, if for any reason you object to this setup, I will happily take on your thread myself.

Thank you very much for your understanding. We'll be with you very shortly.

Thanks softwaremaniac! Fine by me; I totally understand the necessity to train up on the art of Windows-Update-Fu and am happy to support that... Just ideally looking to get this one nailed on the head as soon as. A severe RDP vulnerability being unpatched on an internet facing production RDP server makes me very nervous.

Any further information needed, just shout and I'll gather as soon as I can.

Once again, thanks for any assistance on this.

writhziden · Jun 25, 2019

Hi, and welcome to Sysnative Forums. We have analyzed your logs and found the following entries in your CBS.log related to the error you reported:

Code:

2019-05-31 01:30:54, Error CBS Failed. Attempted to uninstall a version of a non-driver component that is not installed, version: 0X600011db15dd7, component: amd64_microsoft-windows-m..do-backcompat-tlb60_31bf3856ad364e35_6.1.7601.24023_none_4b80caf320b863b8, owner: Package_1514_for_KB4486563~31bf3856ad364e35~amd64~~6.1.1.4.4486563-4401_neutral_LDR [HRESULT = 0x80004005 - E_FAIL]
2019-05-31 01:30:54, Info CBS Failed to mergecomponent [HRESULT = 0x80004005 - E_FAIL]
2019-05-31 01:30:54, Info CBS ComponentAnalyzerUninstallDeployment: Failed on update: 4486563-4401_neutral_LDR [HRESULT = 0x80004005 - E_FAIL]
2019-05-31 01:30:54, Info CBS Failed to execute item[0] in Package: Package_1514_for_KB4486563~31bf3856ad364e35~amd64~~6.1.1.4, Update: 4486563-4401_neutral_LDR [HRESULT = 0x80004005 - E_FAIL]
2019-05-31 01:30:54, Info CBS Failed to execute execution update. [HRESULT = 0x80004005 - E_FAIL]
2019-05-31 01:30:54, Info CBS Failed to execute execution package: Package_1514_for_KB4486563~31bf3856ad364e35~amd64~~6.1.1.4 [HRESULT = 0x80004005 - E_FAIL]
2019-05-31 01:30:54, Info CBS Failed to prepare execution [HRESULT = 0x80004005 - E_FAIL]
2019-05-31 01:30:54, Info CSI 000016dc@2019/5/31:00:30:54.169 CSI Transaction @0xaebd0c0 destroyed
2019-05-31 01:30:54, Info CBS Perf: InstallUninstallChain complete.
2019-05-31 01:30:54, Info CBS Failed to execute execution chain. [HRESULT = 0x80004005 - E_FAIL]
2019-05-31 01:30:54, Error CBS Failed to process single phase execution. [HRESULT = 0x80004005 - E_FAIL]

The error requires that we remove the problematic components of KB4486563. To do so, I will need a registry search output from you:

FRST Registry Search

Click your Start button and type in cmd. Press Enter.
Copy paste the following into the Command Prompt:

reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
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.
Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
Copy and paste KB4486563 into the Search box and click the Search Registry button.
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.

PascalAH · Jun 26, 2019

Hi writhziden,

Thanks - done as requested. Please see attached

writhziden · Jun 26, 2019

Below is the fix for update KB4486563.

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

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.
Download the attached fixlist.txt 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).
Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
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.
When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
Try to install updates again, and if any fail, please provide your CBS log Text Document file:

Export/Upload your CBS log file
Read More:
1. On Windows 8 and Windows 10, press the Windows key, type This PC, and press Enter.
  On Windows Vista and Windows 7, click the Start button then click Computer.
2. Double-click on the C: drive, under the Hard Disk Drives category, and then scroll down to, and double click on the Windows folder.
3. Find and double click on the Logs folder.
4. Find and double click on the CBS folder.
5. Right-click on the CBS Text Document file, and select Copy.
6. Go back to your Desktop, right-click on it, and select Paste. You should now see a copy of the CBS Text Document file appear on your Desktop called CBS.
7. Right-click on this new Text Document file, and navigate through Send to, and select Compressed (zipped) folder.
8. A new file, also called CBS (CBS.zip), but this time with a different icon, will be created on your desktop.
9. Attach the CBS.zip file.
  Note: If your CBS.zip is larger than about 7MB then you will need to upload your file to a hosting service and provide a link instead. See “What to do if your CBS log file is too large to upload” below.
[*][*][*][*]
What to do if your CBS log file is too large to upload

Read More:

In some instances you will be unable to upload your CBS log file to our forum because it is too large.
To work around this problem you need to use a file sharing service to upload your attachment and then provide the link that is generated by the hosting service in your post.
Several file sharing options are listed below (they are clickable links), however you are not limited to these:

Microsoft OneDrive
Google Drive
Dropbox
ExpireBox
SendSpace
WeTransfer

PascalAH · Jun 26, 2019

Hi writhziden,

This won't invoke a reboot automatically, will it? As this is a production server I'm happy to reboot it overnight (if needed), but can't afford it rebooting on its own upon conclusion of the process.

writhziden · Jun 26, 2019

As a precaution, I would recommend waiting to run the fix until it is safe for the server to restart.

PascalAH · Jun 26, 2019

No problem - I'll run it tonight and advise results. Thanks for the prompt response!

PascalAH · Jun 26, 2019

Fantastic news! It worked! (At least partially)

The May roll-up installed successfully, so I decided to go for it and run the outstanding patches against the server and it installed KB2992611 as well as the June roll-up successfully too.

Unfortunately the Silverlight update as well as the standalone installer are still failing with 0x80240022 as before.

Attached is the fixlog.txt and below is the cbs logs:

https://eu.soonr.com/2/filelink/bsyna-byyk4zq-pxeabxw6

Don't know how you do it, but thanks - big sigh of relief that the roll-ups are installed successfully; not quite as perturbed about Silverlight.

writhziden · Jun 26, 2019

I am glad we were able to resolve the most pressing update error. For your Silverlight update issue, have you tried following the guide to clean a corrupted Silverlight installation?

How to clean a corrupted Silverlight installation and then reinstall Silverlight

If you have not followed that guide before, please do so now and let us know the results. Also, please provide your CBS log file if the update/install fails after cleaning the Silverlight installation.

PascalAH · Jun 27, 2019

Nailed it on the head, once again.

Thank you so much! Server is now reporting 0 patches outstanding and seems happy; you guys do work miracles. Silverlight was failing to uninstall, but after doing the commands to clean up Silverlight installation locations, it reinstalled without a hitch.

Out of curiosity and for my own understanding, was it purely reg key deletes by the FRST script that did the trick?

After more digging at best I may have found the Feb KB it was complaining about and tried to reinstall it, but haven't the faintest idea how you determined the keys that needed clearing.

Once again, thanks a million for the hard work and I think we can more than consider this thread closed and resolved.

Cheers,
Pascal

writhziden · Jun 27, 2019

Much of the credit goes to the Windows Update Instructors who have the experience and willingness to pass that experience along to us trainees. This was my first thread involving the 0x80004005 error. softwaremaniac provided the direction for dealing with 0x80004005 errors as well as a hint to use FRST to remove the registry values and keys for the update that failed to uninstall. The registry search for KB4486563 provided me with which values and keys needed removal, and then I used an app I built that converts those values and keys to a fixlist script for removing them.

softwaremaniac also provided the Silverlight link to me in my training session. I am very thankful for the knowledge shared so I may help users with similar errors in the future.

Search

Search

[SOLVED] Error 0x80004005 updating KB4499164 and KB4481252

PascalAH

Member

Attachments

PascalAH

Member

PascalAH

Member

Sysnative Windows Update

Inactive

PascalAH

Member

writhziden

Administrator, .NET/UWP Developer

PascalAH

Member

Attachments

writhziden

Administrator, .NET/UWP Developer

Attachments

PascalAH

Member

writhziden

Administrator, .NET/UWP Developer

PascalAH

Member

PascalAH

Member

Attachments

writhziden

Administrator, .NET/UWP Developer

PascalAH

Member

writhziden

Administrator, .NET/UWP Developer