Windows Enterprise Desktop

Apr 26 2017   10:25AM GMT

Build 15063 DISM Fix Available

Ed Tittel Ed Tittel Profile: Ed Tittel

Windows 10

If you’re running the Current Branch release for Windows 10 — namely, Build 15063 — you may have a DISM problem. Some tangible percentage of such installs will puke if you run DISM /checkhealth on the runtime image. But with a Build 15063 DISM fix available, you can repair this anomaly yourself. Here’s what the symptoms look like:

Build 15063 DISM Fix Available

SFC finds nothing amiss, but DISM erroneously thinks something’s off in the Component Store.</>

The key elements for these peculiar circumstances are:

  • SFC /scannow completes without a hitch
  • DISM /online /cleanup-image /checkhealth reports repairable component store issues
  • DISM … /restorehealth cannot fix those issues, no matter what /source you use (I’ve tried them all)
  • The DISM log file reports a variety of (mostly driver-related) files MIA as the cause of the errors

With a Build 15063 DISM Fix Available, What’s the Deal?

Warning! Some registry editing will be required, so prudence dictates you back up your registry before proceeding. But that editing simply involves deleting these two specific keys. First, reset permissions on each key to give Administrators full access before entering the delete command, or that command will fail.:

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

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

With those edits performed, the DISM problem will vanish. And while cleaning this up might seem like a bit of over-the-top OCD because it restores DISM to proper operation, it actually has real value. That’s because should the running Windows image actually need some kind of real repair, DISM will then be able to perform such tasks.

[Note: I’d like to give a shout-out to the relentless expert Win10 tweakers at, particularly user gommace from posts #39 and 40 in this thread: Creators update component store shows corruption but unable to repair. Be sure to read the whole thread to get a sense of potential gotchas that applying this fix could invite. Most of the more senior members of the forum are electing to wait for MS to fix this issue, as I am myself (except for the test system where I tried out this fix).]

2  Comments on this Post

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when other members comment.
  • userw6803
    Thanks for your article Ed.  A lot of us have this problem with DISM/ restorehealth "can't find source files".

    I notice though, that you and others are reluctant to try this fix on r other OS's except your test machines.  This raises a warning flag...huh?  I've been contemplating performing the fix..but I'm ambivalent about it.
    30 pointsBadges:
  • Ed Tittel

    Good observation! If you read through the whole thread at TenForums, it sounds like this is a Band-Aid. It simply turns off the part of DISM that checks the registry for build-related entries, which is what causes the problem to occur. That's well and good as long as nothing is amiss with the registry that DISM could and should fix. I've read lots of reports from people who've used it on production machines and have suffered no ill effects. If you're fixing your own machines you can do it with relative impunity. I would not recommend it for fixing other people's/user's machines as an IT service in the workplace, however.

    Thanks for bringing this up: I'm profound ambivalent about this fix, too.


    13,590 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

Share this item with your network: