Need advice re DISM

Win 10 pro 1703/15063.250
32 bit pc
I am following Shaun Brink's excellent and exhaustive tutorial, "Use DISM to Repair Windows 10 Image." I have the ISO on a disc and the file D:\Sources\Install.esd is available. Here's a copy of the Cmd results:

c:\Users\Bob\Desktop>Dism /Online /CleanupImage/RestoreHealth/Source:esd:D:\Sources\Install.esd:1 /limitaccessDeployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0[===========================88.4%=================== ]Error: 0x800f081fThe 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 MSN.com - Hotmail, Outlook, Skype, Bing, Latest News, Photos Videos DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

What went wrong?

I've used the same command previously when my ISO had an install.wim file and it worked fine.

Doesn't work with 1703. Hidden FlightSigning packages seem to be the culprit.

Any workarounds?

tcebob said:

Any workarounds?

Some, but you need to go into the registry. There's a (very) lengthy thread on this.
Creators update component store shows corruption but unable to repair

DISM is known to work in 1703 with an offline repair..

Code:

 DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:ESD:D:\x64\sources\install.esd:2 /ScratchDir:C:\Scratch

Use DISM to Repair Windows 10 Image

...so I'm not unduly concerned. Rather than mess with the registry I'll wait fo MS to issue a fix.

I'll take a peep at the registry and try the offline repair. Then I'll take my place in line to wait for MS.

Here is the fix for the DISM error 0x800F081F in Windows 10 v1703

Windows 10 V1703: Fix for DISM error 0x800F081F | Borns Tech and Windows World

jpeni said:

Here is the fix for the DISM error 0x800F081F in Windows 10 v1703

Windows 10 V1703: Fix for DISM error 0x800F081F | Borns Tech and Windows World

Why does no one ever read that blog carefully? If you look at where they say the fix came from you'd realise they freely admit they got the fix from TenForums