Error: 0x80070003 when installing KB 2919355

This error appears to be related to expected files, folders or registry paths that are missing.

One commonly reported folder being missing is the C:\Users\Default folder.

 

Open the File Explorer, expand C, and expand the Users folder.

If there is no folder named Default, create one.

 

If C:\Users\Default exists please use the following guidance:

 

Run the Windows Update Troubleshooter, then open Windows Update and try to install the update again.

 

Then run the DISM tool

 

  1. Swipe in from the right edge of the screen, and then tap Search.

(If you're using a mouse, point to the lower-right corner of the screen, move the mouse pointer up, and then click Search.)

  1. Enter command prompt in the search box.
  2. In the list of results, swipe down on or right-click Command Prompt, and then tap or click Run as administrator.
  3. In the Administrator: Command Prompt window, enter the following commands. Press the Enter key after each command:
    1. DISM.exe /Online /Cleanup-image /Scanhealth
    2. DISM.exe /Online /Cleanup-image /Restorehealth
  4. To close the Administrator: Command prompt window, type Exit, and then press Enter.
  5. Run Windows Update again.

 

If you have C:\Users\Default and you have used the Windows Update troubleshooter and completed the DISM commands but still experience Error 0x80070003 please contact Microsoft Support so that we can further investigate your issue.
|

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

     It may also be worth noting that the C:\Users\Default folder is not the only one for which anecdotal evidence exists that, if missing from it's proper place, the update will fail.  The lack of a  ProgramData/Microsoft/Windows/Start Menu/System Tools has been mentioned as another

possible/probable culprit in the Answers Community threads "KB2919355 (Windows 8.1 Update) Fails on Windows 8.1 Pro with error Code 80070057." (pg. 2) and the now-locked "KB2919355 (Windows 8.1 Update) Fails (800f0092 and 80073712) on Windows 8.1 Pro w Media Center" (pg. 23, among others).

2 people found this reply helpful

Was this reply helpful?

Yes
No

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I received same error code [Error: 0x80070003] when in Microsoft Store as installing free and paid applications/programs.  I had to restart my computer to complete the downloads.  It seems that my computer does periodical lock ups during updates (NO ERROR MESSAGES and/or warnings).  Not sure if issues are connected but I believe I need to put it out there.

Respectfully,

K

ask, believe, & receive @}-'--

Was this reply helpful?

Yes
No

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi Sharath

I have tried your instructions as above without success.

Please see the following message I got when I tried these instructions.

Microsoft Windows [Version 6.3.9600]

(c) 2013 Microsoft Corporation. All rights reserved.

 

C:\WINDOWS\system32>DISM.exe/Online/Cleanup-image/Scanhealth

 

Deployment Image Servicing and Management tool

Version: 6.3.9600.16384

 

 

Error: 87

 

The online/cleanup-image/scanhealth option is unknown.

For more information, refer to the help by running DISM.exe /?.

 

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

 

C:\WINDOWS\system32>DISM.exe/Online/Cleanup-image/Restorehealth

 

Deployment Image Servicing and Management tool

Version: 6.3.9600.16384

 

 

Error: 87

 

The online/cleanup-image/restorehealth option is unknown.

For more information, refer to the help by running DISM.exe /?.

 

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

 

C:\WINDOWS\system32>

What do I do next,

Regards

Robbie McLaughlan

Was this reply helpful?

Yes
No

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Please see the following message I got when I tried these instructions.

Microsoft Windows [Version 6.3.9600]

(c) 2013 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>DISM.exe/Online/Cleanup-image/Scanhealth

Deployment Image Servicing and Management tool

Version: 6.3.9600.16384

Error: 87

The online/cleanup-image/scanhealth option is unknown.

For more information, refer to the help by running DISM.exe /?.

You need spaces between the parameters you pass to DISM.exe:

DISM.exe /Online /Cleanup-image /Scanhealth

Try again with spaces. You should be able to copy/paste the commands directly from this thread.

4 people found this reply helpful

Was this reply helpful?

Yes
No

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Thanks for your help Warp9

I tried the commands with spaces and the following is the result

Microsoft Windows [Version 6.3.9600]

(c) 2013 Microsoft Corporation. All rights reserved.

 

C:\WINDOWS\system32>dism.exe /Online /Cleanup-image /Scanhealth

 

Deployment Image Servicing and Management tool

Version: 6.3.9600.16384

 

Image Version: 6.3.9600.16384

 

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

The component store is repairable.

The operation completed successfully.

 

C:\WINDOWS\system32>DISM.exe /Online /Cleanup-image /Restorehealth

 

Deployment Image Servicing and Management tool

Version: 6.3.9600.16384

 

Image Version: 6.3.9600.16384

 

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

The restore operation failed. Either the repair source was not found or the comp

onent store cannot be repaired.

 

Error: 0x800f081f

 

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

 

C:\WINDOWS\system32>

What do I do now

2 people found this reply helpful

Was this reply helpful?

