Haven't played for a while, and now the launcher won't open

internal error creating window

cannot convert string '/EDLaunch;componet/EliteImages/Logo48.png'
in attribute 'icon' to object of type
'System.Windows.Media.ImageSource'.Thei image data generated an
'CobraBay.CobraBayWindow' in markup file
EDLaunch;componet/cobrabaywindow.xaml'.



I've tried deleting the <supportedRuntime version="v2.0.50727"/> line from the config, but hasn't helped. Also ran as admin and that didn't help either.
This is getting frustrating, I just want to play space game. Space game is fun, but space game no open. Help?
 
Does the launcher open at all? If so can you open the options menu and select "Validate Game Files"?

If it has been a very long time since you played maybe installing the current launcher would help:



good luck
Thanks for responding, no the launcher doesn't open at all. I get an unhandled exception: cannot create instance of "cobrabaywindow'

I've looked into this for a few days now, and the only fix I've heard is a fresh install of OS, and I really don't want to do that.
 
I have ED through steam and have validated the files several times. I've deleted the launcher and launcher exe and reinstalled them, rolled back net framework and nothing works.
 
yeah, i started filing a ticket. I was hoping for some hail mary last ditch thing that might work, I don't think frontier support is going to be able to do anything other than maybe offer a refund I wont take, and ill just have to bite the Microsoft bullet and reinstall OS.
 
One thing comes to mind... If you bought the game on Steam before April 2019 then you should have a "CD-Key copy". In which case you can install and run the game direct, not in Steam at all, so that would give you a completely different installation which might eliminate your issues. - Just a stab in the dark but quicker than an OS reinstall.
 
Having the same issue here. I've not played for a couple of years and fancied a quick flight ahead of the new content.

I have the same issues as above - "Application Failed to Start - Internal Error creating window:".

I have tried the following:

  • swapped (or remove) the <supportedRuntime version="v2.0.50727"/> (which leads to a different error)
  • removed and reinstalled .NET3.5 and 4.8
  • reinstalled Visual C++ runtimes 2009-2013
  • validated E: Dfiles within Steam
  • reinstalled E: D within Steam
  • tried to run from safe mode (with networking)
  • tried to run from a "clean" boot (removing most services/apps using MSCONFIG)
  • updated Windows to latest
  • updated nVidia drivers latest
  • removed Voice Attack
  • removed Oculus Software (used for my old DK2)
  • run Windows repair

...but still no joy. I raised a support ticket yesterday and am currently in an email exchange with a very helpful person in support but no luck in finding a solution.

I'll keep persevering - next step is to start removing software that often causes issues (Citrix) and programs I hardly ever use to see if one of those is causing it. I strongly suspect that this is not a Frontier / E: D issue, but is more than likely being caused by my version of Windows (20H2 build 19042.746) and something to do with the .NET / .NET frameworks I have installed.
 
Last edited:

Thanks for posting that. I've been through pretty much all of those options with the exception using the an 'alternative' launcher or reinstalling Windows. Given the PC in question is also my main "work from home" PC (hence my sole source of income!) I'm going to have to pause on reinstalling Windows for fear of breaking something else that stops me earning!

So I'll look at trying to use an alternative launcher until this is fixed. Thanks for the link once again.
 
Last edited:
Thanks for posting that. I've been through pretty much all of those options with the exception using the an 'alternative' launcher or reinstalling Windows. Given the PC in question is also my main "work from home" PC (hence my sole source of income!) I'm going to have to pause on reinstalling Windows for fear of breaking something else that stops me earning!

So I'll look at trying to use an alternative launcher until this is fixed. Thanks for the link once again.

Yes, unfortunately as of today the only known working solutions for this issue are either using a custom launcher or reinstalling windows.

Btw, there is definitely something messed up in Windows when this issue appears, in my experience you will probably have a similar issue with the DayZ launcher and maybe other game launchers based on the older .Net frameworks. I believe this is due to a conflict with installing/updating the VisualC runtimes but I was not able to identify the root cause or revert it.

