Command Window on Launch of Game

I’m not disabling it as I use it. It shouldn’t open when launching a game from ea desktop. I didn’t have this issue when using the beta ea desktop. Since ea desktop is a step backwards in its current state I’ve reverted back to origin 

@evlsmurfYou changed default terminal application, that why you have command prompt terminal get update some time ago. anyway this is issue with windows terminal not with ea app it can be deduced that if you are using "windows console host" it doesn't have this problem ;-)
https://i.imgur.com/cG8HmLz.png 

No seeing how it that a problem with using Terminal rather than basic Command Line, as closing them works exactly the same.

Even if there was a need to run something through console (not sure why though, Origin does not need to do that), whatever command it being passed send an exit command afterwards.

Whatever EA Desktop is sending to the command line needs an exit command like @Aries_cz mentioned. Nothing on my computer changed when i went from beta to release versions of EA Desktop. This never happened prior to the Release version.

@Aries_cz  Because ea app is 64 bit and origin is 32 bit ;-) and need special thing to work backwards for older games ;-) 

@evlsmurf I suspect that you either change something in the "Windows Terminal" yourself or that windows decided on this 😉

@ZjemCiKolege that makes zero sense considering its BF2042 being the one of them 

@ZjemCiKolege ok so after some digging around the BF2042 launcher exe aka "EasyAntiCheat Launcher" is 32bit which is when the cmd windows comes up, but BF2042 does run in 64bit. Hoping this issues is resolved at some point in the future.