Elite Dangerous Launcher crashing all the time.

[CMDR. Isaac Newton]

Hi, i have put in a support ticket as well about this issue but was wondering if anyone has experienced and fixed this issue about a Cobrabaywindow.xaml crash when trying to run the launcher in steam. Last week it was working perfectly and I was playing fine. Tried today and just get instant crashes and very little info from searching on a real fix to the issue.

I've done the uninstall and removed all files from appdata reboot, then reinstall the game through steam and get the same error. The only change on my machine during the week was upgrading Windows 10 to the May edition 2004 release.

PC specs is 3950x, 32GB ram, Aorus Master motherboard, installed on a Sabrent NVMe SSD, Sapphire Vega 64 Nitro on the latest drivers and Asus Strix sound card. Will enclose a image of both error messages that appear soon as I launch the game.

The game will load if I bypass the launcher but of course you can't play it then either.

 

[STRONTIUM DOG]

does the vanilla crash an burn too or are you not talking about horizons?

 

[SMcA]

You have tried to validate your game files from the Launcher's menu?
Sorry for asking.

 

[CMDR. Isaac Newton]

Crashes on Base game, Horizon and VR version. And yep tried validating the files and changing my EDLaunch.exe.config from
<supportedRuntime version="v2.0.50727"/>
to V4.0
As support ask me to try but get a new error message instead. Enclosed the message below if it helps.

I've even tried going back to the original launcher from the store page in case it was something to do with Steam but get the same errors as well.

 

[Faded Glory]

Crashes on Base game, Horizon and VR version. And yep tried validating the files and changing my EDLaunch.exe.config from
<supportedRuntime version="v2.0.50727"/>
to V4.0
As support ask me to try but get a new error message instead. Enclosed the message below if it helps.

I've even tried going back to the original launcher from the store page in case it was something to do with Steam but get the same errors as well.

This looks like it's the .NET Framework issue.

Take a look at this post and I'd suggest trying option 1 which is editing the EDLaunch.exe.config file.

Here's the steps to fix the issue taken from the post above.

Spoiler

Option 1. Go to C:/Program Files (x86)/Frontier/EDLaunch and you'll find a file EDLaunch.exe.config Back up this file.

Then open it using Notepad and look for the following lines
<supportedRuntime Version="v2.0.50727"/ >
<supportedRuntime Version="v4.0"/ >

Switch the lines so they look like this:
<supportedRuntime Version="v4.0"/ >
<supportedRuntime Version="v2.0.50727"/ >

