As of Sunday or so... there was a patch that I played and then now can't play anymore. Whenever I open the client I log in, and it goes to the next patcher screen and stops. There's no Engage button, there's no options at the top to change, no patch notes... nothing.
I re-installed from the disc and can't patch it up. What I've tried is:
- Restarting... nothing.
- Re-installing... nothing.
- Removed Router... nothing.
- Checked drivers and updated where possible... nothing.
- Run as administrator... nothing.
- Run in XP compatibility mode... nothing.
- Turned off Firewall... nothing.
- Excepted the programs (GameClient and Star Trek Online.exe) in Anti-Virus... nothing
I'm stuck here. Would love some help. I'm running the following:
- Dual Core 3.0ghz
- Windows 7 Home Premium
- 3.0GB RAM
- Cable Modem (RCA) Through Comcast ISP
- Nvidia 9800gtx+ 1GB
This is how my client looks:
Image Link
Comments
My release notes are missing on both clients too. I'm not able to view them. Clicking on the banners like the C-Store announcement on the STO client brings me to the STO website and the correct page.
I did run the nettest.exe tool and it connected fine (no timing out).
this is the crash report
100130 04:15:32 1 MasterControlProgram[1]: Shutting down: C:\src\Core\CrypticLauncher\patcher.c(103)
100205 20:11:29 1 MasterControlProgram[1]: Shutting down: C:\src\Core\CrypticLauncher\patcher.c(104)
100408 05:28:14 1 MasterControlProgram[1]: Shutting down: C:\src\Core\CrypticLauncher\patcher.c(105)
Does your client look like mine?
I was able to visit that site, did the nettest, and a tracert to the patch server. For some reason it wouldn't work. I was forced to re-install the game twice and that still didn't work. I ended up re-installing Windows 7 and was finally able to get it to work.
I haven't downloaded or installed anything that should have affected this. It happened after I patched the last time which it seems like there's a lot of connection problems after that as well. I don't know what to make of this. Be nice if someone had a solution for me next time that didn't mean wiping my harddrive.