Windows 10: KB4103721 fails repeatedly, DISM will not restorehealth

  1.    12 Jun 2018 #1

    KB4103721 fails repeatedly, DISM will not restorehealth


    W10Pro x64 1803 17134.1

    Attempts to install KB4103721 comulative update has failed over 10 times both as an automatic install and a manual (msu) install. 'Some update files are missing or have problems. We'll try to download the update again later. Error 0x80073712'.

    A 2nd cumulative update KB4284835 is also failing now, but other updates continue to install fine.

    To diagnose I ran sfc /scannow, and it found problems and could not complete.
    Next I ran DISM with the /scanhealth and /checkhealth options, and it reported that the system should be repairable.
    Next I ran DISM /Online /Cleanup-Image /RestoreHealth, but it could not find the necessary source files for the repair.
    I then used the media creator to download a new W10x64 17134 ISO file, and copied that install.esd to c:\.
    I also converted this esd to an install.wim to try that too.

    I have tried /restorehealth with both of these install file formats. They both fail around 87%,'The source files could not be found':

    C:\>dism /Get-WimInfo /WimFile:C:\install.esd

    Deployment Image Servicing and Management tool
    Version: 10.0.17134.1

    Details for image : C:\install.esd

    Size : 14,571,793,777 bytes

    Index : 6
    Name : Windows 10 Pro
    Description : Windows 10 Pro
    Size : 15,644,048,998 bytes

    The operation completed successfully.

    C:\>DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\install.wim

    Deployment Image Servicing and Management tool
    Version: 10.0.17134.1

    Image Version: 10.0.17134.1

    [===========================87.1%================== ]
    Error: 0x800f081f

    The source files could not be found.
    Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source | Microsoft Docs.

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

    Dism.log errors:
    2018-06-12 11:28:48, Error DISM DISM Package Manager: PID=3884 TID=5360 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)
    2018-06-12 11:28:49, Error DISM DISM Package Manager: PID=3884 TID=5360 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
    2018-06-12 11:28:49, Error DISM DISM Package Manager: PID=3884 TID=5360 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)
    2018-06-12 11:28:49, Error DISM DISM Package Manager: PID=3884 TID=5360 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
    2018-06-12 11:28:49, Error DISM DISM Package Manager: PID=3884 TID=5360 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f081f)
    2018-06-12 11:28:49, Error DISM DISM Package Manager: PID=3884 TID=5360 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)


    How do I get around this problem?
    thanks
    Last edited by tns1; 12 Jun 2018 at 14:37.
      My ComputerSystem Spec

  2.    12 Jun 2018 #2

    I see numerous reports of DISM /cleanup-image /restorehealth having issues with ESD files. You might want to convert your file to a WIM file, then try again. There's a TenForums tutorial for that: Convert ESD file to WIM using DISM in Windows 10. After you've done that run your /restorehealth again and I bet it will work. Best of luck!
    HTH,
    --Ed--
      My ComputersSystem Spec

  3.    12 Jun 2018 #3

    If you read my post, you'll see I did exactly that.
      My ComputerSystem Spec

  4.    12 Jun 2018 #4

    Observations:

    The build# for the ISO matches my system build#, and shows as x64 like it should.
    FWIW, most reports say that the 10pro image is found as index 1 of the ISO. In my ISO, 10pro is index 6.
    I can't verify a hash on the creation tool ISO file, since MS does not provide one to verify against.
    Others have reported needing a direct ISO download (not the creation tool ISO) of windows to succeed at a DISM repair.
    I'd try that, but MS seems to have removed such direct download links.
      My ComputerSystem Spec

  5.    13 Jun 2018 #5

    The MCT download includes an ESD file, the ISO download a WIM file for the Windows install image. I did miss your mention of conversion at the beginning of the post, so sorry. I concentrated on the log/diagnostic outputs instead. It might be that the conversion process was somehow flawed (have you run checkhealth or scanhealth against that .wim file offline to see if it's clean?).

    Indeed, trying again with a ISO based source for the "master files" is a good idea. Give it a try, and let us know if that works any better for you. If that doesn't work, you may want to take your image offline and work on it that way instead of online. Sometimes that will work when online won't also (though I can't say why, I've experienced this myself).

    HTH,
    --Ed--
      My ComputersSystem Spec

  6.    14 Jun 2018 #6

    I was able to get a direct download ISO (wim file). The trick is to use an XP box for the download. It behaved the same as the creation tool ISO. The needed source files were not found. I am thinking it may be time for a windows reset or clean install.
      My ComputerSystem Spec


  7. Posts : 20,757
    windows 10 professional version 1607 build 14393.969 64 bit
       15 Jun 2018 #7

    See if you can perform an in place upgrade repair:
    Repair Install Windows 10 with an In-place Upgrade | Windows 10 Tutorials
    Download Windows 10

    Had you made a backup image or have a valid restore point?
      My ComputerSystem Spec

  8.    15 Jun 2018 #8

    Yes, I agree with zbook's advice: sounds like it's time for an in-place repair upgrade install.

    Also, if you change the user agent designation in your web browser you don't need to use XP. Here's a TenForums thread that explains how to do this: How to Download Creators Update ISO via MS w/o Media Creation Tool. There's a good WinHelpOnline story on this too: Get Windows 10 Official ISO Images Using MCT Or Direct Download.
    HTH,
    --Ed--
      My ComputersSystem Spec

  9.    24 Jun 2018 #9

    I did a windows reset mainly to see if it could. It did recover and passed sfc, but I wanted to be thorough and ended up doing a clean install anyway.
    thanks
      My ComputerSystem Spec


 

Related Threads
After updating my desktop PC last night to Win 10 1709 edition 16299.98 using an elevated command prompt(administrator) I ran sfc/ scannow and DISM /online /cleanup-image /restorehealth to cheack for any issues. SFC ran fine and found zero issues...
sfc and dism....restorehealth in 16299.64 in Performance & Maintenance
In the previous build (16299.19) I had the issue of contracticting reports between sfc /scannow (reported "corrupt files unable to repair"), and dism.....restorehealth (reported "operation completed successfully"). ref : sfc and dism ..... old...
Really weird. Ran SFC Scannow. Says I have some corrupt files. So I went ahead and did the DISM/Restorehealth and it said it completed successfully. But when I run SFC again getting same error. Wouldn't a DISM/Restorehealth fix any issues with...
SFC Scannow or DISM/RestoreHealth using Image in Performance & Maintenance
Windows 10 user. Having some trouble with my system after coming back from a weekend. Nothing major...just having trouble playing some games that require plugins etc Regardless if it's related, I just wanted to run an SFC/Scannow or...
Error DISM restorehealth in Performance & Maintenance
Hello I use the Windows DVD 10 and option 3 with IMAGE_HEALTH and have an error 50: http://www.eightforums.com/performance-maintenance/68326-sfc-scannow-dism-restorehealth-repair-corrupt-files.html 0x800f081f and operation not fix !!
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 07:15.
Find Us