Today when I tried to start Star Trek Online up, the Cryptic Launcher Auto Updater gave me this message, "Patcher Error: The patchclient got a message while it was in a state with no response function." I click the OK button on the message box and then the whole thing closes. I didn't even recieve an error id number, nothing. I didn't even get into the Star Trek Online Launcher itself either, it was just the Cryptic Launcher Auto Update but that closed once I hit the OK button on the Patcher Error Message Box. Help please thanks.

Could somebody respond to this as soon as possible please? I tried doing a system restore because I though that my use of the program TweekMaster was the problem. So I tried a system restore to restore my orignal network parameters, but after restarting the computer said that nothing was changed and that there was an unspeficied error during system restore.

K....Now I know I'm not crazy....I have the exact same issue. Submitted an Error report using the crypticerror application that is in the STO folder, but I don't have a clue what to do.

i got an error too. could someone please let me know what's going on. but good to know i'm not the only one.

You and me both. I just hope some Dev or some more people see this thread and do something about this. Otherwise I'm not going to be able to get into the launcher. And it's driving me crazy.

I'm getting the same error. What's weird is that the launcher was working perfectly fine earlier today.

Currently experiencing the same issue.

I've got that too! and try to restart the program itselft, please resolve it quickly. it's annoying.

Good to know I'm not the only one. I thought it was only me so I did a system restore, but no it wasn't just me. But argh this is bad.

Alright Captains....

Let's collect information here...

I'm using a Virgin Mobile Broadband device - never had a prob before
My antivirus is AVG - just updated
checked the exceptions list in my firewall and STO is listed.
I've got a laptop - same one I've used since launch.

At the very least we can find out if there's something we have in common that could be causing the issue....so.....anybody have anything to add?