UPDATE: @ZOS_Kevin, @ZOS_BillE

While I was following the first Troubleshooting protocol, I downloaded the Windows 7 patch for the TLS 1.1 and TLS 1.2 secure protocols issue as a .MSU file, which is "Method 2" on the download page for it. When I ran it, the OS refused to install the Windows Update because it was already installed, as shown in the second screenshot in this post, below.

Aside from that, the download page referenced above has the text: "Note The hotfix installer doesn't add the DefaultSecureProtocols value. The administrator must manually add the entry after determining the override protocols. Or, you can install the "Easy fix" to add the entry automatically."

So, after reading your report in Message 72 in the General Discussion thread, I downloaded the "Easy Fix". When I ran it, there was no output except to notify me that it had finished.

Now, apparently Launcher runs as it should, but I still launch the game client with a desktop shortcut. Thank-you for your attention, time and effort to resolve this issue.

____________________

For your information, I am submitting a ticket to Customer Support about the subject, and I will include the URL for this message in the ticket so that they can view the screenshots which are embedded in this post.

To be brief, I replaced the worn SSD on which TESO was installed with a new Sony 870 EVO SSD, and prepared it for use. Then I re-installed TESO on the new one and bought the Blackwood chapter. Since then, I have not had any problem with (a) using a desktop shortcut to run the game client and (b) playing the game, that I did not have before.

However, eventually I must run Launcher either to update the game client or to use the Repair Files option after the game client crashes. But Launcher does not run as it did before I re-installed the game, and I do not know what went wrong -- with respect to the Launcher -- when I did that.

(1) The first screenshot shows the Error 210 dialog on the Launcher output display screen, after I ran it by using a desktop shortcut. Note: the Properties of the Launcher shortcut include Compatibility with Windows 7 Service Pack 3 and Administrator privileges. (It had the same Properties prior to re-installation of TESO.)



(2) The second screenshot confirms that support for TLS 1.0 and TLS 2.0 are installed on my computer system.



(3) The third screenshot shows the Microsoft C++ Redistributable packages which are installed on my computer.



(4) The fourth screenshot shows the Microsoft C++ Redistributable files which Install_ESO.exe downloaded and stored in the Launcher folder.



(5) The fifth screenshot shows the Launcher display after I downloaded the Patch Manifest file and stored it in the folder \Program Files\The Elder Scrolls\Launcher\ProgramData



(6) The sixth screenshot shows the Launcher display after I deleted the folder \Program Files\The Elder Scrolls\Launcher\ProgramData (as instructed by ZOS Support)



When Launcher runs now, note that its display does not include any window controls. The only way that I can close the window is to run Process Explorer (which takes the place of the previous Task Manager) to kill the Bethesda_launcher process.

Again, I completed all of the Basic Troubleshooting and the Advanced Troubleshooting protocols, as instructed by ZOS support, and the sixth image above is the ultimate outcome. Somewhere between the fifth screenshot and the sixth one, Launcher fails to work as it is apparently believed to work by the person who wrote the Advanced Troubleshooting protocol -- which is probably outdated in some respect(s).

For what it is worth, various details in all of the ZOS Support instructions, such as the storage folder location of the 64-bit game client, are outdated. The entire series should be carefully reviewed and corrected as needed.

Also, the forum software editor interprets any string that consists of the letter D followed by a colon as an emoticon not as a Windows NTFS storage drive.

POSTSCRIPT: I have read the discussion in which @ZOS_Kevin requested a copy of the "Host File". However, I could not attach a copy of the file host.developer.LOG to the online Support Ticket because it will not accept files which have that filename extension. (By the way, it also will not accept a file that does not have any extension to the filename.) So, I have sent that file to him via private message.