Forum Discussion
with the 1.09 patch the game won't start. It crashes everytime as soon as I press "any button" to get from the splash screen to the main menu.
- jenny_a_m3 years ago
EA Staff (Retired)
@Logoo69 wrote:
with the 1.09 patch the game won't start. It crashes everytime as soon as I press "any button" to get from the splash screen to the main menu.
For @Logoo69, and all those experiencing this issue, could you try these steps, the first one especially, and let us know if they fix the crash you're experiencing?
- Update your Windows to the latest update - on Windows 10, you can do this by going to the Start button, and then Settings > Update & Security > Windows Update, then click 'Check for Updates'. You can find out more about this here.
- Make sure your graphic drivers are up to date.
- Delete your hardware config file for F1 22 - this is typically located here: Documents\My Games\F1 22\hardwaresettings\hardware_settings_config.xml
If you could try those and let us know how you get on?
- 3 years ago@jenny_a_m For steam deck? Steam Deck not use windows but linux (proton) Any solution for this?
- 3 years ago@ringhio992 I tried to delete: Documents \ My Games \ F1 22 \ hardwaresettings \ hardware_settings_config.xml
On Steam deck but the game still crashes. Help!
- Apophis-STR3 years agoSeasoned Ace
@jenny_a_mHello, could you please give us an update on whether the team is still working on a solution for this issue? or are they gonna leave it be because it might not be a direct issue with them since it's related to windows update?
There're many people's system being plagued by the windows 10 update error (0x80073712) and some reported that they were unable to update it even after reinstalling windows, so this might-be-solution isn't really a realistic option for a lot of them.
If the game never had worked then it's our fault for not testing with the demo first before purchasing, but the problem here is that it worked perfectly fine all the way until to the newest patch, in this case there must be something wrong on the dev team's side when they were doing the patching, the responsibility shouldn't be weighing on the user.It's been 6 days, folks...