Windows update failed - errorcode 80004005 - KB4534310 - Server 2008 R2 SP1 x64

L

Lars-Simonsen

Member
Joined
Feb 28, 2020
Posts
5
Dear Forum!



For the past weeks I’ve been struggling with the KB4534310 update on a single 2008 R2 machine.

Running sfc /scannow did not reveal any erros



I then came across the forum article https://www.sysnative.com/forums/threads/windows-update-failed-errorcode-80070002-kb4534310-server-2008-r2-sp1-x64.30472/ an tried pretty much the same steps (which in general means following the steps in the https://www.sysnative.com/forums/threads/kb4338818-failed-with-code-8024200d.25854/post-227429 post...



When I run the DISM.exe /Online /Add-Package /PackagePath:C:\temp\windows6.1-kb4534310-x64.cab command I get the error 0x80004005



C:\Users\lsiadmin\Desktop>DISM.exe /Online /Add-Package /PackagePath:C:\temp\win

dows6.1-kb4534310-x64.cab

Deployment Image Servicing and Management tool

Version: 6.1.7601.24499

Image Version: 6.1.7601.24499

Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~

~7601.24544.1.9

[===========================86.3%================== ]

An error occurred - Package_for_RollupFix Error: 0x80004005

Error: 0x80004005

DISM failed. No operation was performed.

For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log



When I look at the DISM log fil I do see several errors

Error DISM DISM Package Manager: PID=8140 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80004005)

I’ve attached the DISM log as well as the CBS log, I would be thankful for any advices you may have !
 

Attachments

Hello there Lars!

I don't see anything obvious in the CBS or DISM logs.
Let's start with the System Update Readiness Tool.

System Update Readiness Tool (SURT)

Download and run the System Update Readiness Tool for your version of Windows here: System Update Readiness Tool

NOTE: If you aren't sure if your Windows installation is 32-bit or 64-bit, check here: How to determine whether a computer is running a 32-bit version or 64-bit version of the Windows operating system

This tool will take some time to complete - when it has finished, zip and attach C:\Windows\Logs\CBS\CheckSUR.log with your reply.
 
Hi zcomputerwiz, thanks for your fast response !

As suggested I did run the System Update Readiness Tool, and it took quite I while to complete. (and displayed "installed successfully" at the end) however it ended up just creating a 1 KB CheckSUR.log file

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2020-02-28 20:48

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 2033
No errors detected
(w) Unable to get system disk properties 0x0000045D IOCTL_STORAGE_QUERY_PROPERTY Disk Cache


Any further suggestions are highly appreciated !

Br. Lars
 
I know you've already run SFC previously, but I'd like a fresh log file just to verify nothing is found.

SFC Scan

  1. Click on the Start
    Start%20Orb.jpg
    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 commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt

  4. This will create a file, cbs.txt on your Desktop. Please zip and attach this to your next post.
 
Code: 
2020-03-02 11:05:15, Info                  CBS    Appl: DetectUpdate, Package: Microsoft-Windows-Smtpsvc-Service-Package~31bf3856ad364e35~amd64~~6.1.7601.17514, Remote Parent: IIS-ODBCLogging, Parent Missing (ERROR_FILE_NOT_FOUND), non-critical error, ignored, check case sensitivity
2020-03-02 11:05:15, Info                  CBS    Appl: Evaluating applicability block(detectUpdate part), disposition is: Staged, applicability: NotApplicable, result applicability state: Staged
2020-03-02 11:05:15, Info                  CBS    Appl: DetectUpdate, Package: Microsoft-Windows-Smtpsvc-Service-Package~31bf3856ad364e35~amd64~~6.1.7601.17514, Remote Parent: Smtpsvc-Admin-Update-Name, Intended State: Staged
2020-03-02 11:05:15, Info                  CBS    Appl: Evaluating applicability block(detectUpdate part), disposition is: Staged, applicability: NotApplicable, result applicability state: Staged
2020-03-02 11:05:15, Info                  CBS    Appl: Package: Microsoft-Windows-Smtpsvc-Service-Package~31bf3856ad364e35~amd64~~6.1.7601.17514, Update: Smtpsvc-Service-Update-Name, Applicable: NeedsParent, Disposition: Staged

I do see there were a fair number of pending renames that were applied with the SFC run. Go ahead and restart, then check for any available Windows Updates.
If any are offered, choose one and attempt to install it. If the installation fails, zip and attach the CBS log.
 
