[SOLVED] [Win10ProV1703Build15063 x64] DISM /RestoreHealth gives error 0x800f081f

We aren't allowed to provide support by any other means than the forum. I'll be back shortly with next steps.


I now installed the update to the latest build (16184) by running the setup.exe inside of an iso of that same build I found here.


As I was quite surprised the update worked, I ran /RestoreHealth again to see if the error persisted. And it did. Even with the exact same iso I installed the iso from mounted and provided as repair source.


New View attachment dism.log and CBS.log.
 
OK, let's clean up the error your getting. The solution to that follows however I don't know if that will allow you to upgrade but worth a shot.
https://www.sysnative.com/forums/windows-10-a/22564-dism-error-0x800f081f.html#post180006

Let me know if you need assistance following the instructions in the link.

Now I am getting this in cbs.log:

Code:
2017-05-05 11:22:13, Info                  CBS    DWLD:Search is done, set download progress to 20 percent.2017-05-05 11:22:13, Warning               CBS    Current tick count lower than last tick count. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2017-05-05 11:22:13, Info                  CBS    Nothing to download, unexpected
2017-05-05 11:22:13, Warning               CBS    Current tick count lower than last tick count. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2017-05-05 11:22:13, Info                  CBS    Failed to collect payload and there is nothing to repair. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2017-05-05 11:22:13, Info                  CBS    Failed to repair store. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2017-05-05 11:22:13, Info                  CBS    Ensure WCP corruption flag is clear
2017-05-05 11:22:13, Info                  CBS    All CSI corruption was fixed, ensure CorruptionDetectedDuringAcr is clear
2017-05-05 11:22:13, Info                  CBS    Failed to clear CorruptionDetectedDuringAcr store corrupt flag (slow mode trigger). [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2017-05-05 11:22:13, Info                  CBS    
=================================
Checking System Update Readiness.


(p)    CBS Catalog Missing            Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.16188.1000
(p)    CBS Catalog Missing            Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~10.0.16188.1000


Summary:
Operation: Detect and Repair 
Operation result: 0x800f081f
Last Successful Step: Entire operation completes.
Total Detected Corruption:    2
    CBS Manifest Corruption:    2
    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: 209 seconds.


2017-05-05 11:22:13, Info                  CBS    CheckSur: hrStatus: 0x800f081f [CBS_E_SOURCE_MISSING], download Result: 0x800f0948 [CBS_E_SOURCE_MISSING_FROM_WU_CAB]
2017-05-05 11:22:13, Info                  CBS    Count of times corruption detected: 1
2017-05-05 11:22:13, Info                  CBS    Seconds between initial corruption detections: -1
2017-05-05 11:22:13, Info                  CBS    Seconds between corruption and repair: -1
2017-05-05 11:22:13, Info                  CBS    Failed to run Detect and repair. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2017-05-05 11:22:13, Info                  CBS    Reboot mark cleared
2017-05-05 11:22:13, Info                  CBS    Winlogon: Simplifying Winlogon CreateSession notifications
2017-05-05 11:22:13, Info                  CBS    Winlogon: Deregistering for CreateSession notifications
2017-05-05 11:22:13, Info                  CBS    Exec: Processing complete, session(Corruption Repairing): 30590336_2544638792 [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2017-05-05 11:22:13, Error                 CBS    Session: 30590336_2544638792 failed to perform store corruption detect and repair operation. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2017-05-05 11:22:13, Info                  CBS    Session: 30590336_2544638792 finalized. Download error: 0x800f0948 [CBS_E_SOURCE_MISSING_FROM_WU_CAB], Reboot required: no [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2017-05-05 11:22:13, Info                  CBS    Failed to FinalizeEx using worker session [HRESULT = 0x800f081f]

...and this in dism.log:

Code:
2017-05-05 11:22:13, Info                  DISM   DISM Package Manager: PID=10616 TID=4588  Error in operation: source for package or file not found, ResolveSource() unsuccessful. (CBS HRESULT=0x800f081f) - CCbsConUIHandler::Error2017-05-05 11:22:13, Error                 DISM   DISM Package Manager: PID=10616 TID=10396 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)
2017-05-05 11:22:13, Error                 DISM   DISM Package Manager: PID=10616 TID=10396 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
2017-05-05 11:22:13, Error                 DISM   DISM Package Manager: PID=10616 TID=10396 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)
2017-05-05 11:22:13, Error                 DISM   DISM Package Manager: PID=10616 TID=10396 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
2017-05-05 11:22:13, Error                 DISM   DISM Package Manager: PID=10616 TID=10396 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f081f)
2017-05-05 11:22:13, Error                 DISM   DISM Package Manager: PID=10616 TID=10396 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)
2017-05-05 11:22:13, Info                  DISM   DISM Package Manager: PID=10616 TID=10396 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
 
Please do the following.

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
1. Download attached file 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).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. 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.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Code:
Fix result of Farbar Recovery Scan Tool (x64) Version: 05-05-2017 01Ran by fedor (05-05-2017 16:33:19) Run:1
Running from C:\Users\fedor\Desktop
Loaded Profiles: fedor (Available Profiles: fedor)
Boot Mode: Normal
==============================================


fixlist content:
*****************
CreateRestorePoint:
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.16188.0]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.16188.1000]   
c:\windows\servicing\packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.16188.0.cat
c:\windows\servicing\packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.16188.0.mum
c:\windows\servicing\packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.16188.1000.cat
c:\windows\servicing\packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.16188.1000.mum
*****************


Restore point was successfully created.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0 => key removed successfully
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.16188.0 => key not found. 
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.16188.1000 => key removed successfully
"c:\windows\servicing\packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.16188.0.cat" => not found.
"c:\windows\servicing\packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.16188.0.mum" => not found.
c:\windows\servicing\packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.16188.1000.cat => moved successfully
c:\windows\servicing\packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.16188.1000.mum => moved successfully


==== End of Fixlog 16:33:35 ====
 
Now do the following.

Step#1 - DISM /RestoreHealth Scan
Warning:this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Right-click on the Start button and select Command Prompt (Admin)
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
    Dism /Online /Cleanup-Image /RestoreHealth
  3. Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
    Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
Please do the following.

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
1. Download attached file 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).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. 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.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Please do the following.

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
1. Download attached file 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).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. 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.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

UPDATE: DUUUUUUUUDEEEEEEEE!!!!!! IT WORKED!!!! THANK YOU A MILLION TIMES!!!!!!!!!! /RestoreHealth does not throw any error anymore! <3 Thank you so so so much!

Code:
Fix result of Farbar Recovery Scan Tool (x64) Version: 06-05-2017Ran by fedor (07-05-2017 11:02:52) Run:2
Running from C:\Users\fedor\Desktop
Loaded Profiles: fedor (Available Profiles: fedor)
Boot Mode: Normal
==============================================


fixlist content:
*****************
CreateRestorePoint:
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~0.0.0.0]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~10.0.16188.1000]   
c:\windows\servicing\packages\Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~10.0.16188.1000.cat
c:\windows\servicing\packages\Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~10.0.16188.1000.mum


*****************


Restore point was successfully created.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~0.0.0.0 => key removed successfully
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~10.0.16188.1000 => key removed successfully
c:\windows\servicing\packages\Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~10.0.16188.1000.cat => moved successfully
c:\windows\servicing\packages\Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~10.0.16188.1000.mum => moved successfully


==== End of Fixlog 11:03:06 ====

Thank you again for your ongoing support! :)
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top