Windows 10 V1703: Fix for DISM error 0x800F081F

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.

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:


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:


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~~

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:


Delete the two .cat and .mum files named:


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.

Добавить комментарий

Ваш e-mail не будет опубликован. Обязательные поля помечены *

Post Navigation