Win 10 1703; How to fix broken DISM and hence Windows Update?

For Ccleaner > un-check:
memory dumps
windows log files
windows error reporting
windows event logs


For startup and recovery > system failure > un-check
automatically restart

zbook said:

For Ccleaner > un-check:
memory dumps
windows log files
windows error reporting
windows event logs

Done, but are you asking me to clean the remaining items?

For startup and recovery > system failure > un-check
automatically restart

Done.

When the computer crashes it generates files that are useful for troubleshooting the crash.
The checked settings had files that were being cleaned.
When there is a BSOD crash there is a window that can be viewed where it displays the bugcheck.
Sometime it may display the misbehaving driver in the form *.sys
The automatically restart was un-checked so that you now have time to view this information.
Ccleaner already has the files ready to be cleaned.
So Ccleaner needs to be closed and re-opened before any cleaning is performed

If the KB updates leads to an upgrade the DISM problems should be fixed.
Usually in place upgrade repairs fix problems in the operating system.
So it is likely the DISM problem is a deeper problem in the registry.
See what happens with the KB updates.

Having the computer produce a dump is useful as problematic drivers prevent upgrades and if the problematic drivers produce crashes and dumps they can be identified and replaced.

If the DISM problem is not fixed the computer can be troubleshooted to improve the likely of success in an upgrade. At the same time the logs can be troubleshooted (Panther, DISM, CBS, etc.)

zbook said:

If the KB updates leads to an upgrade the DISM problems should be fixed.
Usually in place upgrade repairs fix problems in the operating system.
So it is likely the DISM problem is a deeper problem in the registry.

Yup, that's what I'm thinking.

See what happens with the KB updates.

From the MS Support page for the key update: "To install this update, you must have Windows 10 Version 1709 installed."

Having the computer produce a dump is useful as problematic drivers prevent upgrades and if the problematic drivers produce crashes and dumps they can be identified and replaced.

If the DISM problem is not fixed the computer can be troubleshooted to improve the likely of success in an upgrade. At the same time the logs can be troubleshooted (Panther, DISM, CBS, etc.)

Ok, but I don't know how.

Download and install Whocrashed.
http://www.resplendence.com/whocrashed
Above analyze click on tools > crash dump test > type: ACCEPT
Click analyze
Post the whocrashed report into the thread using a one drive or drop box share link.
Run this version of the log collector and post a new zip into the thread:
log collector v2-beta08.zip

Earlier this month the logs have information that a crash occurred but there was no BSOD mini dump file generated.
The above test is to see if the computer environment will create BSOD dumps.

Have you noticed any hangs, freezings, black, red, or blue screens, unexpected restarts or shut downs?

No hangups, BSOD, or unexpected start or stop. It's nice to know about the whocrashed utility, but there is no memory.dmp in my Windows directory and the minidmp subdirectory is empty (EDIT -as you suggest). I'm gonna assume that I simply have a fault in the DISM component.

As you mentioned somewhere above, I have a legacy AMD video card. From my reading, it may be contributing to the issue in the sense that the MS upgrades to the Creators' editions didn't provide for it. I think at this point I'll beg off the diagnostics. I will make a disc image, and then try an offline DISM fix, ie. from the PE environment, as suggested, for example, here: How to use DISM in WINDOW PE environment? Will report if it works. If it doesn't work, well.... 1703 can suffice til I move my butt and build my planned new system.

Thank you for the assistance and advice. -Ron