none
DISM problem to repair image after upgrading to 1703 Enterprise

    Question

  • I think there is something wrong with DISM in v1703.

    I 've used DISM and SFC for years without any problems, but now it's getting strange.

    I've downloaded the official ISO for 1703 Enterprise yesterday, burned a DVD, started Setup.EXE and did an upgrade installation.

    Everything went fine - system works as expected without any errors.

    I started to verify my installation with SFC command -> everything OK, no problems!

    Now, I 've checked the image with DISM with Dism /Online /Cleanup-Image /ScanHealth -> image corrupted, can be repaired.

    I did Dism /Online /Cleanup-Image /RestoreHealth /source:wim:z:\sources\install.wim:1 /limitaccess with my DVD in drive Z: and I also tried Dism /Online /Cleanup-Image /RestoreHealth -> everytime I get an error: 0x800f081f

    System is OK, SFC states that everything is OK -> only my Image seems to be in need of repair and I can't get this working :( !

    Please help!

    Here's the log:

    2017-04-06 20:55:36, Info                  DISM   DISM Package Manager: PID=5232 TID=15076 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
    2017-04-06 20:55:36, Info                  DISM   DISM Package Manager: PID=5232 TID=15076 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
    2017-04-06 20:55:36, Info                  DISM   DISM Package Manager: PID=5232 TID=15076 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
    2017-04-06 20:55:36, Info                  DISM   DISM Package Manager: PID=5232 TID=15076 CBS session options=0x40100! - CDISMPackageManager::Internal_Finalize
    2017-04-06 20:58:13, Info                  DISM   DISM Package Manager: PID=5232 TID=13980  Error in operation: source for package or file not found, ResolveSource() unsuccessful. (CBS HRESULT=0x800f081f) - CCbsConUIHandler::Error
    2017-04-06 20:58:13, Error                 DISM   DISM Package Manager: PID=5232 TID=15076 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)
    2017-04-06 20:58:13, Error                 DISM   DISM Package Manager: PID=5232 TID=15076 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
    2017-04-06 20:58:13, Error                 DISM   DISM Package Manager: PID=5232 TID=15076 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)
    2017-04-06 20:58:13, Error                 DISM   DISM Package Manager: PID=5232 TID=15076 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
    2017-04-06 20:58:13, Error                 DISM   DISM Package Manager: PID=5232 TID=15076 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f081f)
    2017-04-06 20:58:13, Error                 DISM   DISM Package Manager: PID=5232 TID=15076 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)
    2017-04-06 20:58:13, Info                  DISM   DISM Package Manager: PID=5232 TID=15076 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
    2017-04-06 20:58:13, Info                  DISM   DISM Provider Store: PID=5232 TID=15076 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2017-04-06 20:58:13, Info                  DISM   DISM Provider Store: PID=5232 TID=15076 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2017-04-06 20:58:13, Info                  DISM   DISM Provider Store: PID=5232 TID=15076 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2017-04-06 20:58:13, Info                  DISM   DISM Provider Store: PID=5232 TID=15076 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2017-04-06 20:58:13, Info                  DISM   DISM Package Manager: PID=5232 TID=15076 Finalizing CBS core. - CDISMPackageManager::Finalize

    Thursday, April 6, 2017 11:03 PM

Answers

