Share via

Error: 80070057 Unable to install Windows Updates - Windows 8

Anonymous
2014-12-28T10:11:11+00:00

<original title: Error running DISM.exe /Online /Cleanup-Image /RestoreHealth>

Hi all geeeky question here, I hope you could please help me sort this one out. :

Due to running into multiple issues with Windows Update (and done multiple times the "Repair Troubleshooter" ), ended up facing error 80070057 for multiple Windows Updates.  (I have System Center Endpoint Protection on my system, but it is disabled, so no other antivirus or third party running)

Decided to run DISM , and got report in Event Log of

"System store corruption detection and repair has completed. Status: 0x0, Total instances of corruption found: 2, total instances of corruption repaired: 0."

Of course, I ran

"DISM.exe /Online /Cleanup-Image /RestoreHealth"

and got

"

Error: 87

An error occurred while processing the command.

Ensure that the command-line arguments are valid. For more information, review t

he log file.

"

Dism.log states :

2014-12-28 10:28:21, Info                  DISM   DISM Package Manager: PID=1016 TID=3640  Error in operation: (null) (CBS HRESULT=0x80070057) - CCbsConUIHandler::Error

2014-12-28 10:28:21, Error                 DISM   DISM Package Manager: PID=1016 TID=4948 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80070057)

2014-12-28 10:28:21, Error                 DISM   DISM Package Manager: PID=1016 TID=4948 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x80070057)

2014-12-28 10:28:21, Error                 DISM   DISM Package Manager: PID=1016 TID=4948 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x80070057)

2014-12-28 10:28:21, Error                 DISM   DISM Package Manager: PID=1016 TID=4948 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80070057)

2014-12-28 10:28:21, Info                  DISM   DISM Package Manager: PID=1016 TID=4948 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine

2014-12-28 10:28:21, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80070057

and  cbs.log:

2014-12-28 10:28:15, Info                  CBS    Not able to add current session file to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2014-12-28 10:28:15, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2014-12-28 10:28:15, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2014-12-28 10:28:15, Info                  CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2014-12-28 10:28:20, Error                 CSI    0000000c (F) STATUS_INVALID_PARAMETER #245# from CCSDirect_IRtlComponentStore::EnumStoreCorruptions(...)[gle=0xd000000d]

2014-12-28 10:28:20, Error                 CSI    0000000d (F) E_INVALIDARG #244# from Windows::COM::CStorePendingStoreRepairTxn_IStorePendingStoreRepairTransaction::Detect(Flags = 5, cancelEvt = 384 (""), disp = 0)[gle=0x80070057]

2014-12-28 10:28:20, Error                 CBS    Rept: Failed to call CSI detect. [HRESULT = 0x80070057 - E_INVALIDARG]

2014-12-28 10:28:20, Info                  CBS    Failed to check CSI store. [HRESULT = 0x80070057 - E_INVALIDARG]

2014-12-28 10:28:20, Info                  CBS    Ensure CBS corruption flag is clear

2014-12-28 10:28:20, Info                  CBS    Ensure WCP corruption flag is clear

2014-12-28 10:28:20, Info                  CBS    

=================================

Checking System Update Readiness.

Summary:

Operation: Detect and Repair

Operation result: 0x80070057

Last Successful Step: CBS store detection completes.

Total Detected Corruption:    0

    CBS Manifest Corruption:    0

    CBS Metadata Corruption:    0

    CSI Manifest Corruption:    0

    CSI Metadata Corruption:    0

    CSI Payload Corruption:    0

Total Repaired Corruption:    0

    CBS Manifest Repaired:    0

    CSI Manifest Repaired:    0

    CSI Payload Repaired:    0

    CSI Store Metadata refreshed:    False

Total Operation Time: 199 seconds.

2014-12-28 10:28:20, Info                  CBS    SQM: CheckSur: hrStatus: 0x80070057 [E_INVALIDARG], download Result: 0x0 [S_OK]

2014-12-28 10:28:20, Info                  CBS    Count of times corruption detected: 0

2014-12-28 10:28:20, Info                  CBS    Seconds between initial corruption detections: -1

2014-12-28 10:28:20, Info                  CBS    Seconds between corruption and repair: -1

