Elite Dangerous

Elite Dangerous

"Application startup exception"
I recently reinstalled the game and got these messages in order after clicking play
https://gyazo.com/66d8dffa1014dfbf066512ad4d111567
https://gyazo.com/49e3b7c0ae98e3935716a33417c6a8bf
It then says that Elite Dangerous has stopped responding.
I have tried validating it and reinstalling it to no avail. I have previously been able to play this game.
Any help on the matter would be greatly appreciated.
Last edited by The Screaming Creamer; Sep 23, 2015 @ 2:26pm
< >
Showing 1-8 of 8 comments
Wolf Sep 23, 2015 @ 2:29pm 
try uninstalling the redistributable packages in programs and features in cpanel then reinstall the required package. this worked for 2 people today. if you uninstalled steam and installed it in the programs folder, you will have to run steam and the launcher as an administrator or move the steam installation to a non system folder like c:\\steam\
Wolf Sep 23, 2015 @ 2:30pm 
anything beyond that, i would either run system restore, or contact frontier support.
I would likely choose the latter 1st :)
Last edited by Wolf; Sep 23, 2015 @ 2:31pm
Thank you for the reply. However, before doing what you said I decided to try to launch it directly from EDLaunch.exe in the Elite Dangerous folder in steam and got the same messages as I did before, however I also got an additional "error parsing" message exclusivley from launching the game like this. Basically, this message was telling me there was something wrong with the .NET framework in the frameworkx64 folder (for anyone else sharing this problem, the location of this folder is C:/Windows/Microsoft.NET/Framework64/v2.0.50727/CONFIG). What I did was this;
in the CONFIG folder, I created a backup of the file machine.config and placed it on my desktop in case anything went wrong. Then I did this:
1) Delete the machine.config file (in CONFIG)
2) Make a copy of machine.config.default
3) Paste the copy in the CONFIG folder
4) Rename the copy machine.config
5) restarted my computer
The reason I thought this might have been the solution was because of my passed experience with the "error parsing" pop-up. I solved my previous problem in relativley the same way as I did this one. Luckily what I did in both cases ended up working for me, so if anybody sees this and has the same problems as I did I hope this helps you out.
Last edited by The Screaming Creamer; Sep 25, 2015 @ 5:39pm
Wolf Sep 25, 2015 @ 5:42pm 
nice, glad its working now. hopefully this thread will help some others too. thanks for posting your solution :)
Raven Oct 20, 2015 @ 4:24pm 
Hello.
I had that problem too.
If anyone still have it, I contacted Frontier and got the response below.
Nothing that people suggested worked for me, except the item 5 of the list below. And this e-mail from Frontier is the only place I ever saw this suggestion.
So I bring it here in hope that this might help someone.
______________________________________________________________________

Please try the following steps as these should resolve most of the common issues encountered with the launcher.

1- Restart your computer - Please restart after the launcher is installed and before you run it. This is a key part of the installation process so please try again after restarting your PC.

2- Check your .Net version - Please try installing the latest versions of .Net 3.5 and 4.5 from Microsoft, which can be found here and here. Can you also make sure that the "Turn Windows features on or off" page has both entries under Microsoft .net Framework 3.5.1 unticked.

3- Check for 3rd party monitoring programs - If you are running any 3rd party hardware monitoring software or graphics card companion programs such as EVGA Precision, Raptr, Lucid Virtu MVP, Nvidia Experience or AMD Gaming Evolved, please try closing them and then try running the launcher. These programs can usually be found with an icon running in the System Tray (lower right of the screen). Please also try closing down any other non-essential programs running to rule these out.

4- Check for corrupted files - If the steps above fail to solve the issue, please try the steps in this Microsoft article to rule out the chance you have any corrupted files affecting the launcher: http://support.microsoft.com/KB/929833 Please note that the scan process may take a while, so please only run this at a time when you won't be needing to use the computer for a while.

