none
[SOLVED! Windows Update BUG!] Windows Update Failure [7SP1 x64] KB4074598 [HRESULT = 0x80004005 - E_FAIL] RRS feed

  • Question

  • The computer successfully installs the update, on reboot while configuring updates, it hits 98% complete then fails. Registry settings show Trusted Installer "start" set to (2) before restarting. I see no group policy for trusted installer after updating policy with Security Compliance Manager 4.0; 

    Tried clean boot install; Did online and offline sfc scan (zero integrity violations) Ran Windows Update Troubleshooter. Still receiving this error. 

    Dism /Online /Cleanup-Image /ScanHealth = CBS.log

    2018-03-02   01:44:12:651   344   1140   Handler   Post-reboot status for package Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24055.1.3: 0x80004005.
    2018-03-02   01:44:12:651   344   1140   Handler   WARNING: Got extended error: "Generic Command   ErrorCode   80004005   Executable   netsh.exe   ExitCode   1   Phase   24   Mode   Uninstall (upgrade)   Component   Microsoft-Windows-PeerDist, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"

    2018-03-02 02:43:54, Info                  CBS    Ending TrustedInstaller initialization.
    2018-03-02 02:43:54, Info                  CBS    Starting the TrustedInstaller main loop.
    2018-03-02 02:43:54, Info                  CBS    TrustedInstaller service starts successfully.
    2018-03-02 02:43:54, Info                  CBS    SQM: Initializing online with Windows opt-in: False
    2018-03-02 02:43:54, Info                  CBS    SQM: Cleaning up report files older than 10 days.
    2018-03-02 02:43:54, Info                  CBS    SQM: Requesting upload of all unsent reports.
    2018-03-02 02:43:54, Info                  CBS    SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
    2018-03-02 02:43:54, Info                  CBS    SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
    2018-03-02 02:43:54, Info                  CBS    SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
    2018-03-02 02:43:54, Info                  CBS    SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]
    2018-03-02 02:43:54, Info                  CBS    No startup processing required, TrustedInstaller service was not set as autostart, or else a reboot is still pending.
    2018-03-02 02:43:54, Info                  CBS    NonStart: Checking to ensure startup processing was not required.
    2018-03-02 02:43:54, Info                  CSI    00000004 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x111f6b0
    2018-03-02 02:43:54, Info                  CSI    00000005 Creating NT transaction (seq 1), objectname [6]"(null)"
    2018-03-02 02:43:54, Info                  CSI    00000006 Created NT transaction (seq 1) result 0x00000000, handle @0x200
    2018-03-02 02:43:54, Info                  CSI    00000007@2018/3/2:09:43:54.041 CSI perf trace:
    CSIPERF:TXCOMMIT;200
    2018-03-02 02:43:54, Info                  CBS    NonStart: Success, startup processing not required as expected.
    2018-03-02 02:43:54, Info                  CBS    Startup processing thread terminated normally
    2018-03-02 02:43:54, Info                  CSI    00000008 CSI Store 5485296 (0x000000000053b2f0) initialized
    2018-03-02 02:43:54, Info                  CBS    Session: 30650890_4197273720 initialized by client DISM Package Manager Provider.
    2018-03-02 02:44:14, Info                  CBS    Archived backup log: C:\Windows\Logs\CBS\CbsPersist_20180302094353.cab.

    Any advice?




    • Edited by tutudid Thursday, April 12, 2018 1:51 PM
    Friday, March 2, 2018 2:41 PM

