I’m having the exact same issue. When I double-click on the MSFS icon I get an instant BSOD.
My system is only one week old (12600K, Asus Z690P, 32Gb Ram, GTX1060) and Windows as well as all drivers are up to date. Last week everything was working perfectly fine. But since yesterday I can’t start MSFS without getting a BSOD. Everything except keyboard and mouse is unplugged but it makes no difference.
sounds like memory issue… or… You have hopefully disabled Fast-Start ( windows energy options ) ?
also the question ( I hope you read former posts ):
When was the latest windows updated installed ?
Thanks a lot for replying!
KB5011487, KB4023057 and KB890830 were installed last Friday. But I used MSFS without issues on Friday evening after the updates got installed. However, I just noticed that Windows Update also installed new Intel Bluetooth drivers on Friday. I have deactivated Bluetooth in the device manager for now and will report back if it made any difference.
thanks for reply. This is what currently try to narrow down : is there a relation to the windows update 
PS: Bluetooth sounds intressting too
Thank you for your warm welcome! Yeah im pretty new to the MSFS community, I moved from x plane for the time being lol😛
I have some news to share.
I believe I am now able to replicate the issue in question.
Some context:
So like I said yesterday in the morning I ran MSFS. I ran it purely to test the AIG models for vPilot (vatsim) that I had finished downloading late the evening prior
so yeah in the morning I ran msfs and vpilot to see it worked and yeah it worked as expected, I close msfs and didnt think about it till the evening when I wanted to fly again.
and thats when I realised. once I had finished testing v pilot with msfs, I simply went to the main menu and closed the sim
this is where the problems start. I forgot to disconnect Vpilot PRIOR to closing the sim, after that I just closed vpilot as it said it had disconnected automatically
however, after doing this, I get BSODS upon opening MSFS. I had no clue what could be the issue, so today I tried deleting yesterdays Windows update and reinstalling it. that made me able to actually get msfs to open. Once I opened it, I subsequently closed it upon entering the sim. then I tried opening msfs again, and yes it opened. this time I tried loading into an airport with the FBW. No problems at all
this time I tried connecting again to vatsim just randomly
then I did the same mistake.
I didnt disconnect before closing the sim, and when I tried opening the sim It gave me the same error;
so thats 1 thing clarified; something to do with Vpilot
secondly, I can fix these BSOD’s by going to the microsoft store and updating all the libraries, and I notice this error pops up when msfs causes the BSOD:
And I just checked, closing Vpilot before closing the sim still gives the BSOD.
This is really strange. im gonna report back and see if anything changes after updating all of the visual C packages.
short note: this brings another question on top… are only MS-Store users affected ? 
PS: and dont forget the sfc /scannow after a bsod
really looks like some MS store/ xbox app glitch
sfc /scannow:
after reinstalling all the C++ packages it still causes a bsod and once it restarts again and you go into the microsoft store and into libraries it doesnt even show the app and just says something happened on our end.
looks like MS store issue 99%
I found this one:
but there are older other post… may be…
Same here.
I also tried with Bluetooth turned off in the device manager, again no change. I still get the BSOD when trying to launch MSFS.
well after checking my VCC again, I open msfs and BSOD once again
going into microsoft store and library and now I dont see any errors, 2 times already
so I think I fixed the download errors, but why wont msfs open now again
What happens when you retry?
intressting would be wether the other users with the BSODs see the same update error… then at least we have a common ground.
@viiaero7 I see the same issue in the MS Store with the C++ that you are having after a restart.
I retry, the error goes away and then I click get updates and it says no errors
then I restarted my pc and a few more visual c++ errors popped up
I clicked retry all and msfs works again
So opening msfs, not connecting to vpilot, then closing it, then trying to open it again works
but as soon as you disconnect from msfs after using vPilot it messes up the C++ and because of this I get a BSOD.
looks like a MS store problem to me- something bugs out the Visual cc stuff and in my case its vPilot
do any of you guys use vpilot and AIG models?
we could be having the same problem but triggered by different things
I think at this point its pretty safe to say its not hardware related-But VCC and MS store related
reading some MSFS reviews on the MS Store also indicates that some people have had this problem like in november last year so I think we can eliminate that its related to a sim update
Its most likely a Microsoft Store bug- I might try reinstalling it completely
Or its a Microsoft update bug but thats less and less unlikely
have you already disabled Fast-Start ( energy options, what should happen press power button ) ?
no, why?
I dont think it should be a problem really.