5- Change EDLaunch.exe.config - On C:\Program Files (x86)\Frontier\EDLaunch you will find a file named EDLaunch.exe.config. Firstly, make a backup this file by copying it to another location such as your desktop. After that open the EDLaunch.exe.config file with a text editor such as Notepad. You'll see a line with something similar to: < supportedRuntime version="v2.0.50727" /> Simply delete this line and leave the line underneath that states "v4.0" instead, save the file and run the launcher again.

As a last resort please follow the steps below:
- Uninstall the launcher from your computer
- Remove (delete) any left over files from where the launcher was installed. This will mean you may have to download all game files again.
- If "C:\Program Files (x86)\Frontier\EDLaunch" exists - Delete it
- If "C:\Users\AppData\Local\Frontier_Developments\Products" exists - Delete it. Appdata is a hidden folder by default, so to access it you will have to copy the file path into file explorer or enable "Show hidden files and folders" in the System Control Panel -> Folder Options
- Install the Launcher to a non-program files location
- For Example "C:\Games\EliteDangerous"
- Do NOT run the launcher at the end of the install process. Untick the checkmark that asks you if you would like to and close the installation.
- Launch the launcher but NOT as administrator
- Download game and try again
JayBee Oct 27, 2015 @ 3:08pm 
Originally posted by Cirincioneator:
Thank you for the reply. However, before doing what you said I decided to try to launch it directly from EDLaunch.exe in the Elite Dangerous folder in steam and got the same messages as I did before, however I also got an additional "error parsing" message exclusivley from launching the game like this. Basically, this message was telling me there was something wrong with the .NET framework in the frameworkx64 folder (for anyone else sharing this problem, the location of this folder is C:/Windows/Microsoft.NET/Framework64/v2.0.50727/CONFIG). What I did was this;
in the CONFIG folder, I created a backup of the file machine.config and placed it on my desktop in case anything went wrong. Then I did this:
1) Delete the machine.config file (in CONFIG)
2) Make a copy of machine.config.default
3) Paste the copy in the CONFIG folder
4) Rename the copy machine.config
5) restarted my computer
The reason I thought this might have been the solution was because of my passed experience with the "error parsing" pop-up. I solved my previous problem in relativley the same way as I did this one. Luckily what I did in both cases ended up working for me, so if anybody sees this and has the same problems as I did I hope this helps you out.


worked for me as well thanx
Originally posted by JayBee:
Originally posted by Cirincioneator:
Thank you for the reply. However, before doing what you said I decided to try to launch it directly from EDLaunch.exe in the Elite Dangerous folder in steam and got the same messages as I did before, however I also got an additional "error parsing" message exclusivley from launching the game like this. Basically, this message was telling me there was something wrong with the .NET framework in the frameworkx64 folder (for anyone else sharing this problem, the location of this folder is C:/Windows/Microsoft.NET/Framework64/v2.0.50727/CONFIG). What I did was this;
in the CONFIG folder, I created a backup of the file machine.config and placed it on my desktop in case anything went wrong. Then I did this:
1) Delete the machine.config file (in CONFIG)
2) Make a copy of machine.config.default
3) Paste the copy in the CONFIG folder
4) Rename the copy machine.config
5) restarted my computer
The reason I thought this might have been the solution was because of my passed experience with the "error parsing" pop-up. I solved my previous problem in relativley the same way as I did this one. Luckily what I did in both cases ended up working for me, so if anybody sees this and has the same problems as I did I hope this helps you out.


worked for me as well thanx
I'm glad I could help someone else out too!
Doogal Dec 25, 2017 @ 6:42am 
Originally posted by Andrew:
Originally posted by JayBee:


worked for me as well thanx
I'm glad I could help someone else out too!
Thanks Andrew this solution helped me out to.
< >
Showing 1-8 of 8 comments
Per page: 1530 50

Date Posted: Sep 23, 2015 @ 2:25pm
Posts: 8