@swansojb Apparently my problem is/was a little different. The Computer which was "hanging" on updates I was dealing with "hung" on a pair of updates. The 1st one was the one released prior to the one that prompts this thread. Both updates, no matter
what process I went through, including all of your recommendations, was able to get a "completed install" on my system. It is an "ancient" Acer Z3731-UR21P manufactured very shortly after Windows 7 (X64) was released. It has an Intel dual-core Pentium E6700
and 4gb of RAM and an Intel Graphics chipset that uses an area in that RAM.
I ended up "chatting" with Microsoft Support and got a tech to link to me to check things out. He ended up trashing a huge volume of "Log" files that had accumulated on the 1TB disk I had spinning. He also performed the same rituals I had already tried
twice. In his final swath through the machine after he convinced himself that Microsoft Update on this machine had something "weird" going on, he disabled the history of updates on the machine, so my Check for Updates screen no longer displays any entries.
The system spec screen shows 1709 with 1629.125 as the version.
The available downloadable installers, at least in my case, did not "cure" the symptoms, but hopefully a subsequent release will bring back the update history and proceed onward. It was "current" as of about 1/24/2018. The original install / reboot sequence
was "working" by the updates apparently in my case "did not register" at the end of the reboot cycle in a way that the module that does the updating could see that the update was there! I used a .DLL described in this thread from the console to pull a list
of the installed updates and even though the display in "Settings" does not show them, THEY ARE ON THE SYSTEM