Ironically, the DISM that you posted won't work, as it has to be /online /cleanup-image /restorehealth. I had been running dism properly, as shown by the lengthy log, with the failures being shown at the end of each session in the log. In addition, earlier today, I tried at least of two the dism options in the ResetWUENG.cmd script, which failed for reasons other than when trying the code in this paragraph.
Before I did that, I ran Option 2, "Resets the Windows Update Components." That did all sorts of things, one of which I wish it had done, namely remove the block I had on the KB, so that Windows Update would keep giving more problems.
Just before posting this, I managed to delete everything in the Software Distribution folder, which, has become the normal, was not easy. The first problem was that something could not be deleted as it was active in one of the services (name already forgotten,) which would not complete the stop process, so I had to reboot to get that done. Then another service had to be stopped, and a third, but now the folder is empty, and the KB block has been reestablished.
I then once more ran the Windows Update troubleshooter, which had at least once or twice cleaned up the database, but was failing to do so the last few times I tried; it is now restored.
Given that dism.exe will not work, I am loathe to try updating yet again. This is based entirely on my complete lack of knowledge or information as to why it won't work, and, thus, what might be wrong with Windows 10, things that might still prevent a successful update.
I have a Macrium Reflect full backup which was created the Monday before the KB was issued, and I have a System Restore Point dated 07Dec2017. 9 (There are a few later ones, that apparently were created on 12Dec when I first tried to update, and on 12DEc and 15Dec for "Windows Module Installer," whatever that means.
In sum, I seem to have three possible ways of fixing this before applying drastic measures. Oh, hold on, I just scrolled up and saw that you suggested trying a repair install again. I don't see how, even if it were to fail, that it could make matters worse, so I will do that after finding and restarting the services I had to stop as they might interfere with the ISO attempt.
However, as the adage has it in my version, "Multiple times bitten, multiple times shy," so before I do anything about the KB problem, I am once again going to wait for advice; as far as I have seen since the KB fiasco started, everything else is working correctly, although I've not tried many programs, so waiting is not likely to cause any further consternation.
===
A few minutes later: There are no services stopped, but the Software Distribution folder, that I fought with to empty is now again full. I suspect that that was caused by my running the Windows Update troubleshooter to fix the database. If so, I am apparently stuck in a moebius strip conundrum.
===
Continuing My Flailing
Two other possibilities:
1. I have the KB downloaded directly from MS, and wonder what might happen were I to run it; any ideas?
2. Having had my weekly Macrium Reflect full-disk backup fail twice on the Monday after the KB release, I started a support ticket, which eventuated in a link to a Macrium troubleshooting procedure. I finally got to that yesterday, only to find that it is for version 4 and 5/6, while I have 7. I am waiting for a reply to my question as to how to proceed. I wonder if, once I run the procedure, which I am fairly certain creates a log, and were I to submit it to Macrium, if they might see something on my computer that not only caused the backup failures but might also be related to the update failures. Perhaps it would be a good idea for me to wait for this to take place before I try any of my other techniques as listed above in this conglomerated what ever it is?