Windows 10 V1703: Fix for DISM error 0x800F081F

[German]Microsoft’s Windows  10 Creators Update images contains a flaw. Broken manifest files are causing DISM to stall with error 0x800F081F. Here are a few details and a fix.


Advertising


What’s broken?

After upgrading a system, some users are running a file system check, as discussed within my blog post Check and repair Windows system files and component store – to assure, that all files are intact. Users upgrading or installing Windows 10 Creators Update are facing an error after executing the following commands (see also Windows 10 Creators Update Troubleshooting – part 1). The error will be shown, after the 2nd command is executed within an administrative command or PowerShell window:

DISM.exe /Online /Cleanup-image /Scanhealth
DISM.exe /Online /Cleanup-image /Restorehealth

The screenshot shown below, has been taken from my German Windows 10 V1703. The /RestoreHealt command has been aborted with error 0x800F081F.

The reason for error 0x800F081F in Windows 10 Version 1703

DISM says, that the source to repair the corrupted file can’t be found. In normal circumstances, it’s possible to use an install DVD as a source. But if the install image also contains the broken files, it won’t help.

DISM creates a log file dism.log at C:\Windows\Logs\DISM\ – but within my test environment I wasn’t able to detect the root cause (the file mentioned below was never reported). But a reader of my German blog left a comment pointing to a forum post. Within this english forum thread someone was able to detect the faulty file within the log file after executing dism … /scanhealth – it was the file:

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

that is shipped with a damaged MUM file (Microsoft Update Manifest, error CBS Corrupt MUM).

A  fix for error 0x800F081F in Windows 10 Version 1703

The fix removes all references to this file (probably left from Insider Preview program) from registry and from component store. References to component store may be found within the registry branche:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\

in subkeys:

Component Based Servicing\PackageIndex
Component Based Servicing\Package

To remove the registry entries, proceed the following steps.

1. Launch registry editor regedit.exe from an administrator account or use Run as administrator context menu command after searching for the file in taskbar’s search box.

2. Confirm UAC and navigate to the following registry keys.

3. Grant full access rights to the admin account and delete the entries using context menu command delete.

It’s probably a good idea to export the registry key into a .reg file using File/Export.

The first key is:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0

The 2nd key is:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0

You can’t delete these keys, even, if you an administrator, because of missing rights. The following error will be shown.

Therefore use the following additional steps.

1. Right click the key in the left pane and select Permission (see).

2. Select on property page Permissions the group Administrators in Group- or user names.