Let me know on reddit if you need a link to the the recompiled launcher.
 
Do you have another drive bay you could boot from... with another SSD or HDD
IS this a TOWER PC with extras drive bays or LAPTOP with USB expansion only...
IT may be a pain but if you realy want to play again... you could Dual boot with a brand new Windows install and a NEW install of Elite Dangerous on a seperate Drive and not touch the work from home SSD windows version...

Yes this does mean that you are forced to reboot every time to play..
but this also stops anything you install for work breaking games that use IE as a launcher shell..
 
That takes me back a few decades to booting into DOS to play a game. :)
Dual boot shouldn't be too bad on SSDs.
keeps you honest in these work from home times as well ... Hard to skip work when you have to dual boot to play the latest games...
Untill you work out Geforce now runs steam/epic games in chrome... lol and has free 1 hour play slots... Of course im working boss you only paid for dual core lap top can not play good games on that ;) ...
Screenshot_20210110_232258.png
 
keeps you honest in these work from home times as well ... Hard to skip work when you have to dual boot to play the latest games...
Untill you work out Geforce now runs steam/epic games in chrome... lol and has free 1 hour play slots... Of course im working boss you only paid for dual core lap top can not play good games on that ;) ...
Pretty impressive 👨‍🚀
How do you explain "Friendship drive charging", on zoom calls? ⛈
 
Pretty impressive 👨‍🚀
How do you explain "Friendship drive charging", on zoom calls? ⛈
You got to be on top game, Directional boom mic not webcam mic. (y) wont pick it up... 😛 hence the wireless RF headphones avatar...
bg,f8f8f8-flat,750x,075,f-pad,750x1000,f8f8f8.jpg
...
b458b033abc0803901208be82db356dc

edit = and yes can go the bathroom without the coms dropping out if you wish...
 
Last edited:
You got to be on top game, Directional boom mic not webcam mic. (y) wont pick it up... 😛 hence the wireless RF headphones avatar...
bg,f8f8f8-flat,750x,075,f-pad,750x1000,f8f8f8.jpg
...
b458b033abc0803901208be82db356dc

edit = and yes can go the bathroom without the coms dropping out if you wish...
It seems that you have covered all the angles. :D
I don't use headphones. I'm too scared the boggieman will creep up behind me.
Then it would take me ages to clean up the mess.
There are some men things aren't meant to know. 😖
 
UPDATE:

Hi, as of today I found out what was the source of the issue that was causing that same error in my ED Launcher.
The issue was caused by a color management configuration setting that somehow was automatically updated during the install procedure of some Windows update.
As suggested here: https://stackoverflow.com/questions...e-data-generated-an-overflow-during-processin in the first answer I reverted all my color management configurations to "System Default" and restarted my PC and this solved the issue for me.
I can now successfully use the default unmodified ED Launcher.
So you may want to try the same and go back to use the default ED Launcher...
 
UPDATE:

Hi, as of today I found out what was the source of the issue that was causing that same error in my ED Launcher.
The issue was caused by a color management configuration setting that somehow was automatically updated during the install procedure of some Windows update.
....

Thanks. Fixed it for me too. In the years since I last played ED I'd added a new monitor that was using it's own colour profile - setting that back to system default has allowed me to use the official launcher again! Who'd have thought a simple colour profile interfering with a 50x50 .PNG file could have caused all these issues!

Thanks again for finding and posting the fix!
 
UPDATE:

Hi, as of today I found out what was the source of the issue that was causing that same error in my ED Launcher.
The issue was caused by a color management configuration setting that somehow was automatically updated during the install procedure of some Windows update.
As suggested here: https://stackoverflow.com/questions...e-data-generated-an-overflow-during-processin in the first answer I reverted all my color management configurations to "System Default" and restarted my PC and this solved the issue for me.
I can now successfully use the default unmodified ED Launcher.
So you may want to try the same and go back to use the default ED Launcher...
Thanks so much this has fixed my launcher issues after days of frustration.
 
Back
Top Bottom