Save the file (make sure it's still a .config file, Notepad has a habit of saving it as a Notepad file which might cause issues), and that should solve the error. If it doesn't (it did for me) you can simply revert to the original copy of the file you backed up.

Edit - Oops, sorry, see you've already tried that.

Cannot speak for steam, but this has worked 100% for me when getting that error with the native launcher.

 

[CMDR. Isaac Newton]

Hehe aye tried that as well as checking my .Net Frameworks were on and tried reinstalling theml. The only thing makes sense is the Windows 10 update has changed something that breaks the launcher from working. Was hoping that others had ran into the same issues and there was a workaround for it.

 

[nepomuk]

Hehe aye tried that as well as checking my .Net Frameworks were on and tried reinstalling theml. The only thing makes sense is the Windows 10 update has changed something that breaks the launcher from working. Was hoping that others had ran into the same issues and there was a workaround for it.

The May update has problems. Can you go back to the previous version ?

Windows 10, version 2004 and Windows Server, version 2004

View announcements and review known issues and fixes for Windows 10 version 2004 and Windows Server 2004

docs.microsoft.com

German - https://www.chip.de/news/Viele-Bugs...Fehler-stoppen-Windows-10-2004_182737243.html

 

[CMDR. Isaac Newton]

I had a look at the issues before updating and none of them would affect me personally. And I like that variable refreash rate is working properly on multi displays so I would rather not do the roll back.

I'd see the point to do a roll back if I was having multiple issues across games and programs but not really for one game though. If you see what I mean.

I can wait for some patch to fix it from the dev's in the meantime though

 

[CMDR. Isaac Newton]

Just bumping to say the issue has been fixed, Support kindly noticed I didn't have the proper v2004 windows update but the insider one which they had someone else have the same issue trying to launch the game.

Would have thought updating to 2004 was the real update after all. Silly me

 

[Para Handy]

Just bumping to say the issue has been fixed, Support kindly noticed I didn't have the proper v2004 windows update but the insider one which they had someone else have the same issue trying to launch the game.

Would have thought updating to 2004 was the real update after all. Silly me

Was that the " <supportedRuntime version="v2.0.50727" " thing? It is crazy that the launcher fails if that is not present as it works fine with just " supportedRuntime version="v4.0" " *- why they can't code the launcher to accept either I don't know. Mind you they have not found anyone able to code a "save as" button in the Controls setting page either.

* One can edit out that "v2..." entry from the config and the launcher works fine.

 

[CMDR. Isaac Newton]

Nah it was that I installed the Windows 10 update marked as 2004 but it turned out that was from before December last year for the Insider builds, Once I reverted back to my previous windows build 1909 the launcher was working fine.

I am trying the windows update at the moment to 20H1 as they call it so it may just break it again

 

[CMDR. Isaac Newton]

Okay and on the 2004 build it does the same crashing. So you may want to hold off on doing the Windows 10 update for now till it's been fixed

 

[yah-ta-hey]

Frontier installs info in your registry and if that registry gets corrupted... it can give you fits... I had the Mauve problem and a registry cleaning fixed it and it has not come back. There are free registry cleaners out there from the antivirus people and I think microsoft has a freebie also. good luck.

 

[CMDR. Isaac Newton]

Wish that would have fixed it but alas no.

Thanks for getting back to us, I've passed this issue on to be investigated internally and will hold on to your ticket until I have an update.

Hopefully when we know more we can get this fixed for you as soon as possible.

Is the last response to my ticket so hopefully in a little while a fix for it will come out

 

[MACsaddict]

i am having this issue now and cannot figure it out... any success?

 

[MickyG1982]

i am having this issue now and cannot figure it out... any success?

Start by giving us a clue as to what you're actually running, inc the gpu. Make sure your drivers are up to date, state whether it was working before or if this happened after a change in hardware or software.

basically, the more info you can provide, the more help we will be able to try and give you.

 

[MACsaddict]

thanks, I was just hoping the OP could me out because they were having the same problem and opened a ticket with frontier...

ryzen 1700x
1080 ti
16gb ddr4 ram
game is install on SSD
windows 10 pro

all drivers are up to date

game worked previously. I just rebuilt this computer into a new case, same components. I was having a PSU related issue and got that replaced recently.

I set up my Vive on this pc for the first time to try out with ED, and after setting it up ran into this issue. Also, I haven't booted the game in months prior to this.

Since encountering the problem, things I have tried:

• validating files through steam
• uninstalling and reinstalling
• uninstalling .NET 3.5 and reinstalling via turn windows features on/off(I also have 4.8 installed and have tried the same with that)
• using .NET repair tool
• running sfc /scannow
• modifying the edlauncher.exe.config to remove/modify(and every permutation in between) the runtime version

@yah-ta-hey mentioned cleaning the registry, that sounds like it could be promising... not really sure what I need to do tho

thanks for any help you can provide

 

[MACsaddict]

oh and with nothing modified, these are the errors I get:

then, if I modify the edlauncher config to remove the v2 runtime line (so only v4 line is left), I get these errors:

 

[STRONTIUM DOG]

free ccleaner will clean the reg up but I am suspecting windows version or net framework issues
I would try to get the game running on just a basic monitor first too

 

[MACsaddict]

created a support ticket, frontier said its a known issue with the windows 2004 update(confusing name, its the most recent update) that they are looking to see if they can resolve on their end, but currently the only confirmed fix is to reinstall windows... so I did a 'reset my pc' or whatever from the advanced settings menu and everything seems good now.