Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
No
Have you disabled/removed all your mods and addons?
Yes
Brief description of the issue:
Won’t run MSFS straightaway, requires numerous attempts to get it to run.
Provide Screenshot(s)/video(s) of the issue encountered:
Detailed steps to reproduce the issue encountered:
When I start up MSFS for a new flight, it goes straight to the desktop. Try again - gets to the white screen. Try again, gets past the Asobo screen after a few attempts. Try again, gets past Blackshark (?) screen. When it gets to to the copyright it’s fine. It normally takes about 10 attempts to get to this stage.
If I then restart MSMS, it’s fine. The next day after shutting the PC down, the problem re-appears.
I have re-installed MSFS twice and it runs fine after I’ve finished the installation. The next day, back to the same issue. I have also tried with an empty Community folder - no effect.
The thing is that it happened all of a sudden, and I hadn’t done anything recently to MSFS.
Many issues may be due to an outdated graphics card. Please state your Graphics Card Driver Manufacturer (NVIDIA, Intel, AMD) and Version (Learn how to find your current graphics card driver version):
NVIDIA GeForce GTX 1080 Ti - Driver 31.0.15.2802
PC specs and peripheral set up:
If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:
Build Version # when you first started experiencing this issue:
The one just prior to this week’s update.
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons: