I solved the problem last week, and thought I'd explain how so that others, it having the same problem, can try what I did.

It turns out that the BCD Template in C:\Windows\System32\Config folder was 
corrupt, but I didn't find this out until after using diskpart to first try 
and fix what I though was a corrupted UEFI partition.

But first, when I got home today, removed the suspect SSD, and connected 
the SSD to a USB IDE & SATA external adapter ot my desktop.  The SSD didn't 
show up in Windows File Explorer, and when I launched Disk Management, Disk 
Management said "Connecting to Virtual Disk Service forever.  I had to 
CTRL-Alt-Del out.  As soon as I disconnected the external adapter, Disk 
Management found all other drives.  But because I was able to log on to the 
SSD using the Media Creation Tool USB boot stick, and read the C: drive, I 
still thought that the SSD was not dead, but the UEFI was corrupted, and 
hoped that if I could fix it, I could boot the OS successfully.

I used a USB boot stick to get to Troubleshooting>Command Prompt.  Once 
there, I used diskpart>list disk>list vol to find the FAT32 partition which 
held the boot manager.  It had no volume letter, so I assigned it letter=V.

I exited diskpart, and a dir of V: showed and EFI folder, but there was no 
Microsoft folder within.  No luck so far.  I thought I was getting somewhere.

Nonetheless, I logged back on to C:\ and issued command that I would have 
issued if there was a Microsoft folder:

C:\>bcdboot C:Windows /s v: /f UEFI

I got the message, "BFSVC Error: Could not open the BCD template store. 
Status = [000000f]".

I logged back to the Media Creation Tool drive, X:, and issued:

X:\sources>xcopy x:\windows\system32\config\BCD-Template c:\windows
\system32\config\BCD-Template

Overwrite all? yes

I did a dir on the EFI folder, and now there was a Microsoft folder, and 
within was a Boot and Recovery directory.

Within the Boot directory was a BCD file.

While in v:\EFI\Microsoft\Boot>bcdedit showed the bcd configuration.  
Encouraging.

I closed the command prompt, and was returned to the the Windows Recovery 
Console, and I choose "Continue, Exit and continue to Windows 10".

The machine presented me with the Windows logon screen, and all was fine.