After a reboot I did a search for updates, and did (apart from the KB4534310 (which previously where the only update) now also see the KB4539601 update… - first I tried just to install the KB4534310, that failed, then I tried to install the KB4539601, failed as well, I then downloaded the KB4539601 from the MS catalogue and tried to install it manually, that one failed as well :-(

I’ve then made yet another SFC Scan followed by yet another robot, and yet another attempt of installing the KB4534310 as well as the KB4539601, but it just kept failing.

I've created e new cbs.log, however even in Zipped version it's 12 MB !! (350 mb un-zipped) - it's to big to attach here, so I've uploaded it to this link instead www.idaogknud.dk\cbs.zip

Thanks a lot for the effort you’ve put into it so far !
 
Code: 
020-03-04 14:24:00, Info                  CBS    Exec: Unprojecting Package: Package_1455_for_KB4093118~31bf3856ad364e35~amd64~~6.1.1.4, Update: 4093118-4211_neutral_LDR, UninstallDeployment: amd64_6148bda12571ef836d7634626221ea16_31bf3856ad364e35_7.6.7601.23806_none_7ae9eaf78756b877
2020-03-04 14:24:00, Error                 CBS    Failed. Attempted to uninstall a version of a non-driver component that is not installed, version: 0X700061db15cfe, component: amd64_microsoft-windows-w..owsupdateclient-aux_31bf3856ad364e35_7.6.7601.23806_none_ce0a5ec791eca700, owner: Package_1455_for_KB4093118~31bf3856ad364e35~amd64~~6.1.1.4.4093118-4211_neutral_LDR [HRESULT = 0x80004005 - E_FAIL]
2020-03-04 14:24:00, Info                  CBS    Failed to mergecomponent [HRESULT = 0x80004005 - E_FAIL]

Install Update with DISM

  1. Download the update MSU here: http://download.windowsupdate.com/d..._5ea1778b896fcc764e0db8da7d094f62dc98d82f.msu
  2. Copy the MSU file to a convenient location (such as C:\temp).
  3. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  4. When you see Command Prompt on the list, right-click on it and select Run as administrator
  5. When command prompt opens, copy and paste the following commands into it, press enter after each

    cd C:\temp

    replace C:\temp with your path if different

    expand {update name}.msu -f:* C:\temp

    replace {update name} with the name of the MSU file downloaded in step 1

    DISM.exe /Online /Add-Package /PackagePath:C:\temp\{update name}.cab

  6. You should receive the message:
    The operation completed successfully.
    Restart Windows to complete this operation.
    Do you want to restart the computer now (Y/N)?
  7. Make sure to allow the computer to restart if prompted.

    If you receive any other message:
  8. Right-click on the Command Prompt window and click Select All, this will invert all of the colours by selecting the text, now press enter. All of this text is now copied.
  9. Paste (Ctrl+V) it into your next post.
  10. Zip and attach C:\Windows\Logs\CBS\CBS.log

You may wish to rename the downloaded MSU to something more convenient, such as Windows6.1-kb4093118-x64.msu before beginning the command line portion.
 
Last edited:
Hello zcomputerwiz!



Sorry for this late response!



I followed your suggestion, and where able to perform the steps 1-6 and ended up with the message “The operation completed successfully.” Without any request for a reboot.

Microsoft Windows [Version 6.1.7601]

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\lsiadmin>cd C:\temp

C:\Temp>expand Windows6.1-kb4093118-x64.msu -f:* C:\temp

Microsoft (R) File Expansion Utility Version 6.1.7600.16385

Copyright (c) Microsoft Corporation. All rights reserved.

Adding C:\temp\WSUSSCAN.cab to Extraction Queue

Adding C:\temp\Windows6.1-KB4093118-x64.cab to Extraction Queue

Adding C:\temp\PkgInstallOrder.txt to Extraction Queue

Adding C:\temp\PCIClearStaleCache.exe to Extraction Queue

Adding C:\temp\Windows6.1-KB4093118-x64-pkgProperties.txt to Extraction Queue

Adding C:\temp\Windows6.1-KB4093118-x64.xml to Extraction Queue

Expanding Files ....

Expanding Files Complete ...

6 files total.

C:\Temp>DISM.exe /Online /Add-Package /PackagePath:C:\temp\Windows6.1-kb4093118-

x64.cab

Deployment Image Servicing and Management tool

Version: 6.1.7601.24499

Image Version: 6.1.7601.24499

Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~

~7601.24106.1.4

[==========================100.0%========================= ]

The operation completed successfully.



I’m then a little unsure what next steps I should perform? (I tried to install the KB4534310 once more, but still get the same error)
 
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