Answers

  • Solved, 2 months later! After 3 dist upgrades!

    So I finally solved this Windows / Update BUG, it and it was as simple as this; set peerdissvc (under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\) (aka branchcache as it is known under services.msc) from disabled back to manual, along with its dependency http, to manual. I'm quite sure setting branchcache to manual was all that was necessary for the fix to take place; I also had set "not configured" to alll changes I had made to "Background Intelligence Transfer Service" under group policy regarding peer caching. I had tried the latter before the last 3 distupgrades and it did not make any difference; so it seems windows update fails if you disable branchcache, which is typically only used by businesses anyway, so many people recommend to disable it, for security reasons also. What a headache; I spent at least a 80 hours, and weeks, and months trying to figure this one out; Windows update has turned into a bunch of bull***** with their ROLLUPS; one error on one of 130 little updates and the whole shebang goes down with the ship; dumbest idea ever for their update platform; they should change to individual updates and do it quick.

    This is a MICROSOFT WINDOWS UPDATE BUG. You shouldn't have to enable or disable any built in windows service to get a "windows" update working. What a headache.

    SO for all of you 80004005 victims out there; check your C:\Windows\Logs\CBS\cbs.log; search for "error" or "Failed execution" know very well whatever app is failing to install, be it IIS as quoted below-> they disabled IIS and it fixed their problem, or peerdist -> I had to set it from disabled to manual, so make sure you fiddle with enabling or disabling the failing install service using services.msc or under the registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\

    Change the entry "start" to demand or auto, or disable if it was already enabled, reboot, then try your update.

    0 Boot
    1 system
    2 Automatic
    3 Demand (aka manual)
    4 Disabled




    • Marked as answer by tutudid Thursday, April 12, 2018 1:43 PM
    • Edited by tutudid Thursday, April 12, 2018 2:33 PM
    Thursday, April 12, 2018 1:43 PM

