Unable to connect (error 99/RSA Key error)

[BruceFeuillette]

Hello !
I'm running TV 9.0.31064 on Windows 7 x86. Everything was fine until some weeks.
Tv refuses to connect... Even on the 12345 test server.
Here's the log

2014/09/06 17:28:28.934  2552  1120 G1   Trying connection to XXXXXXXX, mode = 1
2014/09/06 17:28:28.934  2552  6132 G1   CLogin::run()
2014/09/06 17:28:28.987   384  5424 S0   CT14 CT.Send.CMD_MASTERCOMMAND_ENCRYPTED From=XXXXXXXX To=0 L=392
2014/09/06 17:28:29.053   384  5424 S0   CT14 CT.Receive.CMD_MASTERRESPONSE_ENCRYPTED From=0 To=XXXXXXXX L=520
2014/09/06 17:28:29.054   384  5424 S0!! Encryption.RSADecrypt exception: RSA/EME-PKCS1-v1_5: invalid ciphertext
2014/09/06 17:28:29.054   384  5424 S0!! SendMasterCommand: DecryptAndVerifySign() failed!
2014/09/06 17:28:29.054   384  5424 S0   CT14 CT.Disconnect
2014/09/06 17:28:29.055   384  5424 S0!! MC.RR.XXXXXXXX ErrorCode: 99
2014/09/06 17:28:29.055   384  5424 S0!  CT.ConnectTeamViewer.ConnError.
2014/09/06 17:28:29.055   384  5424 S0   CT13 CT.Disconnect
2014/09/06 17:28:29.056  2552  6132 G1   CLogin::run() leave

It seems that there's an error with the RSA key... Do anybody know how to solve it ?

Thanks !

[BruceFeuillette]

Problem solved.
I don't know how and when. It works like a charm tonight.
My ID has changed, it's the only visible thing.

[matt]

ID should be specific to hardware, and shouldn't change.

Was this restored from another computer, or is it a virtual machine, or perhaps accessed remotely via Remote Desktop. These are the things that would normally cause an ID change for TV. (Remote desktop will normally have 2 IDs, one for the concole, and another for a client session. Restored or cloned VMs will often have the original ID that needs to be reset when on new hardware)

[BruceFeuillette]

TV staff send me a registry file today to change the ID. But it wasn't usefull after yesterday change.
I don't know why the ID changed. Nothing has been modified on my computer, neither accesses from outside.
It was just different at boot.

[Admin]

maybe a driver update???

[matt]

Just realised too that a recent Windows security update plays with the file system encryption, and that many users are having trouble install any MSI since the update.

If the problem persists, try removing this update from your computer
http://support.microsoft.com/kb/2918614

The error you received is VERY similar to the errors received when trying (and failing) to install an MSI on an affected machine.