This is the post on Reddit that the eagle-eyed @s0urce spotted and that gave the clue that MS had finally fixed it at the server end. @s0urce was the first one to report this here on TenForums.
https://www.reddit.com/r/Windows10/c...e_out/dhs1qp9/
My guess would be the servers didn't have a copy of the .mum file that apparently has errors on the .wim or .esd. Once they repair the .mum it no longer looks for it again unless that .mum shows up bad again on the next install or re-install.
Hi,
@EdTittel & @f14tomcat et al, I had it working on one machine that was not on the net for a few weeks prior to installing the KB.
So, yes, it seems MS cleared the mismatch on their side without further notification to end users.
I could dl that KB again and see what it actually does but I doubt it's worth the trouble though.
Cheers,
My Desktop PC failed to boot 36 hours ago after a cumulative update, with no ability to boot to any windows environment.
...so it's been 'offline DISM' hell for the last 4 hours or so.
After trying SFC and not being able to save the logs as being in Windows PE mode (wtf....surely that's when you need logs most), and then battling all day with DISM, with offline images, and finally reading this forum post from start to finish and still getting the 0x800f081f error.
I'm having to work in offline mode via a boot using the SHIFT-F10 from an Install Image (10.0.15063.0) I downloaded yesterday morning, and I'm still getting to around 88% before hitting the error.
I guess that MS have not propagated the fix to their MediaCreationTool, and therefore it's still an old DISM. (Although it says Image Version 10.0.15063.0).
Any idea how long it takes MS to get a new Install Image and DISM tool via MediaCreationTool ?
Sorry to hear you have been to hell and back. The problem with DISM online in 1703 that's been fixed recently has nothing to do with the .iso made by the Media Creation Tool. It had been shown that, before the problem was fixed, running DISM's RestoreHealth offline as you have done was the only way that was known to work without error.
Use DISM to Repair Windows 10 Image - Post #400Here is how DISM offline repair looks...
Not what you want to hear, I know. But it looks like your problem is not in the ,iso you downloaded. Compare your command line with that use in the post I linked to. In particular, look to see if you are using the correct index number - it's '2' for Home...
...Pro would use "...install.esd:1"
Thanks Bree
I'm a bit at a loss now...
I'm running:
DISM /Image:E:\ /Cleanup-Image /RestoreHealth /Source:ESD:H:/Sources\Install.esd:1 /ScratchDir:E:Scratch /LimitAccess
also tried:
DISM /Image:E:\ /Cleanup-Image /RestoreHealth /Source:WIM:H:/Sources\Install.wim:1 /ScratchDir:E:Scratch /LimitAccess
I've go both ESD and WIM versions in that location, and both go through the cmd-progress%-bar.
Getting to 88.1% and then still getting the 0x800f081f error.
I've now also tried to remove the 'FlightSigning' registry items, and files as per:
Windows 10 V1703: Fix for DISM error 0x800F081F | Borns Tech and Windows World
but not getting any further.
Well, you've come to the right place, did you spot that the article in your link credits a TenForums post (describing it as 'this english forum thread') for that fix? Or perhaps that's why you've come here :)
It may be worthwhile starting a new thread for your problem as I'm not convinced SFC/DISM is the most appropriate repair approach. Give as many details as you can of any error messages at boot, others may recognise the symptoms and have further suggestions. Also, fill in you system details here: https://www.tenforums.com/profile.php?do=extra as these may be relevant to your problems. I would have thought the most important task would be to make it able to boot into Windows first.
Run Startup Repair in Windows 10
Then perhaps an in-place repair install.
Repair Install Windows 10 with an In-place Upgrade
You need to run RestoreHealth within your booted windows while connected online to replace the error .mum file.
Path is wrong to Scratch, plus you manually need to make directory folder \Scratch
DISM /Image:E:\ /Cleanup-Image /RestoreHealth /Source:WIM:H:\Sources\Install.wim:1 /ScratchDir:E:\Scratch /LimitAccess
Yeah, probably... this came from a 0xc000021a error.
Machine will not boot, nor into any safemode.
Tried that... didn't work either.
Nothing from the Advanced Options recovery menu worked so far...
Hence the SFC and DISM route... and having to do it from PE in offline mode.
I was really trying to avoid that... but it's pretty much my last option.
Many thanks for the assistance so far (now and in the entire thread).
Quote