Windows 10: DISM, unexpected behavior

Thank-you, for the information. Here is what happened:

When I went to look for "secure boot" settings, I noticed that the boot order got changed back from the way I saved it (?). I changed it back again and tried. Upon boot, first I had to choose a keyboard layout, 2nd I chose ""Use USB device", 3rd, there was only a choice of "EFI USB" or Internal drive. I'm not sure what EFI is, but if I choose internal, of course, it will do a normal boot. If I choose EFI USB, it starts all over at keyboard layout and just keeps repeating. Disable "secure boot" had no effect.

Since this is different behavior than before, I did not try a different port yet, until I check with you all first.

Thanks.

 

The EFI USB choice suggests that you may not have formatted the USB device correctly in order to use it as a boot device. Make sure it is formatted with fat32.

 

Yes, I formatted with Fat32. Since I hadn't tried the other port as suggested above, I wiped the flash drive and started over with the other port, but no change.

In Control Panel, Windows 10 can create a Windows 7 boot disk. Would DISM work from a Windows 7 boot disk?

 

Although the option to 'create a system repair disk' is found in 'Back up and Restore (Windows 7)' it is NOT a Windows 7 boot disk. It's the same Windows 10 recovery tools as the USB recovery drive - just without the option to 'include system files'. Yes, it will work just the same as booting from USB.

 

Yesterday when I ran dism restorehealth it worked for Windows 10 version 1703 build 15063.296.
See if the sfc /scannow and/or dism /online-cleanup-image /restorehealth commands can fix your operating system.

dism restorehealth now working for windows version 1703 - Windows 10 Forums

 

Bree: Thanks.

zbook: Thanks, but we already went through using those commands and sfc. (see previous posts).

 

Yes, so had I (many times) - DISM always failed on 'source not found'. The last time it failed on me was yesterday, with the logs showing a failure to download a package that was required for the repair. Today it worked perfectly, finding and downloading the required packages.

Seem that Microsoft have updated something at their download server that makes it work, because I certainly didn't change anything at my end. @ray5450 it's worth trying it one more time.

 

Are you saying then that if I redownload the iso using the Microsoft Windows Media Creation Tool, that it should work now?

 

No @ray5450. I'm saying the problem isn't at your end. Nothing had change on my 10063.296 system, but the DISM command that failed on the 19th May worked on 20th May. There's no point in downloading a new .iso as it hasn't been changed. The fix was applied by Microsoft to the download servers that provide DISM with the repair packages, not to our Windows installations.

see this post: Creators update component store shows corruption but unable to repair

 

So, you are only talking about when NOT using the limitaccess option?

 

That's the way I understand the fix - new test-flight-signing files / or new hashes are downloaded - I guess those in the iso/component store have the incorrect hash...