Forum Discussion
Hi everyone,
We appreciate the reports on this. We'll pass this along for a look.
Please change the default terminal application as windows console host (as the photo). This will fix the problem.
The problem exist with the default option : let windows decide.
- 3 years ago@Frozenoulis This did fix the issue. Or at least remedy the situation. Not sure why this was a new bug that cropped up, but changing this option made it not show up any longer. Thank you!
- 3 years ago
@Frozenouliskindly please tell us how exactly you came to that settings page?
- OnSync3 years agoSeasoned Adventurer@SturmGraz Go to settings and search terminal settings.
- 3 years ago
Hi all,
I have the same issue. When starting BF 2042 - a second window opens - looks like a .cmd tab but yeah it is Terminal - session.
Changing the settings form "let windows devcicide" to "Windows Console Host" as proposed before solved the issue on my side.
Game works fine and the Powershell window doesn´t open anymore.
How to get to these settings: (Win 11)
Press the start button and type Terminal in the search area
In the Terminal app there is a drow-down arrow ( next to the "+"--sign for a second tab)
Select "settings" and there change from "let windows devcicide" to "Windows Console Host".
Save and thats it.
Now what I am asking myself:
Does this impose any risk on my PC:
Is this game now run in a 32 compatibility environment?
Really?
Any further comments are highly appreciated.
THX & Good Luck
Hawks
- 3 years ago@Hawks2063 Thanks!
I selected the 'Never' option under the 'Background App Permission' tab and it doesn't open up!
- OnSync3 years agoSeasoned Adventurer
@FrozenoulisThis fixed the issue. Cheers mate!
UPDATE: I noticed that changing that setting makes BF2042 unplayable. It can load the game just fine, but going into match makes it crash/freeze.
About EA app Technical Issues & Bugs
Recent Discussions
- 4 hours ago
- 6 hours ago
- 7 hours ago