Thank you for the post. Good stuff.
I also have a routine similar to yours but I didn’t know about Reliability History. Just checked it out and will incorporate into my startup flow.
Thanks again!
Thanks for your feedback. I imagine that there are a few more industrious folks in this forum who could probably write a macro to do these things for me.
But to be honest, this routine kind of helps me to wake-up in the morning while getting through that cup of coffee.
Yeah, that is obviously not a CTD… are you trying to run MSFS as Administrator? If so, there was a topic stating not to do so because it will cause that exact error - post update if I recall.
Not sure why people are going out of their way to do so, especially when the administrative user does not have access to the MSFS application folder without modifying its security properties by design.
1 Like
huh. In 20H1 i see splash screen every time when i run MSFS.
After updating to 21H2, SSplash screen is gone =|
Haha you’re a lucky man, you fly on your work PC ! I’m not allowed to do that 
industrious rules..
Yes noticed it this morning after rebooting as well
Good for you! 
There are literally hundreds (if not thousands) of us not quite so lucky…
I don’t quite understand why some simmers get the new splash screen and others don’t ? same platform ie MS Store, same build hence 21H1, same .NET framework update… yet no chance.
Thanks, I suppose…
Many of which are caused by the user - modifications, unstable overclocking and XMP profiles, less than idea hardware, overheating laptops, overall system health, VR compatibility issues, input device conflicts, or something as simple as maxing out all MSFS settings in 4K on low-end hardware.
Not to make it sound like the game is perfect of course, it is anything but, same can be said for its users.
1 Like
LOL!
I’ve been retired for 12 years!
2 Likes
Actually, I was not the one who first raised the issue in this string. I was only trying to confirm it.
I have my properties set in the .exe file to always run MSFS as Administrator. It’s been that way for the past several months, and it remains so. I haven’t modified any security properties.
I did not receive that error dialog box until I tested the original submitter’s claim that they are unable to run MSFS as Administrator from the context menu. As you too, pointed out, they are correct.
BTW, I have not had a CTD since last August when I rudely learned the hard way that I needed to turn my virtual memory back on. LOL
Intel I7-7700 2.8GHZ
nVidia GTX 1050ti
16GB Ram
250GB Samsung NVME C-drive (MSFS)
I make films and continuity matters so I appreciated your observation! 
1 Like
Rule Number One in UI development:
If it doesn’t DO anything, Get RID of it.
I thought we got over all that by eliminating the “Press any key to continue”.
Why do we need yet another intro screen? Do we need YET another option to bypass this latest splash screen?
For me, the startup load process bar tells me everything I need to know until the main menu appears.
1 Like
I am happy we have a “Splash screen”. Now I no longer have to doubt myself if I clicked the FS2020 icon twice or not, and just sit there waiting to see if the sim actually loads or not.
But for those that see it as an “inconvenience”, I am sure someone will find a way to bypass it.
1 Like
I updated to 21H2 this morning, and then rebooted my computer.
Splash screen showed right after I double clicked the FS2020 icon.
Rebooted three times. No splash =\
1 Like
Then you’re a VERY VERY lucky man!!! Or, blessed instead of lucky, depending on your take on it😊
Just a quick follow-up regarding the use of -fastlaunch.
I’ve had a couple of more hiccups intermittently today using the -fastlaunch option. It also happened once yesterday.
During the start-up process I received an error box telling me that it could not connect to the content servers.
After further investigation it appears like I might have lost my Windows Store connection to my account. There were no reported outages for the servers or any of the Windows Store game resources.
So, I re-started without the -fastlaunch option and it started up normally.
I suspect that there is some kind of secret hand-shake going on with the Windows Store and account verification during the splash screen cycle. Accordingly, I’m staying away from the -fastlaunch option, at least until I hear something differently.
Here is more detailed information from the Zen Desk regarding my symptoms:
Access to the content servers is currently unavailable error message (Microsoft Store version) – Microsoft Flight Simulator Support (zendesk.com)
I think in your case scenario, it was just coincidental. I, and many others have been using the -fastlaunch switch either via a shortcut or by launching via Addon Linker with no problems.
Your issue assuredly lies elsewhere. I sure hope you can track it down. I know how frustrating this game can be at times.
1 Like
I updated to 21H1. Got the splash screen. Restarted my PC. Is now gone. 