Yep, in my opinion the fix was absolutely not that given here, I was doing all of that whilst having the CTD’s, then they just stopped.
So who knows what it was, I suspect something not on our side.
Perhaps something came down from the Microsoft Store packages (nothing to do with MSFS) and isn’t really being noticed as updated by people? You can use an elevated powershell and see Get-AppxPackage –AllUsers to list them, although it is hard to find install date via that.
Other than that, normal app updates can be listed with a powershell Get-ItemProperty hklm:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* | select-object DisplayName, InstallDate.
I don’t know what fixed it, but things like Microsoft Gaming Services etc do update via the Microsoft Store and can do it without appearing in install lists. There could have been a bad interim app update, that got reverted and people are then caught in a time window where MSFS using those dependencies is broken (or rather susceptible to a crash now, even using a live service moreso). An update could have come down and the restart was just the moment it started to get used, hence the reduction of CTDs?
That would be a reasonable explanation, except that many of us are running the Steam version and there were certainly no updates installed via that. You can also check Windows update history and you can check modified and created dates on MSFS files. I’ve done all of that, and there were no updates on my machine between a CTD every flight and no more CTDs. Whatever change happened, did not happen on my machine.
Microsoft Game Services etc come down as Store packages on Windows regardless of Steam or MS Store purchases. Those packages aren’t listed in Windows Update history or the ‘Add/Remove Programs’ lists. The MS Store also often waits for a full system restart if a dependency it updated is being used, which would sort of explain what people are seeing.
“You can fool some of the people all of the time, and all of the people some of the time, but you can not fool all of the people all of the time.” I think a bit more in-depth explanation would be nice. After they return from Gamescom 
They made a great sim (to me the best one) with so many groundbreaking, innovative features. I just hope they can make the sim a bit more stable. I really like this sim.
Im pretty sure gaming service was updated last friday right around when these CTD started
So after the 28th (end of gamescom) we will have stable MSFS again, will it? Why are the servers pointed to some machines that are there? Wouldn’t that perception be outrageous?
I am getting a CTD every time I fly about 20 Km north of EGNL in UK. Tried with a fast jet but only doing 200kts and then with a CAP10 @ about half that. It seems to “not like” the scenery on the coastof Cumbria.
Gigabyte X299 UD pro + I9 9940X + GeForce RTX 2080Ti + 32Gb Corsair Vengence RAM DDR4 3000Mhz running sim on Win 10 Home premium (Rig watercooled0
Having those since 4 days, sometimes as soon as I get in the menu while other times after 10 minutes of preflight:
Faulting application name: FlightSimulator.exe, version: 1.27.16.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.27.16.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001cea644
Faulting process id: 0x1f88
Faulting application start time: 0x01d8b7eebf2d2b3c
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.27.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.27.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: fdd87a0e-efd6-4bb2-9067-5824c8c5ace4
Faulting package full name: Microsoft.FlightSimulator_1.27.16.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Anyone has any clue?
It isn’t any specific update or updates. It is the update process itself. Microsoft Windows downloads things all the time and sometimes things break that impact apps like MSFS. Running the update process even without pending updates does housekeeping finding and fixing things as needed. Nothing in MSFS was broken. It was something in Windows that MSFS uses that was broken.
Sir I have the same error as this guy and only since Saturday. I think it is related to ntdll.dll otherwise we would have had it before. We only had it starting Saturday, in my case for every single flight right now. Even tried a Windows reinstallation but didn’t work. It clearly is an issue on Asobo’s side.
If the error in your event log doesn’t report “ntdll.dll” then it is unrelated.
Having this at every single flight since Saturday. Never had a CTD before.
“is there something we all have in common?” yes probably have online services running, I had constant ctd’s so I disabled online services, ran map enhancer(Bing) and the AIG AI, did five 2 hour flights without one ctd
Ordinarily I would agree although I’m using an update blocker that will stop every communication to MS (wsus/store etc). I’ll update when it suits me thanks 
So I know 100% there was nothing updated on my PC between the sim crashing and the sim now not crashing. Do not use defender and make my own arrangements there. The update ‘fix’ was a cover that they hoped would make it appear it wasn’t msfs servers/client.
I am still seeing lots of missing scenery tiles too so something is amiss still…
They said another thing in another topic. Since a lot of people like me had this only since Saturday (never a single CTD before), they say it’s related.
That´s correct. If they really know about any update to fix the issue they would have specified which KB (which update ID) had to be applied to solve it, don´t you think? They just said “hey guys, run the updates and let´s see if we are lucky”.
The effect of missing scenery is what they are ignoring completely and I can´t really understand why. During the weekend not only the tiles but the complete scenery data was not sent by servers. You faced a completely flat area (no textures, no buildings and no terrain mesh). That was confirmed by several users. However connection to server was still alive.
I can´t understand this situation. Nobody will blame them in case there´s a server issue. Those things can also happen, even on the most reliable servers. What is important is that they debug the error properly so that it never happens again, specially when server/client communication is so critial for this game. I understand that they have to say something but giving as a result of hundreds of posts such a generic solution like the check for updates one is what is not good at all for their image because it seems as if they really had no idea at all of the reason for the error and specially when the error still happened with a fully updated Windows during the weekend.
Everyone understands that they are busy at Gamescom, which is important for their business too. Everyone would also understand that the error is analized after the event or that the error may be even caused by something they prepared just for the demos or that serverrs were just overloaded for whaterver the reason. Nobody will really care about what was the reason provided that is fixed. This is my opinion at least.
Cheers
Hey Folks, This may be totally unrelated but here is what happen over the weekend.
Had one CTD on Friday night. woke up next morning started msfs up there was an update so i updated figured it was a mandatory one. turns out it reverted me back to sim update 9. i didnt leave the beta. So i went back into xbox insiders hub on my pc and had to click the join button again. it went through downloading the beta again restarted msfs and was back to where i was when this latest update was 1.27.16 with no CTD yet fingers crossed still get out of memory issues but i know i have plenty of memory so what ever bug that is.
Which CTD thread should I be in? Crashing 100% of the time in safe mode even. First time launching the sim in several days and I’ve changed nothing.
Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program FlightSimulator.exe because of this error.
Program: FlightSimulator.exe
File:
The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.
Additional Data
Error value: 00000000
Disk type: 0