All replies

  • Hi tutudid,

    Try this:

    net stop wuauserv

      net stop cryptSvc

      net stop bits

      net stop msiserver 

    Ren C:\Windows\SoftwareDistribution SoftwareDistribution.old 

    Ren C:\Windows\System32\catroot2 Catroot2.old 

    net start wuauserv 

    net start cryptSvc 

    net start bits 

    net start msiserver

    Regards

    Simon


    If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful. Regards Simon Disclaimer: This posting is provided AS IS with no warranties or guarantees, and confers no rights.

    Friday, March 2, 2018 4:59 PM
  • With Sfc /Scannow  any errors or warnings will be in Win OS..However with windows running the repairs can not be

    done in Win explorer.So once Sfc is thru,type: CHKDSK C: /F  agree to restart,type: EXIT  restart pc.The repairs are in MS-DOS/reboot of pc...

    Friday, March 2, 2018 11:33 PM
  • Ran chkdsk c: /f; Still getting the same windows update error;

    this:


    net stop wuauserv
    net stop cryptSvc
    net stop bits
    net stop msiserver 
    Ren C:\Windows\SoftwareDistribution SoftwareDistribution.old 
    Ren C:\Windows\System32\catroot2 Catroot2.old 
    net start wuauserv 
    net start cryptSvc 
    net start bits 
    net start msiserver
    net start wuauserv

    resulted in finding two new updates; on of which kb3159706; that contains some improvements to Windows Update Client in Windows 7 Service Pack 1 (SP1); Installed that update first; Then KB4074598; the result; same error. Just ran sfc /scannow again; zero errors.

    Saturday, March 3, 2018 12:31 AM
  • http://www.tomshardware.com/answers/id-2686192/win-update-working.html

    This can be triggered by some pretty obscure software apparently; not sure how this guy figured his problem out but here is an example from the above link:

    "I figured it out. It was the preinstalled Intel RAID storage manager software. 
    I uinstalled it, and Windows Update worked."

    Saturday, March 3, 2018 12:36 AM
  • Windows Update Troubleshooter ALSO detected the following:

    Problems found: Windows update error 0x80070005

    RootCause: RC_DataStore
    ErrorCode: 0x80070005
    TimeDetected: 2018-03-02-T-5:34:40P
    Collected File
    File Name: CheckSURLog.cab

    I've included some logs in the following file

    https://mega.nz/#!7zgGVITY!nwqjK4VYtH91UzGINPjTXnXWqs1BOALPsZ0OtZ4h28A

    Saturday, March 3, 2018 1:07 AM
  • Dism /Online /Cleanup-Image /ScanHealth checksur.log

    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7601.23471
    2018-03-02 18:00

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_79_for_KB3172605~31bf3856ad364e35~amd64~~6.1.1.2.mum Line 1: 
    (f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_79_for_KB3172605~31bf3856ad364e35~amd64~~6.1.1.2.cat
    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_80_for_KB3172605~31bf3856ad364e35~amd64~~6.1.1.2.mum Line 1: 
    (f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_80_for_KB3172605~31bf3856ad364e35~amd64~~6.1.1.2.cat

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages

    Checking Component Store
    (f) CSI C Mark Deployment Missing 0x00000000 c!policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_ef17e13d91c55d96 amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_499a1b14d5902dfc
    (f) CSI Missing Winning Component Key 0x00000000 amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.25325.0_none_4b5d1834d3072800
    (f) CSI C Mark Deployment Missing 0x00000000 c!policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_36c51814a641869c x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_914751ebea0c5702
    (f) CSI Missing Winning Component Key 0x00000000 x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.25325.0_none_97ea50fde4578039
    (f) CSI C Mark Deployment Missing 0x00000000 c!policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_364e78aca69bba41 x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_962753dde6e08635
    (f) CSI Missing Winning Component Key 0x00000000 x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.25325.0_none_930a4f0be7835106

    Summary:
    Seconds executed: 111
     Found 10 errors
      CSI C Mark Deployment Missing Total count: 3
      CBS MUM Corrupt Total count: 2
      CBS Catalog Corrupt Total count: 2
      CSI Missing Winning Component Key Total count: 3

    Unavailable repair files:
    servicing\packages\Package_79_for_KB3172605~31bf3856ad364e35~amd64~~6.1.1.2.mum
    servicing\packages\Package_79_for_KB3172605~31bf3856ad364e35~amd64~~6.1.1.2.mum
    servicing\packages\Package_80_for_KB3172605~31bf3856ad364e35~amd64~~6.1.1.2.mum
    servicing\packages\Package_80_for_KB3172605~31bf3856ad364e35~amd64~~6.1.1.2.mum
    servicing\packages\Package_79_for_KB3172605~31bf3856ad364e35~amd64~~6.1.1.2.cat
    servicing\packages\Package_79_for_KB3172605~31bf3856ad364e35~amd64~~6.1.1.2.cat
    servicing\packages\Package_80_for_KB3172605~31bf3856ad364e35~amd64~~6.1.1.2.cat
    servicing\packages\Package_80_for_KB3172605~31bf3856ad364e35~amd64~~6.1.1.2.cat

    Saturday, March 3, 2018 1:10 AM
  • Tried updating with march preview, same error; I see other entries like: CBS SQM: Ignoring upload request because the sample type is not enabled: Standard; What is Microsoft trying to upload to what my Windows update experts?

    CBS SQM: Upload requested for report: PackageChangeEnd_Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24058.1.5, session id: 142862, sample type: Standard
    CBS SQM: Ignoring upload request because the sample type is not enabled: Standard"

    "Sample type"? for what?

    CSIPERF:TXCOMMIT;199124
    CBS Startup: Primitive operations were successfully rolled back.
    CBS Setting RollbackFailed flag to 1
    CBS Error Startup: Rollback failed, startupPhase: 0. [HRESULT = 0x80004005 - E_FAIL]
    CBS Setting ExecuteState key to: CbsExecuteStateFailed
    CBS Doqe: Enabling Device installs
    CSI 00000100 Cancelling transactions: [1:[85]"TI4.30651110_520159795:4/Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24058.1.5"[1]"]"
    CSI 00000101 Creating NT transaction (seq 3), objectname [6]"(null)"
    CSI 00000102 Created NT transaction (seq 3) result 0x00000000, handle @0x25c
    CSI 00000103@2018/3/3:12:12:15.092 CSI perf trace:
    CSIPERF:TXCOMMIT;336203
    CBS Clearing HangDetect value
    CBS Saved last global progress. Current: 1, Limit: 1, ExecuteState: CbsExecuteStateFailed
    CBS Doqe: Unlocking driver updates, Count 4
    CBS WER: Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24058.1.5, status: 0x80004005, failure source: GC, start state: Staged, target state: Installed, client id: WindowsUpdateAgent
    CBS Failed to query DisableWerReporting flag. Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    CBS Failed to add %windir%\winsxs\pending.xml to WER report because it is missing. Continuing without it...
    CBS Failed to add %windir%\winsxs\pending.xml.bad to WER report because it is missing. Continuing without it...
    CBS SQM: Reporting package change completion for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24058.1.5, current: Installed Invalid, original: Staged, target: Installed, status: 0x80004005, failure source: GC, failure details: "80004005 netsh.exe 1 24 Uninstall (upgrade) Microsoft-Windows-PeerDist, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS ", client id: WindowsUpdateAgent, initiated offline: False, execution sequence: 1687, first merged sequence: 1687
    CBS SQM: Upload requested for report: PackageChangeEnd_Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24058.1.5, session id: 142862, sample type: Standard

    Microsoft-Windows-PeerDist is the problem. The Windows Management Framework BITS.



    • Edited by tutudid Saturday, March 3, 2018 3:29 PM
    Saturday, March 3, 2018 3:13 PM
  • How does that relate to these entries?


    018-03-02 02:43:54, Info CBS SQM: Initializing online with Windows opt-in: False
    2018-03-02 02:43:54, Info CBS SQM: Cleaning up report files older than 10 days.
    2018-03-02 02:43:54, Info CBS SQM: Requesting upload of all unsent reports.
    2018-03-02 02:43:54, Info CBS SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
    2018-03-02 02:43:54, Info CBS SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
    2018-03-02 02:43:54, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
    2018-03-02 02:43:54, Info CBS SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]

    Saturday, March 3, 2018 3:16 PM
  • Bits peerdist is the main component not installing properly; That is a component of WMF; so I installed "WMF 5.1 on Windows Server 2008 R2 and Windows 7"The result executing it normally (double clicking the installer) caused the exact same error on reboot; got to 98% then failed; Then I installed it using the included poweshell script, and it succeeded without an issue! However after this the same error occurred when running the KB4074598 again; I tried installing it simply by executing it from powershell but it seems it needs a dedicated powershell executor. Is there any way to install these updates with a powershell script as well?
    Saturday, March 3, 2018 7:19 PM
  • I am getting the same error number in "Binance" application log. 0x80004005 means "permission denied", so whoever was trying to install bits didn't have the permissions to do so. You would need to become "owner" or otherwise have such permissions. You can look at the properties of the directory to determine the owner and the security restrictions on it. 
    • Edited by tutudid Sunday, March 4, 2018 10:48 PM
    Sunday, March 4, 2018 10:22 PM
  • Hi, 

    So many errors in your log file. At this time, I recommend you perform the In-place Upgrade to repair the computer without losing any data, then do the update again. 

    https://support.microsoft.com/en-sg/help/2255099/how-to-perform-an-in-place-upgrade-on-windows-vista-windows-7-windows


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, March 5, 2018 10:09 AM
    Owner
  • Thank you Kate Li, I will certainly consider doing that very soon. I've ran into other errors with WMI as well so its looking less and less salvageable. 
    Saturday, March 10, 2018 5:56 AM
  • Hi tutudid.

    Since all these errors have been detected, the first action to take should be resetting the Windows Update components as per Microsoft Knowledge Base article 971058.
    If neither this solves the problem, perform an in-place upgrade of the operating system: read here to know how to do that.

    Bye.


    Luigi Bruno
    MCP, MCTS, MOS, MTA

    Saturday, March 10, 2018 12:58 PM
    Moderator
  • Dist upgrade solved the problem temporarily; getting the same error.
    Thursday, April 12, 2018 6:28 AM
  • Dist upgrade solved the problem temporarily; getting the same error.

    If not other solution worked fine, perform an in-place upgrade of the operating system: it will restore the operating system files while preserving stored data and installed applications; read here to know how to do that.

    Bye.


    Luigi Bruno
    MCP, MCTS, MOS, MTA

    Thursday, April 12, 2018 8:37 AM
    Moderator
  • Solved, 2 months later! After 3 dist upgrades!

    So I finally solved this Windows / Update BUG, it and it was as simple as this; set peerdissvc (under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\) (aka branchcache as it is known under services.msc) from disabled back to manual, along with its dependency http, to manual. I'm quite sure setting branchcache to manual was all that was necessary for the fix to take place; I also had set "not configured" to alll changes I had made to "Background Intelligence Transfer Service" under group policy regarding peer caching. I had tried the latter before the last 3 distupgrades and it did not make any difference; so it seems windows update fails if you disable branchcache, which is typically only used by businesses anyway, so many people recommend to disable it, for security reasons also. What a headache; I spent at least a 80 hours, and weeks, and months trying to figure this one out; Windows update has turned into a bunch of bull***** with their ROLLUPS; one error on one of 130 little updates and the whole shebang goes down with the ship; dumbest idea ever for their update platform; they should change to individual updates and do it quick.

    This is a MICROSOFT WINDOWS UPDATE BUG. You shouldn't have to enable or disable any built in windows service to get a "windows" update working. What a headache.

    SO for all of you 80004005 victims out there; check your C:\Windows\Logs\CBS\cbs.log; search for "error" or "Failed execution" know very well whatever app is failing to install, be it IIS as quoted below-> they disabled IIS and it fixed their problem, or peerdist -> I had to set it from disabled to manual, so make sure you fiddle with enabling or disabling the failing install service using services.msc or under the registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\

    Change the entry "start" to demand or auto, or disable if it was already enabled, reboot, then try your update.

    0 Boot
    1 system
    2 Automatic
    3 Demand (aka manual)
    4 Disabled




    • Marked as answer by tutudid Thursday, April 12, 2018 1:43 PM
    • Edited by tutudid Thursday, April 12, 2018 2:33 PM
    Thursday, April 12, 2018 1:43 PM
  • Here is how another user solved this issue:

    For me the problem resides with peerdist; I had already disabled it under services and its dependency "http" after the dist upgrade and updating windows.
    Another user claimed the following:

    I can also attest that IIS seemed to be the culprit for me.

    I disabled the services World Wide Web Publishing Service, IIS Admin Service and some others for good measure, set them all to manual, rebooted, then tried to install SP1 RC Refresh and that finally succeeded.
    I would get certain GUIDs in my CBS.log:
    Code Block
    2008-01-17 12:28:30, Error CSI 00000d42 (F) Failed execution of queue item Installer: Task Scheduler ({386b5911-b69e-4d2d-a3ab-796d2ec6af38}) with HRESULT 80041315 [Error,Facility=FACILITY_ITF,Code=4885 (0x1315)]. Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable (2)[gle=0x80004005]
    Old component: Microsoft-Windows-IIS-HttpErrors, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
    New component: Microsoft-Windows-IIS-HttpErrors, Version = 6.0.6001.17128, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
    CSIPERF:AIDONE;{81a34a10-4256-436a-89d6-794b97ca407c};Microsoft-Windows-IIS-HttpErrors, Version = 6.0.6001.17128, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;274
    2008-01-17 12:28:41, Error CSI 00000f12 (F) Done with generic command 110 (0x0000006e); CreateProcess returned 0, CPAW returned S_OK
    Url reservation add failed, Error: 6
    Thursday, April 12, 2018 1:43 PM
  • Confirmed, for me simply setting "branchcache" to manual (from disabled) under services.msc does the trick.
    Sunday, July 8, 2018 10:37 AM
  • If this does not help, try running surt, https://www.microsoft.com/en-us/download/details.aspx?id=3132
    Monday, August 27, 2018 2:21 PM
  • Please propose my post as answer
    Monday, August 27, 2018 2:22 PM