3.  Check the Full control checkbox in column Allow (group Permissions for “Administrators” and click OK.

4. Then right click the registry keys mentioned above and delete them via context menu command Delete.

After deleting the two registry entries mentioned above, proceed another step and open Windows Explorer. Then navigate to folgender:

C:\Windows\Servicing\Packages

Delete the two .cat and .mum files named:

Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~*.*

via context menu command of via Delete button in Explorer’s menu bar. This requires administrative user rights.

Note the comment given below, mentions another key (probably in 64-bit-environments), if the fix given above doesn’t work.

After finishing the steps give above, try to check the system health using dism. As shown above, the system integrity check with dism shall be successful.

Similar articles:
Windows 10 V1703 Wiki
Check and repair Windows system files and component store
Windows 10 Creators Update Troubleshooting – part 1
Windows 10: Disk Cleanup is causing a Blue Screen
Windows 10 V1703: SuperFetch service fails


Advertising

This entry was posted in issue, Windows. Bookmark the permalink.

19 Responses to Windows 10 V1703: Fix for DISM error 0x800F081F

  1. Matthew Bott says:

    Thanks for writing about this error 0x800F081F, that I keep receiving. I now know it has nothing to do with .net 3.5 and really is about the Creators Update. I clean installed once from it and it seems to be there anyway on clean install. Ya, the new install.esd doesn’t seem to fix it for me either, nor component fixes, or anything from command lines. Hopefully there is a better fix than touching the registry about it, in the future, but thanks!

  2. William says:

    Hello sir. Thank you for posting this fix (in process of testing if it works or not). I was getting ready to start hunting down Microsoft employees for releasing this shoddy piece of crap of an operating system and not fixing this particular error THAT I HAD PERSONALLY REPORTED TO THEM A MONTH AGO. Yes, I spent 4 hours over 4 days convincing Microsoft tech support that this was an issue and finally got in touch with a engineer who captured all the log info and…..nothing. No fix, no word, just stagnation. Well, anyhow, I did want to bring up a…a difference…that I encountered when following your tutorial. I don’t know what the difference between your system and mine is, but the two registry keys that I found and deleted were [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0] and [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~0.0.0.0]

    The difference being that both of my registry entries have 0.0.0.0 for what appears to be a version number and one of my registry keys has “WOW64” in the name, while neither of your keys has them. Furthermore, when I went to C:\Windows\servicing\packages, there were 4 cat and mum files that had “Microsoft-Windows-TestRoot-and-FlightSigning” in the name. Two of them contained the “WOW64” previously mentioned. Anyway, so I deleted the two registry keys I had, and moved all 4 cat and mum files out of the folder and re-ran the scan. Still same issue. It appears not to have worked.

    • William says:

      I take that back. I didn’t delete the registry keys in “Packages” (there were two of them also, one with “WOW64”). When I did and re-ran it, it worked. If only Microsoft was as smart….

    • guenni says:

      Well, I tested it on a 32-Bit-VM – your machine was probably a 64-Bit-Install.

      BTW: I’ve escalated that issue after W10 V1703 release (as a MS Answers community moderator, I’m able to to that). Then I was last Wednesday in touch with Microsoft’s Product Group. I raised this issue – and it has been confirmed, that it’s a known issue and that MS developers work on it – but no solution yet.

    • Андрей says:

      For 64-bit systems, you need to delete 4 keys in the registry. 2 keys about which is written in the article, plus 2 exactly the same keys that contain the name WOW64. You also need to delete 4 .cat and .mum files. After that, DISM will work.

  3. Nems says:

    Thanks man for this fix, searched for hours before finding your site

  4. Terry Huckstep says:

    Brilliant, have been searching for a couple of weeks to fix this. I use win 10 64 bit and in the regedit just remove the WOW64 files as well and the same in in explorer. Worked perfect first time and now have my system faults repaired.

  5. Micky41 says:

    I am not the brightest bulb and I know how to get around in the registry and have look at the instructions but I am not sure as to what you have deleted. Is it just the 0.0.0.0 and nothing ells in both?

  6. Micky41 says:

    Is there any way for some one to do a step by step on how to make the correction, giving exactly what to delete. I need help badly.

  7. atnest says:

    Dears!
    After chat and remote control with support MS :

    Error: 0x800f081f
    DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\Sources\install.wim:1 /LimitAccess
    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0
    [===========================88.2%=================== ]
    Error: 0x800f081f

    The source files could not be found.
    ************
    I receive:
    This should be handled by our Professional support team
    5:19 pm
    I will provide you the direct number for the Pro support team.
    5:20 pm
    Here it is:
    1 800 936 4900
    5:20 pm
    J
    You have to call this number to be able to get this resolve.
    5:20 pm

    Just in case you need further assistance don’t hesitate to contact us again at www. answerdesk. com
    ******
    Gentlemen and who can call the United States and talk with technical services to solve the problem .. I am not fluent in English and there is no possibility. Can joint efforts solve the problem.
    Thanks

    • guenni says:

      Windows 10 Creators Update (Version 1703) fixes the problem.

      • atnest says:

        Dear Guenni!
        Very sorry,
        but Error: 0x800f081f DISM==
        is AFTER win 10 1703 build 15063.290 creator Update
        and DO not fixed….
        Help wanted!

        • guenni says:

          Try to use the fixes mentioned above to derive a working solution, that’s all I can suggest currently.

          Addendum: I just tested Version 1703 (Build 15063.296) worked without a flaw. I’m using a local account on this test machine so far.

  8. atnest says:

    dear Guenni !
    thanks for help.
    win 10 enterprise x64 is my os…

  9. Thanks it worked! Yet I wanted to know whether it will interfere with other updates and upgrades, and if it might come back because of updates or upgrades.

  10. Joker says:

    Hi i have same problem but on Windows 8.1
    Could i do this too or no???

  11. efoel says:

    Yes, it worked like a charm…..!! Thanks guys all

Leave a Reply

Your email address will not be published. Required fields are marked *