TLS Authentication Error When Starting d7x
Originally on Friday the 13th (updated)
Affected: d7x PC Technician’s software. No other products or services are affected.
TLS authentication with the server is not functioning properly. The failures result in TLS authentication errors when starting d7x, and you may be prompted to change your login credentials. Please do not do that (just close/cancel!) Also, a fresh download of d7x will fail to activate, and working copies may possibly have failures in Config Mgmt Portal and in checking for updates.
WORKAROUND: Get the latest d7x from the manual; download the blank config version, all you need from this is the new d7x EXE file. Delete your existing d7x vX.X.X.X.exe file, and copy over the new d7x EXE file from the download, running that instead. The latest d7x versions have TLS authentication disabled for server access.
NOTE: If the workaround fails, then you have another older affected copy of d7x running, having been launched by the new d7x when it reads session data from the registry. This happens when running multiple copies of d7x on a PC from different locations. In this event you should close d7x and delete the registry value “AppEXE” located in: HKLM\Software\d7xTech\d7x\Session\Paths and do the same for the \Session\Paths located in HKLM\Software\Foolish IT\d7x and \d7II (if either exist) and then restart the new d7x.
If using the d7xRDT it should just work now without doing this, unless d7x has already been run on that system, then you’ll need to follow the same workaround as described above including the NOTE.
If you are not yet affected, it is strongly recommended to update to v184.108.40.206 (or later); choose Check for Updates from the Main drop down menu in d7x, or you may follow the workaround as described above including the NOTE.