Beruflich Dokumente
Kultur Dokumente
The problem below -- Launcher Doesn't Appear -- will often mean that the launche
r is running, but frozen. If you try to run the launcher a second time, you will
receive an error message about how only one instance of the launcher can be run
at a time. You'll want to open Task Manager (hit Control-Alt-Delete and pick Ta
sk Manager from the options), and then select Launcher.exe and click 'End Proces
s.' Once that's done, you can move on to the entry below, to figure out why your
launcher isn't starting up properly.
Launcher Doesn't Appear / Just Won't Start / Takes Forever to Start
When the launcher first starts, the UI won't appear until its finished a few thi
ngs. As a result, if the launcher freezes up on you at start, you won't see anyt
hing appear at all. You will still see launcher.exe in your Task Manager process
list, however, as noted above.
For some people, allowing the launcher to sit for 10-15 minutes actually allows
it to finish whatever its trying to do and recover. This situation (the long wai
t) apparently arises most often with college campus proxies that are automatical
ly assigned in Internet Explorer via a PAC file, where not all proxies play nice
ly with the launcher. Or where the computer has stopped being on college campus,
but is still trying to request PAC information.
However, some ad-blocking software will set up proxies in Internet Explorer that
remain even if the software's been uninstalled. It's worth checking Internet Ex
plorer's proxy settings, as a result, as the WinInet library -- and thus the SWT
OR launcher -- inherit system proxy settings from IE.
So, open Internet Explorer and pick the 'Tools' menu, then select 'Internet opti
ons.' Go to Connections, and click on 'LAN Settings' -- see if there are any pro
xy settings there which might be causing you problems, including 'Use automatic
configuration script.' You can try unchecking those options if so, and then runn
ing the launcher again.
If, however, that does not work, there are a few things you can still try. One o
r more of these may apply to you.
Check if there is a "patch" directory under your SWTOR install. If there is, the
launcher may have died partway through checking on patches. Delete that directo
ry and things will likely work.
You can also delete the launcher.settings file without any worries, and that may
fix things if the launcher had some broken state.
Hit up Windows Update and make sure you have the latest .NET updates installed.
Make certain launcher.exe is allowed through your firewall.
Some folks have reported issues with the Launcher even when added to the excepti
on list if using Avira, so you may want to try another antivirus to see if that
works if you are using Avira.
The same thing applies to Comcast's branded version of Norton.
If you are using ESET, try turning off Protocol Filtering.
Make certain that you have the latest build of Java installed. You may also have
better luck with the 32-bit version of Java even on 64-bit systems.
If you are running a game that uses GameGuard anticheat protection, GameGuard se
ems to conflict with the SWTOR launcher in some situations. In most cases, if yo
u ensure the game's launcher/update tool has been exited, GameGuard will go dorm
ant and you'll be able to play. This means quitting out of launchers for Lineage
2, Aion, etc. that might be running.
If none of that applies to you or nothing lets Launcher start working, you may w
ant to try rebooting Windows in Safe Mode + Networking, and see if the launcher
will start up for you. If the launcher starts in Safe Mode, then something runni
ng in normal mode is likely the cause. If you boot in Diagnostic Mode (which loa
ds all drivers, where Safe Mode doesn't) and the launcher fails to work, then yo
one setting here on the account page of your SWTOR.com settings are the same. Ba
sed on a couple posts by CS droids in other threads, if the timezones don't matc
h, you might get an authentication failure and the 'Server Not Responding' error
when you try to log in.
If time and date are correct, you might have a network issue. Make sure that you
've allowed launcher.exe through your firewall software and that it's not being
blocked by any antivirus or other security software!
There are also a few programs which can cause issues:
ESET: If you are using ESET as your antivirus and firewall, go and disable Proto
col Filtering in the settings and see if that fixes the launcher for you.
Kaspersky Internet Security: Turn off 'Scan secure connections' and see if the l
auncher works properly.
IPblocker: If you are running IPblocker, you will need to add Launcher.exe to th
e exceptions, or else it can stop the launcher from running.
Peerblocker: For whatever reason, even if you add the launcher to Peerblocker's
exception list, it doesn't always like the launcher and will stop it from talkin
g to the Launchpad. Try disabling Peerblocker and see if this fixes things.
Additional Verification Needed
This error crops up if you haven't set security questions on your account. Go ch
eck the security question page and set at least three of the five questions. Onc
e this is done, the launcher should allow you to log in with your user and passw
ord, to begin patching.
Certificate Failure
If you get a certificate failure error, the simplest thing to check first is whe
ther your clock is off. If your clock is way off, by years, the launcher fails t
o negotiate properly with the patch servers entirely. (This happens when securit
y certificate fails to validate, because your clock is set to some time before t
he certificate existed. If your computer thinks it's 2007, a certificate from 20
11 is clearly not valid yet.)
You may also have outdated security certificates which you've skipped over updat
es for. You can go find the optional 'updated certificates' update in Windows Up
date (probably the simplest route), or re-download the Verisign and Thawte Root
Certificates from the Verisign site manually, using this helpful guide by the Dr
unken Pirate Guild. Updating those certificates from either source can't hurt an
yway; Bioware's going to be far from the only place that'll eventually sign with
the newer ones.
I Keep Getting a Busted Security Question
Make certain your security question doesn't contain any accented characters. Eve
n if the website allows this (which I don't believe it does, anymore), the launc
her doesn't always like it.
Further Troubleshooting Info For This Problem
If the above fixes don't work and you're going to ask CS or other players for he
lp, you will need your launcher logs. Go to your SWTOR directory, and you will f
ind a logs directory under it. Find the latest launcher log and include it, wrap
ped in SPOILER tags, when posting a request for help on the forum.
2.4 - LAUNCHER WON'T PATCH
You logged in, and now the launcher is trying to pull down great heaping piles o
f Old Republic data to get the game patched up. If this is the point where you'r
If that doesn't work, however, you can check the launcher logs (in the 'logs' di
rectory under where you installed SWTOR) to see what the error is.
Reliable source serving corrupt data
This means that one of BioWare's Content Delivery Network (CDN) servers is servi
ng you corrupted data. They've gone through and scrubbed corrupted servers from
the system, and changed the launcher's behavior; what the launcher should do at
this point is keep reconnecting to different CDN servers until it gets a valid c
opy of the file.
If you did edit your hosts file as was recommended in several threads way back i
n the early days of the game, the BioWare folks have asked that you revert that
change, because that causes all users to hit one specific CDN server, which caus
es that server to deliver data veeeeery sloooooowly and can cause other problems
. In fact, if you're now having problems with more recent patches, the hosts fil
e change is a good possibility as to the cause; when all the folks who edited th
eir file try to patch and all hit one single CDN server to download everything,
that server will be heavily overloaded and serve files slowly (or stop serving t
hem at all).
'Corrupt Source detected' error, 'Unknown file' error or 'File info: missing...'
error in launcher log
These errors mean that the file checked out on the CDN side, but was corrupted o
n your local side somehow. There's unfortunately no one fix for this. Many folks
with these errors have been able to fix the situation by running the Repair opt
ion in the launcher, but if the problem persists, there are a few other possible
fixes with no clear front-runner.
Important note: Though the 'repair' option will appear to redownload the game, i
t is not necessarily actually doing so. It's examining the assets, comparing, an
d figuring out what it needs to redownload. See this post from BioWare for furth
er details.
Now, some people have seen the corruption due to other (hardware) issues: becaus
e the files are so large, the launcher seems more vulnerable to memory issues th
an some things are (simply by virtue of touching so much of your RAM at once as
the files are uncompressed, patched or copied around). Running memtest86 can hel
p to expose if there are issues in your memory, but there can also be misconfigu
ration. For instance, BioWare's also noted that they've been internally able to
reproduce patching errors on a system where the CAS Latency in the machine's BIO
S was set wrong for the memory installed, causing memory errors which corrupt th
ings in much the same way. So you can check your memory speed in your BIOS.
If your memory is good and your configuration is good, there's also a corner cas
e in some 64-bit editions of Java which can affect the patcher portion of the la
uncher; if you're on a 64-bit machine, there seems to be a bug in the 64-bit JRE
that can cause large buffers to get corrupted in certain edge cases; this cause
s the patch process not to work right. The simplest fix is thus to uninstall the
64-bit version of Java and reinstall the 32-bit version of Java 1.6.
If even that still doesn't work, BioWare folks are trying to track down other ca
uses, and are asking that people send them information, as per this sticky threa
d. So, if you find these error in your launcher logs and your memory tests out g
ood and the configuration is right and the Java suggestion doesn't work, please
contact them with the information they request in that thread. The more informat
ion they can gather, the more easily they'll be able to make fixes that will hel
p get everyone up and running more smoothly in the future!
In the meantime, the best workaround for this issue is to get a copy of the SWTO
R directory from a friend (or a second machine) whose copy you know is not corru
pted and which has patched successfully. That's not an ideal solution, but it'll
get you up and running in the meantime.
Further Troubleshooting Info For This Problem
If the above fixes don't work and you're going to ask CS or other players for he
lp, you will need your launcher logs. Go to your SWTOR directory, and you will f
ind a logs directory under it. Find the latest launcher log and include it, wrap
ped in SPOILER tags, when posting a request for help on the forum.
3 - STARTING THE GAME (SWTOR.exe)
3.1 - NO PLAY BUTTON
Your launcher is working, everything's downloaded, and now... the play button is
grey! And there's an error message!
The error message flashed past too fast to read!
If the error message flickers past way too fast, chances are it says "The curren
t environment is unavailable for play" or something similar.
Okay, then, the error is "The current environment is unavailable for play."
That means 'none of the servers you have access to are available right now.' Thi
s usually means, you want to check the server status page or forums for stickies
or posts about server downtime or maintenance.
You may also want to make sure you're not accidentally using the Public Test Ser
ver at a time when the PTS isn't around.
3.2 - ERROR CODES
You're ready! You click PLAY and...
ERROR CODE 1
If you're getting a black screen followed by an 'Error Code 1' dialog box, some
users are reporting that downloading the Origin client and running it once adds
some missing settings or setup to your machine and can resolve the error.
ERROR CODE 3
This seems to have something to do with administrator accounts in general. If yo
u aren't on an administrator account, you'll need to run the game on one. If you
are on an administrator account, try making a new one and running the game ther
e to see if that works. The usual caveat applies: don't use any strange characte
rs in the account name, just stuck to A-Z and 0-9.
ERROR CODE 5
This error code usually means one of the asset files has become corrupted on dis
k somehow. Running 'repair' in the launcher may work to get you back up and runn
ing, by re-downloading the broken asset. Alternatively, if you have someone else
in the same household (or a friend locally) who has a good, working copy of SWT
OR on their own machine, you can just copy their directory over to your machine
and that should fix the problem.
ERROR CODE 6
The most common cause of this error is when you don't have at least 3 gigabytes
of disk space free. If you installed TOR on a drive other than your main Windows
system drive, make sure there's 3gb free on both some data is likely to be stor
ed in temporary directories or otherwise in your user profile data, which will m
ost likely be on your system drive.
The Bioware folks have suggested also making use of Microsoft's Disk Cleanup too
l to try and free up space. If you have 3GB free on all applicable drives, bad s
ectors could be confusing the situation. Run scandisk, and check again.
This error can also happen if you have non-standard characters in your Windows u
sername -- Chinese or Japanese, Cyrillic or Greek letters, or even just accented
characters can cause the game to erroneously return error code 6, thinking ther
e's not enough space in the AppData directory. If you have accented characters o
r other non-ASCII characters in your Windows username, try making a temporary se
cond Windows account and running the launcher.
ERROR CODE 7
One of the common issues here is if your graphics drivers aren't up-to-date. If
your graphics driver doesn't support the Direct3D Shader Model 3, this error wil
l happen. So, double-check that your graphics drivers are current first, because
that's the easiest fix. Unfortunately, if you don't have a dedicated GPU (i.e.,
if you don't have an Nvidia or ATI graphics card) you probably won't be able to
play.
If you are on an ATI-based Mac using Bootcamp, the drivers included with Bootcam
p do not always work and may trigger the issue. You can hit up AMD's GPU driver
download page and pick specifically the Mac/Bootcamp option and the appropriate
version of Windows; the drivers AMD will give you from that page are known to wo
rk properly with SWTOR.
If your card is definitely good and your drivers are current, this can also be c
aused if your .NET Framework is out-of-date or if you have an older version of D
irectX installed, so hit up Windows Update just in case. And one last possibilit
y is that your copy of PlatformInfo.dll is missing from the installation (or cor
rupted). If that's the case, you can try reinstalling, or you might be able to g
et a copy from a friend's installation of the game.
Another issue is apparently if you use ASUS GamerOSD to allow overclocking of yo
ur GPU, something in that program conflicts with the system check and can cause
the Error Code 7 issue to surface. In general, if you are running anything you d
on't absolutely require for the computer to function, you should probably try qu
itting it to see if it was causing a conflict with the game. You can even try a
Clean Boot just to be safe.
Unfortunately, those don't seem to be the solution for everyone. The CS droids a
re aware of that, and are trying to collect information for the developers in th
is thread, where they'll also presumably provide updates on any fix. If everythi
ng is current, you'll want to check over there.
SERVER ERROR 1002
Error 1002 actually means that you've become stuck in a queue. According to Biow
are, you'll want to make sure there are no SWTOR processes running in the task m
anager, and then just wait 30 minutes. That will give the servers enough time to
see that you're a ghost, kick you from the queue, and allow you to log back in.
SERVER ERROR 1003
Normally, this means the server has gone down -- or been taken down for maintena
nce. It can also be related to firewall issues, so the usual 'check your firewal
l' instructions apply.
For some people, this happens without any firewall issue and while the server is
demonstrably up. For many people, setting the launcher to run in Windows XP SP3
compatibility mode seems to solve the problem as an interim workaround. Otherwi
se, there is currently a sticky BioWare information thread where they are trying
to gather more information on this particular error.
SERVER ERROR 1005
First, do make sure that SWTOR is being allowed through the Windows firewall, as
per the instructions here on Microsoft's site. If you use a different firewall
program, make certain that SWTOR is allowed to function as a server as well as a
client (i.e., to accept incoming connections as well as make outgoing ones).
Secondly, make certain you're not running Peerblock, IPBlock or Hotspot Shield.
For some reason, Peerblock in particular can conflict with TOR at the actual gam
e level and will prevent the server list from downloading. Make sure to add SWTO
R.exe and Launcher.exe to the exemptions, or else temporarily turn the blocker/s
hield off while playing.
Bioware CS has noted that the following ports need to be open for SWTOR, as well
:
80
2052-2053
8995
12000-12999
20000-30000
For the vast majority of modern routers, SWTOR will be able to negotiate opening
these ports for you. Unfortunately, if your router is not allowing SWTOR to pro
perly request these ports to be opened for you, you may need to go to your route
r and forward them to your machine directly. The process necessary to open the p
orts on your router will be specific to your router, so you'll probably need to
Google the make and model number, along with 'port forwarding' or 'open ports.'
If you are on a college network, you may have to contact campus IT to ask them a
bout getting access through a proxy server of some form.
Further Troubleshooting Info For This Problem
If the above fixes don't work and you're going to ask CS or other players for he
lp, you will want to grab your DxDiag output. Go to the Start menu, pick Run, an
d enter DxDiag in the field. Click the 'Save All Information' button, and save t
he report as a textfile on your desktop temporarily. Open that textfile, and you
'll see a report suitable for pasting into the forum. You will also potentially
want a client log, which can be found in your SWTOR directory; go to the SWTOR d
irectory, then pick the 'swtor' folder in there, then 'retailclient' and then 's
wtor' and then 'logs'. Be sure to enclose all logs/reports in SPOILER tags to ke
ep from making threads unreadably large.
3.3 - GAME DOESN'T START / BLANK SCREEN
Game Crashes Immediately with a Message about MSVCP90.DLL
The MSCVP90.DLL is part of the Visual Studio 2008 runtime set. Normally this is
installed by a number of programs, but especially if you skip installation seque
nces it's possible to end up missing this file, or with an outdated copy. The qu
ickest fix for this is to go grab the latest copy from Microsoft in a handy VS20
08 runtime redistributable package. Once you're up-to-date, things should go bet
ter.
Game Crashes Immediately with NodeSpecCache error
For some people, running the FixLauncher.exe program in your SWTOR installation
directory will solve this. For others, they may have to use the Repair function
in the launcher.
If neither of those helps, one of the more common causes of this issue seems to
be having a language other than English (United States) set as the fallback lang
uage in your Windows preferences. If you're running Windows 7, this can be set f
rom the 'Region and Language' control panel go to the Administrative tab and mak
e sure the 'Current language for non-Unicode programs' is set as 'English (Unite
d States)' -- if that's not the setting, change it and try running again.
Another cause is if your Windows user account name contains extended characters
(accented characters, Greek characters, Cyrillic characters and so on). You can
try creating a second administrator account using only basic numbers/letters and
If you click Play and the game seems to hang for several minutes, this is not un
expected. Don't panic over this either just wait a few minutes, and you should s
ee the opening movie.
If it still never starts after that, some players have reported that having a se
cond monitor active causes the game not to load if you're set in fullscreen mode
. Try temporarily disabling your second monitor, and the game might start up.
If you get a screen that only has the SWTOR logo and the blue 'loading cog,' the
n you may have a firewall or security dialog that popped up behind the game, ask
ing whether or not to allow it access to things. If that isn't the case, you mig
ht be in a server queue there appears to be an issue where the queue position po
pup doesn't come up in all situations. Just hold tight, and you might pop in whe
n your queue number comes up.
My Screen Goes Black!
If you only get a black screen indefinitely, check to see if you are running an
ATI/AMD Radeon card. If you are, there is a known incompatibility with the Catal
yst 11.8 (and occasionally 11.9) drivers they will not work and will result in a
black screen. Either update to newer drivers, or roll back to old ones, and you
should be fine. 11.10 and 11.11 are known to work fine, as is the 11.12 that AM
D/ATI released on December 13th.
There are also rumors that the current beta build of the Nvidia unified drivers
has a similar problem for some people if you're a GeForce user with the black sc
reen problem and grabbed the most recent beta, you may want to try downgrading t
o the last real release.
If your monitor is saying something like 'invalid resolution' or 'bad signal' or
whatever, chances are that the SWTOR default resolution wasn't working with you
r monitor. You'll probably want to go find the 'client_settings.ini' file in you
r SWTOR directory and change a few modes.
You can find the client_defaults.ini file in the installation directory of the g
ame. By default it is located at:
For 32 bit Operating Systems - C:\\Program Files\\Electronic Arts\\BioWare\\Star
Wars - The Old Republic\\swtor\\retailclient
For 64 bit Operating Systems - C:\\Program Files (x86)\\Electronic Arts\\BioWare
\\Star Wars - The Old Republic\\swtor\\retailclient
Open the file in a text editor you'll find many graphics settings there.
The most common settings to change for people are:
fullscreen (often changing from 'true' to 'false')
D3Dfullscreen (often changing from 'true' to 'false')
windowed mode
You'll also find width/height/refresh and other options, if you know what you're
doing. Once you've edited the file, save it and exit the editor, then try runni
ng the game again.
If that doesn't help, there's also a Bioware thread on video and sound issues yo
u might want to check, and one on specifically the black screen issue, with deta
ils on some troubleshooting steps you can take.
My Screen Goes Black And (For Added Fun) I Crash, Too!
Apparently, this is often a partially corrupted DirectX installation. Unfortunat
ely, the smaller web-installer version of DirectX cannot repair a broken install
ation, where the bigger actual DirectX distribution can. If you think this might
be your problem, you'll want to download the full DirectX redistributable packa
ge and run a repair from that, then try again.
As mentioned earlier, as well, if you have two monitors, apparently the renderin
g changes in patch 1.1 also can cause issues; if you disconnect the secondary mo
nitor, the game may start correctly for you.
If that doesn't help, there is a thread on this, where folks are trying to track
down possible causes.
My Screen is All Stretched and Everyone Looks like 'Fat Hobbits.'
There are two main causes for this.
First, if you're on a Mac running Windows under Bootcamp, the version of the ATI
drivers included with the Bootcamp disc doesn't like SWTOR. Don't bother trying
to update the ATI drivers via Apple Software Update or Windows Update, just gra
b Catalyst from ATI's site directly and install.
Secondly, apparently some people have had Windows Update install an erroneous mo
nitor driver. Since SWTOR reads monitor settings differently than some games, th
is has caused it to think it needs to run the 3D portion in 4:3 mode. If you've
had an odd monitor driver appear that doesn't match your real monitor, try unins
talling it and either reinstalling your real monitor's driver, or reverting to t
he generic Plug-and-Play driver monitor.
If neither of those works for you, unfortunately, there doesn't seem to be a way
to override this at present.
Further Troubleshooting Info For This Problem
If the above fixes don't work and you're going to ask CS or other players for he
lp, you will want to grab your DxDiag output. Go to the Start menu, pick Run, an
d enter DxDiag in the field. Click the 'Save All Information' button, and save t
he report as a textfile on your desktop temporarily. Open that textfile, and you
'll see a report suitable for pasting into the forum. You will also potentially
want a client log, which can be found in your SWTOR directory; go to the SWTOR d
irectory, then pick the 'swtor' folder in there, then 'retailclient' and then 's
wtor' and then 'logs'. Be sure to enclose all logs/reports in SPOILER tags to ke
ep from making threads unreadably large.
3.4 - GAME ISSUES AFTER PLAYING A BIT
I Get Disconnected with "Error 9000"
Error 9000 means your internet connection went away... or at least, the game thi
nks it did. If you're playing on a link that has a tendency to drop, this error
is probably real. However, apparently some folks have seen Ventrilo cause this i
ssue while playing on an otherwise-solid Internet link. If you're getting this p
roblem and are running Ventrilo, try quitting and seeing if that helps. (No, tha
t's not an ideal solution, I admit.)
Another interesting factor is that some setups -- it's unclear where in the chai
n of things, whether at your router, your modem or your ISP or what -- don't see
SWTOR connections as actual network traffic, and so will reset your connection
periodically. Setting something that will be recognized as a live connection -streaming video in the background (BBC iPlayer works for those who have access),
or BitTorrenting a Linux ISO or something similar (please only choose LEGAL tor
rents, folks) -- can prevent this sort of reset/disconnect, and thus keep you co
nnected. If you BitTorrent something, set the bandwidth to be pretty low; you'll
stay connected, and it won't eat all your link. This trick does not work for ev
eryone, but has worked for a surprising number of players who were suffering the
Error 9000 disconnection issue.
Blue Screen of Death
If you're getting a
e most likely cause
eaning out the fans
ry turning down the