Application Failed To Start
- Thread starter Saool
- Start date
try running the launcher with admin rights.
it shouldnt need too be, but in the past i have had too run it this way for it to work.
it shouldnt need too be, but in the past i have had too run it this way for it to work.
i have the same problem and nothing helped so far... where you able to solve the problem?
there is an issue with the windows 2004 update what ver of windos r u using could be that( American style date)
type winver in start box
type winver in start box
Hey STRONTIUM DOG,
my Windows 10 Version is indeed 2004 (Build 19041.572)
what should i do? :O
my Windows 10 Version is indeed 2004 (Build 19041.572)
what should i do? :O
If it is less than 10 days since the update to 2004 you can revert to your old version easily via 'Settings\Update\Recovery then if available "Go back to previous" '. If more than 10 days then I have no idea - maybe you need to reinstall windows 10 or maybe a "Reset this PC" - https://www.howtogeek.com/675411/how-to-uninstall-windows-10s-may-2020-update/ and https://www.howtogeek.com/132428/ev...t-refreshing-and-resetting-your-windows-8-pc/ might help.
MSFS 2020 users have reported issues with 2004 and suggested reverting or installing a version 1909 iso file - googlify is your friend I suppose.
P.S. I did a thread about how to stop the update if you are on W10 pro - https://forums.frontier.co.uk/threads/the-dread-windows-version-update.556421/
its more than 10 days. i actually dont have the time to reinstall windows 10 atm. i tried updating the windows version to 20H or something but it still wont start the game... i guess ill wait and try again after my exams. no gaming for now it seems 
but thx for help anyways!
but thx for help anyways!
sorry as para advised revert roll back or refresh
I just heard others cmdr having a lot of hasstle with it so I did what para advised an halted
big updates and have just stuck to sec patches
hope fd find what the issue is and resolve it
it seems there are 2 versions of 20/04 out according to redit American/and the other plebs ver
one works with elite according to some and another ver don't?
I haven't the foggiest if the 10 day thing has past
what some advised is disabling net framework from what I remember of it so could try that for different versions maybe
I just heard others cmdr having a lot of hasstle with it so I did what para advised an halted
big updates and have just stuck to sec patches
hope fd find what the issue is and resolve it
it seems there are 2 versions of 20/04 out according to redit American/and the other plebs ver
one works with elite according to some and another ver don't?
I haven't the foggiest if the 10 day thing has past
what some advised is disabling net framework from what I remember of it so could try that for different versions maybe
- Browse out to Programs and Features in Control Panel.
- On the left side, click on Turn Windows features on or off.
- Click the + symbol next to .NET framework 4.6 Advanced Services.
Last edited:
I have the same problem
I play on Win10x64
What I did with the help of Google:
- Reinstalled all kinds of libraries from DX to c++
-According to one of the tips, I tried to reinstall only the launcher separately
-Changed lines in configs
-Reinstalled the game from 0
-turned on and off the services responsible for window processing
-did a BACKUP UPDATE of WINDOWS under 0 with all the following
Nothing helped, the error both crashes and crashes without the ability to play.
I play on Win10x64
What I did with the help of Google:
- Reinstalled all kinds of libraries from DX to c++
-According to one of the tips, I tried to reinstall only the launcher separately
-Changed lines in configs
-Reinstalled the game from 0
-turned on and off the services responsible for window processing
-did a BACKUP UPDATE of WINDOWS under 0 with all the following
Nothing helped, the error both crashes and crashes without the ability to play.
I found this on Steam forums. Might be worth a shot.
steamcommunity.com
PSA: DO NOT UPGRADE TO Windows 10 v2004!! Stay with 1909 or 1904 (check by hitting Win-R > winver > Enter)
v2004 totally destroyed folder sharing on my work network. All older shares (Linux, 2003 server) stopped working.
Imagine my headache. FU-Microsoft.
X.
Cant Start Up ED: Cobra Window Error :: Elite Dangerous General Discussions
So, I just bought Elite Dangerous for 40$ to download it over night, only to wake up to this error message --------------------------- Application Failed To Start --------------------------- Internal error creating window: Failed object initialization (ISupportInitialize.EndInit). Could not load...
PSA: DO NOT UPGRADE TO Windows 10 v2004!! Stay with 1909 or 1904 (check by hitting Win-R > winver > Enter)
v2004 totally destroyed folder sharing on my work network. All older shares (Linux, 2003 server) stopped working.
Imagine my headache. FU-Microsoft.
X.
that's strange
found this on redit
Hey CMDR.
This specific exception (it's .NET related) has been reported a few times and looks to be an issue with some installs of Win 10 after updating to 2004, primarily Insider versions. Build 10.0. 19041 is in fact Ver. 2004.
It causes a problem for the ED launcher that no amount of reinstalling and fixing .NET ever resolves.
Unfortunately, the only sure fire fix I've seen so far is an OS reinstall, but if the update to 2004 was recent, you may still be able to just roll this back instead.
Likely not what you wanted to hear, and I apologise for the grim news.
We're still looking into any possible way we can re-work the launcher to accommodate this fault, but I'm afraid there's been no progress no that so far.
-Luna
HEY @Support Luna any update on this as it was posted in june
as I would like to update my windows 10 OS sometime this year!
at least make this abundantly clear to new users during the installation process as first impressions do count
and it's just not pleasant to be greeted by "cant open a window cos I am in the loading bay in my cobra"
or words to that effect
found this on redit
Hey CMDR.
This specific exception (it's .NET related) has been reported a few times and looks to be an issue with some installs of Win 10 after updating to 2004, primarily Insider versions. Build 10.0. 19041 is in fact Ver. 2004.
It causes a problem for the ED launcher that no amount of reinstalling and fixing .NET ever resolves.
Unfortunately, the only sure fire fix I've seen so far is an OS reinstall, but if the update to 2004 was recent, you may still be able to just roll this back instead.
Likely not what you wanted to hear, and I apologise for the grim news.
We're still looking into any possible way we can re-work the launcher to accommodate this fault, but I'm afraid there's been no progress no that so far.
-Luna
HEY @Support Luna any update on this as it was posted in june
as I would like to update my windows 10 OS sometime this year!
at least make this abundantly clear to new users during the installation process as first impressions do count
and it's just not pleasant to be greeted by "cant open a window cos I am in the loading bay in my cobra"
or words to that effect
i made a clean reinstall of windows 10 OS like the frontiersupport told me. Problem is now solved and i can nerd-around again. o7
Last edited:
Oh great. I was hoping to do a clean install of ED. I removed it, then realised I could not download the launcher anywhere (what changed)? SO it looked like I could not play Elite again without repurchasing via Stream?
However I managed to find an old launcher install but still get the same error when I try to run it.
I don't think I have the will to do a full system re-install right now.
However I managed to find an old launcher install but still get the same error when I try to run it.
I don't think I have the will to do a full system re-install right now.
direct download
direct download:
If you bought via Frontier then you should be able to see the download in your frontierstore.net account under "my downloadable products".
direct download:
If you bought via Frontier then you should be able to see the download in your frontierstore.net account under "my downloadable products".
In my case the error was caused by a color management configuration settings. Go into your "Color Management" settings go to "Advanced" and make sure all profiles options are set to "System default...". I know it sounds strange but it worked.