Yes
No

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hello!

Try to follow these steps:

  1. Go to C:\WINDOWS\Logs\DISM\    folder.
  2. Delete the dism.log  file.
  3. Open the Command Prompt (Administrator)
  4. Type  DISM.exe /Online /Cleanup-image /Restorehealth  and press the "Enter" key
  5. Copy  the new   C:\WINDOWS\Logs\DISM\dism.log   file and paste it into this thread

Internet connection must be enable during this process.

2 people found this reply helpful

Was this reply helpful?

Yes
No

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi RH6M6

I carried out your instructions and the dism.log file is as follows:

Summary:
Operation: Detect and Repair
Operation result: 0x0
Last Successful Step: Entire operation 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: True

Total Operation Time: 737 seconds.
 - CDISMPackageManager::Internal_Finalize
2014-05-24 22:19:12, Info                  DISM   DISM Package Manager: PID=6124 TID=7284  - CDISMPackageManager::Internal_Finalize
2014-05-24 22:19:12, Info                  DISM   DISM Package Manager: PID=6124 TID=7284 <----- Ending corruption detect/repair info -----> - CDISMPackageManager::Internal_Finalize
2014-05-24 22:19:12, Info                  DISM   DISM Package Manager: PID=6124 TID=7284  - CDISMPackageManager::Internal_Finalize
2014-05-24 22:19:12, Info                  DISM   DISM Package Manager: PID=6124 TID=7284 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2014-05-24 22:19:12, Error                 DISM   DISM Package Manager: PID=6124 TID=7284 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)
2014-05-24 22:19:12, Info                  DISM   DISM Package Manager: PID=6124 TID=7284 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2014-05-24 22:19:12, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F081F
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM Package Manager: PID=6124 TID=6396 Finalizing CBS core. - CDISMPackageManager::Finalize
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Finalizing the servicing provider(IBSManager) - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Disconnecting Provider: IBSManager - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Finalizing the servicing provider(AppxManager) - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Disconnecting Provider: AppxManager - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Finalizing the servicing provider(AssocManager) - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Disconnecting Provider: AssocManager - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Finalizing the servicing provider(GenericManager) - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Disconnecting Provider: GenericManager - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6124 TID=6396 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2014-05-24 22:19:12, Info                  DISM   DISM.EXE:
2014-05-24 22:19:12, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2014-05-24 22:19:12, Info                  DISM   DISM.EXE:
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6916 TID=1220 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6916 TID=1220 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2014-05-24 22:19:12, Info                  DISM   DISM Provider Store: PID=6916 TID=1220 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

I hope this will help you solve my problem

2 people found this reply helpful

Was this reply helpful?

Yes
No

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

OK

Do nothing

Now we have to look through   С:\Windows\logs\CBS\cbs.log

This is the rather big file.

Upload it to OneDrive, please, and paste the link here

2 people found this reply helpful

Was this reply helpful?

Yes
No

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

***It appears I have stumbled upon a fix for all KB2919355 issues and will be posting this to numerous forum threads***

As many discoveries have been made, I discovered this accidentally. and quite by coincidence... 

In order for users, who've been plagued by errors and file corruption, to get a successful completion of KB2919355, all that's needed is to run the 8.1 upgrade installer, and when the 8.1 installed goes to the wait screen after entering the generic product key, start Windows Update for the install of KB2919355

Steps

  1. Run the Windows 8.1 installer from within Windows, as if you're going to do an install repair "upgrade".
  2. Enter the generic product key, and upon clicking next, the installer will say wait... 
  3. Give the installer about 5 minutes, then start Windows Update (it should show the KB2919355 update), and click install.
  4. Windows Update will begin downloading the update... if you have a Windows Update cache problem that causes the speed and percentage to remain at zero, don't worry about it and get the update installed first, then you can clear the cache and remove the directories afterwards.
  5. The install may fail, don't worry... simply hit install again, making sure the 8.1 installer screen is still on the "wait" screen, as whatever the installer is doing during the "wait" screen is what makes the KB2919355 install possible. 
  6. KB2919355 should install and Windows Update should request you to restart... simply do so without cancelling the 8.1 installer.  Windows will finalize the update during the shutdown and restart processes.
  7. Upon rebooting into Windows, you will have a multitude of additional updates that will need to be installed (around 10, give or take a few), and you can verify the install of KB2919355 by going to "view installed updates" 

A few users will need to comment back once they'e performed this in order to see if this automatically fixes the multitude of issues users are facing, and if it doesn't complete successfully, then I can back track what step I took over the past several days in order to figure out what caused this to work for me, but not others if problems occur.


2 people found this reply helpful

Was this reply helpful?

Yes
No

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

C:\Users\Compaq_Administrator.ROBBIE\SkyDrive\CBS log file.

I hope I have this link right!

3 people found this reply helpful

Was this reply helpful?

Yes
No

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Question Info


Last updated August 18, 2021 Views 29,354 Applies to: