Lt. Commander
Join Date: Dec 2007
Posts: 120
# 31
01-13-2010, 04:06 PM
I just disabled Windows Defender and the launcher ran flawlessly. This is on Windows 7 x64.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 32
01-13-2010, 04:07 PM
Well.. I have the process running.. in background.. errors.log says nothing..

In the applications Tab.. I only have MSN and Firefox.. in the processes tab.. I have the ghost STO.exe*32.. consuming CPU and RAM.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 33
01-13-2010, 04:18 PM
Update: Ticket: 4544685
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 34
01-13-2010, 05:47 PM
And another free bump...

100113 21:59:36 1 MasterControlProgram[1]: OLE failed to initialize: 80010106
100113 21:59:36 2 MasterControlProgram[1]: Shutting down from fatal error "OLE failed to initialize: 80010106"
100113 22:17:47 1 MasterControlProgram[1]: OLE failed to initialize: 80010106
100113 22:17:47 2 MasterControlProgram[1]: Shutting down from fatal error "OLE failed to initialize: 80010106"
100113 22:22:35 1 MasterControlProgram[1]: OLE failed to initialize: 80010106
100113 22:22:35 2 MasterControlProgram[1]: Shutting down from fatal error "OLE failed to initialize: 80010106"
100113 22:22:41 1 MasterControlProgram[1]: OLE failed to initialize: 80010106
100113 22:22:41 2 MasterControlProgram[1]: Shutting down from fatal error "OLE failed to initialize: 80010106"
100113 22:22:57 1 MasterControlProgram[1]: OLE failed to initialize: 80010106
100113 22:22:57 2 MasterControlProgram[1]: Shutting down from fatal error "OLE failed to initialize: 80010106"
100113 22:35:33 1 MasterControlProgram[1]: OLE failed to initialize: 80010106
100113 22:35:33 2 MasterControlProgram[1]: Shutting down from fatal error "OLE failed to initialize: 80010106"
100113 22:38:15 1 MasterControlProgram[1]: OLE failed to initialize: 80010106
100113 22:38:15 2 MasterControlProgram[1]: Shutting down from fatal error "OLE failed to initialize: 80010106"
100113 22:38:24 1 MasterControlProgram[1]: OLE failed to initialize: 80010106
100113 22:38:24 2 MasterControlProgram[1]: Shutting down from fatal error "OLE failed to initialize: 80010106"
100113 22:38:28 1 MasterControlProgram[1]: OLE failed to initialize: 80010106
100113 22:38:28 2 MasterControlProgram[1]: Shutting down from fatal error "OLE failed to initialize: 80010106"
100113 22:38:44 1 MasterControlProgram[1]: OLE failed to initialize: 80010106
100113 22:38:44 2 MasterControlProgram[1]: Shutting down from fatal error "OLE failed to initialize: 80010106"
100113 22:54:32 1 MasterControlProgram[1]: OLE failed to initialize: 80010106
100113 22:54:32 2 MasterControlProgram[1]: Shutting down from fatal error "OLE failed to initialize: 80010106"
100113 22:54:39 1 MasterControlProgram[1]: OLE failed to initialize: 80010106
100113 22:54:39 2 MasterControlProgram[1]: Shutting down from fatal error "OLE failed to initialize: 80010106"
100113 23:13:55 1 MasterControlProgram[1]: OLE failed to initialize: 80010106
100113 23:13:55 2 MasterControlProgram[1]: Shutting down from fatal error "OLE failed to initialize: 80010106"
100114 00:43:33 1 MasterControlProgram[1]: OLE failed to initialize: 80010106
100114 00:43:33 2 MasterControlProgram[1]: Shutting down from fatal error "OLE failed to initialize: 80010106"
100114 00:43:56 1 MasterControlProgram[1]: OLE failed to initialize: 80010106
100114 00:43:56 2 MasterControlProgram[1]: Shutting down from fatal error "OLE failed to initialize: 80010106"
100114 00:44:02 1 MasterControlProgram[1]: OLE failed to initialize: 80010106
100114 00:44:02 2 MasterControlProgram[1]: Shutting down from fatal error "OLE failed to initialize: 80010106"
100114 00:44:11 1 MasterControlProgram[1]: OLE failed to initialize: 80010106
100114 00:44:11 2 MasterControlProgram[1]: Shutting down from fatal error "OLE failed to initialize: 80010106"

Error Ticket ID: 4544685
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 35
01-13-2010, 06:58 PM
Im having the same issue. heres my crash log if it helps.


100112 11:07:28 1 MasterControlProgram[1]: Shutting down: C:\src\Core\CrypticLauncher\patcher.c(103)
100112 23:44:43 1 MasterControlProgram[1]: Shutting down: C:\src\Core\CrypticLauncher\patcher.c(103)
100112 23:54:04 1 MasterControlProgram[1]: Shutting down: C:\src\Core\CrypticLauncher\patcher.c(103)
100113 13:12:31 1 MasterControlProgram[1]: Shutting down: C:\src\Core\CrypticLauncher\patcher.c(103)
100113 13:18:12 1 MasterControlProgram[1]: Shutting down: C:\src\Core\CrypticLauncher\patcher.c(103)
100113 22:14:36 1 MasterControlProgram[1]: Shutting down: C:\src\Core\CrypticLauncher\patcher.c(103)
100113 23:02:44 1 MasterControlProgram[1]: Shutting down: C:\src\Core\CrypticLauncher\patcher.c(103)
100114 01:34:18 1 MasterControlProgram[1]: Shutting down: C:\src\Core\CrypticLauncher\patcher.c(103)
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 36
01-13-2010, 07:17 PM
I redownloaded another client.. just a stupid question..

Instalation space = 1.4GB ? Is this correct ?
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 37
01-13-2010, 07:30 PM
Have you tried disabling Windows Defender as I suggested?
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 38
01-13-2010, 07:37 PM
Quote:
Originally Posted by sa_clavicle
Have you tried disabling Windows Defender as I suggested?
Yes.. I have no type of FW active... Either Windows or any other brand..
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 39
01-13-2010, 09:55 PM
The problem is NOT on the players end. It's the stupid launcher and how its programmed.

It uses some IE browser like scheme that hits their server and loads components from cryptic's server. This problem has been existing since Champions and Cryptic has never bothered to fix it. They've been ignoring the launcher problem forever and focusing on game code.

I wish they would get a new programmer and rewrite their 'patching' scheme.

I've had this launcher problem since closed beta last week ever since i got into CB with fileplanet key. The support here is terrible because they offer no help. They don't have a "Support Troubleshoot" page that says if you're having these problems, here are the solutions. You get forum replies that are all one liners that aren't very helpful.

How did I solve the launcher problem?? I really didnt. For a while, I thought the problem was my computer, so I thought maybe I'm missing a driver or my drivers are not up to date. Let's just say the really "SCREWED ME OVER HARD". I went to update windows from MS updates site. I thought maybe .NET updates. I select a bunch of those. I noticed my Nvidia needs updating as MS suggested that I need new Nvidia drivers for my mother boards built up network card and graphics. Well. It prompted me some errors during the update. Then I restart my computer and no internet. I can't get access to the internet WTF. so the I check the device manager and I get yellow ! on the network card. Crap. I can't even roll back to previous drivers. So Now I had to get replacement drivers from another computer off my house mate that had internet access. installed it rebooted, and then my entire systems32 folder is hosed. Windows won't even start!! Crashes over and over. Can't even get safe mode or the best working config. Just completed hosed! tried to repair from the windows CDROM and that didnt work either. Long story short- I had to REINSTALL my entire windows on a new boot harddrive. Fresh installation of windows XP with no stupid updates worked.

So now I install StarTrek on that and it worked. If you want startrek to work- my answer to you is buy a new computer with a new install or buy a new harddrive and reinstall your entire computer as a new duel boot. Until Cryptic decides to fix it. As there is enough people having this launcher problem with NO real trouble shooting or actual solution. Apparently nobody knows how to fix it. I've seached all the Champions forum and there were NO SOLUTIONS.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 40
01-13-2010, 10:14 PM
I was able to get it working after removing some older programs off my system and the going to an older chipset and updating back to the newest ones. What fixed it, not sure, but was probably something with the chipset drivers that was causing my issue.
Closed Thread

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


All times are GMT -7. The time now is 05:52 AM.