All replies

  • ............I think there is something wrong with DISM in v1703..............


    I know you use Enterprise version.

    This problem you described has been in existence for 4 builds in Insider Preview program.

    I let it slide as long as sfc /scannow works and reports no integrity violation. But that's just me.

    Perhaps you would want to report the issue at Feedback Hub.

    Friday, April 7, 2017 3:01 AM
  • Hi ,

    Your discovery is valuable. We sincerely appreciate your taking time to provide your feedback and thank you for the collected data. We have submitted it to system product team via our internal feedback tool, you could also use the built-in feedback hub to submit on your side.

    Best regards

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

    Friday, April 7, 2017 7:17 AM
    Moderator
  • 2017-04-06 20:58:13, Info                  DISM   DISM Package Manager: PID=5232 TID=13980  Error in operation: source for package or file not found, ResolveSource() unsuccessful. (CBS HRESULT=0x800f081f) - CCbsConUIHandler::Error


    Use the CBS.log indexed by this timestamp to check what your error is.  If it is the one known error then I agree with David--ignore it.  Unfortunately this makes the use of DISM as an integrity check more cumbersome.


    Robert Aldwinckle
    ---

    Friday, April 7, 2017 3:09 PM
  • Same problem here. Installed 1703 using windows.iso file created with Media Creation Tool. This worked fine. 

    When mounting the windows.iso file, DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:G:\Sources\Install.wim:1 /LimitAccess does not work as this iso contains an Install.esd file.

    When mounting the Win10_1703_English_x64.iso file it still does not work although this iso has the necessary Install.wim file.

    The latter always worked fine for the 1511 and 1607 versions.

    PS. I downloaded the Win10_1703_English_x64.iso file from http://windowsiso.net/windows-10-iso/windows-10-creators-update-1703-download-build-15063/windows-10-creators-update-1703-iso-download-standard/


    • Edited by W10Creator Friday, April 7, 2017 3:57 PM
    Friday, April 7, 2017 3:55 PM
  • This is a problem created by Microsoft Windows 10 newly updates in both RTM and Insider Previews.

    We shouldn't have to try to fix it.

    In fact I doubt anyone outside MS Development Team can fix it.

    This problem started at least 4 builds back, and you think Microsoft will fix it. An important part of troubleshooting application ?

    If you think we have not told Microsoft via Feedback HUB, have a look at the HUB. There is a long list of entries posting the same issue.

    Friday, April 7, 2017 4:01 PM
  • Thanks for your reply. I now know it's the tool and not the fool :-)

    Friday, April 7, 2017 4:14 PM
  • Thank you for your answers.

    I switched back to v1607 using my Image-Backup (wanted to try this for a long time to check if my Baclup is working ;-) !)

    Now, waiting for refreshed ISOs from MS.

     

    Sunday, April 9, 2017 6:48 AM
  • Thank you for your answers.

    I switched back to v1607 using my Image-Backup (wanted to try this for a long time to check if my Baclup is working ;-) !)

    Now, waiting for refreshed ISOs from MS.

     

    Suggest you run the dism...../restorehealth on your version 1607.

    My money is you will have the same error message.............source files could not be found.


    Sunday, April 9, 2017 6:52 AM
  • Yesterday I re-upgraded W10 using the Win10_1703_English_x64.iso downloaded from http://windowsiso.net/windows-10-iso/windows-10-creators-update-1703-download-build-15063/windows-10-creators-update-1703-iso-download-standard/

    When mounting this iso, there is an install.wim file in the sources folder.

    Afterwards I ran DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:G:\Sources\Install.wim:1 /LimitAccess

    I'm still getting the error message that it cannot find the source file.

    Seems like an issue as this always worked fine with earlier W10 versions.

    Sunday, April 9, 2017 7:20 AM
  • Thank you for your answers.

    I switched back to v1607 using my Image-Backup (wanted to try this for a long time to check if my Baclup is working ;-) !)

    Now, waiting for refreshed ISOs from MS.

     

    Suggest you run the dism...../restorehealth on your version 1607.

    My money is you will have the same error message.............source files could not be found.


    Nope! You are wrong! Everything is OK on my machine running v1607. BTW: I've checked before the Upgrade and now again after restoring my Backup -> everything is OK!

    My 2 other Win10 PCs (Home x64 and Pro x86) show the same behavior as my Enterprise x64 after the Upgrade, so THERE IS something wrong with the Upgrade Process on the ISOs!

    Sunday, April 9, 2017 10:26 AM
  • It seems that EVERY installation features this problem. Anyone out there who could run DISM without errors?

    https://www.tenforums.com/performance-maintenance/81640-windows-10-creators-update-dism.html

    https://www.tenforums.com/performance-maintenance/81413-creators-update-component-store-shows-corruption-but-unable-repair.html

    Would be nice to hear anything from MS about this issue.

    Thursday, April 13, 2017 3:52 PM
  • It seems that EVERY installation features this problem.

    Evidently.  I was hoping the CU would have fixed it but apparently not.

    PS>Repair-WindowsImage -Online -ScanHealth
    
    
    Path             :
    Online           : False
    ImageHealthState : Repairable
    RestartNeeded    : False
    
    
    
    PS>(gc ..\Logs\CBS\CBS.log)[-200..0] | clip
    PS>ise
    PS>
    
    
    (p)	CBS MUM Corrupt			Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0
    

    BTW just the last 40 records would have been enough in this case.



    Robert Aldwinckle
    ---

    Thursday, April 13, 2017 11:34 PM
  • This is definitely a new issue in 1703 (10.0.15063.138).  CBS log indicates:

    Checking System Update Readiness.
    
    (p)	CBS MUM Corrupt			Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0
    
    Summary:
    Operation: Detect and Repair 
    Operation result: 0x800f081f
    Last Successful Step: Entire operation completes.
    Total Detected Corruption:	1
    	CBS Manifest Corruption:	1


    However, 

    Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0
    

    does not exist in install.wim... It's referred to in the online registry by the following registry keys:

    1st Loction:
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0]

    2nd Location:
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0]

    (from another forum)

    DISM /ONLINE servicing refers to the registry, sees that Microsoft-Windows-TestRoot-and-FlightSigning-Package.. should be there, but can't find it in the WIM file.

    This is benign...

    Friday, April 14, 2017 7:57 PM
  • Tuesday, April 25, 2017 12:01 PM