2014-12-28 10:28:21, Info                  CBS    SQM: Upload requested for report: CheckSurSqm, session id: 142858, sample type: Standard

2014-12-28 10:28:21, Info                  CBS    SQM: Ignoring upload request because the sample type is not enabled: Standard

2014-12-28 10:28:21, Info                  CBS    Failed to run Detect and repair. [HRESULT = 0x80070057 - E_INVALIDARG]

2014-12-28 10:28:21, Info                  CBS    Reboot mark cleared

2014-12-28 10:28:21, Info                  CBS    Winlogon: Deregistering for CreateSession notifications

2014-12-28 10:28:21, Info                  CBS    Winlogon: Stopping notify server

2014-12-28 10:28:21, Info                  CBS    Winlogon: Unloading SysNotify DLL

2014-12-28 10:28:21, Info                  CBS    Exec: Processing complete, session(Corruption Repairing): 30417536_661514780 [HRESULT = 0x80070057 - E_INVALIDARG]

2014-12-28 10:28:21, Error                 CBS    Session: 30417536_661514780 failed to perform store corruption detect and repair operation. [HRESULT = 0x80070057 - E_INVALIDARG]

2014-12-28 10:28:21, Info                  CBS    Session: 30417536_661514780 finalized. Reboot required: no [HRESULT = 0x80070057 - E_INVALIDARG]

2014-12-28 10:28:21, Info                  CBS    Failed to FinalizeEx using worker session [HRESULT = 0x80070057]

2014-12-28 10:30:21, Info                  CBS    Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP

2014-12-28 10:30:21, Info                  CBS    TiWorker signaled for shutdown, going to exit.

2014-12-28 10:30:21, Info                  CBS    Ending the TiWorker main loop.

2014-12-28 10:30:21, Info                  CBS    Ending the TrustedInstaller main loop.

2014-12-28 10:30:21, Info                  CBS    Starting TiWorker finalization.

2014-12-28 10:30:21, Info                  CBS    Starting TrustedInstaller finalization.

2014-12-28 10:30:21, Info                  CBS    Ending TrustedInstaller finalization.

2014-12-28 10:30:21, Info                  CBS    Ending TiWorker finalization.

Thank you all for looking into this!

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous
2014-12-29T09:09:24+00:00

Hello Alejandro,

Thank you for posting your query on Microsoft Community. I appreciate your efforts towards resolving the issue.

I understand that you are not able to install Windows Updates. This problem may occur if one or more of the following conditions are true:

a. If the Windows Update database is corrupted.

b. If the Background Intelligent Transfer Service (BITS) service & Cryptographic Service do not receive a content link header.

c. If a required system file is registered incorrectly.

d. Third-party application conflict.

However, before we proceed I would require some more information to assist you better.

What are KB number of the failing updates?

I would suggest you to try the following steps:

Step 1:

**Try to reset the Windows update components**and then check if it helps.

Note: Try to perform the manual steps from above article.

Important this section*, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: How to back up and restore the registry in Windows*

Step 2:

After resetting the Windows Update components, then boot the computer in **clean boot** state and try to install the updates.

Putting your system in Clean Boot state helps in identifying if any third party applications or startup items are causing the issue.

Note: After troubleshooting, refer to this section ‘How to reset the computer to start normally after clean boot troubleshooting’.

Hope this information is helpful. Please do let us know if you need further assistance, we’ll be glad to assist you.

Thank you

Was this answer helpful?

0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2015-07-30T21:13:49+00:00

    This protocol (clean boot) for installing WIN 10 (update) on a WIN 7 OS computer was quite helpful to me, after initially encountering the error code 0x80070057 several times on my system in an update procedure. My system unit has both IE and Mozilla software on it and after downloading the MS 'fix it' (repair) software and applying it, I performed the suggested 'clean boot' install. It worked perfectly, although due to the immense amount of data WIN 10 downloads (2.712  GIG), I found myself getting a bit impatient during the process, despite the apparent smooth continuity of the WIN 10 update steps. The text "Sit back and relax' on the loading screen was appropriate after all! Thanks to Sayed and the others there in support who suggested this 'work around' for us WIN 7 users.

    Was this answer helpful?

    0 comments