After reading your post I checked the Microsoft Store app and saw that there was an update to the gaming services app this morning. The update was just 25.35 mb but took really long to download and install. In any case after update was complete, I tried MSFS 2024 and it all seems to be working fine again. Thanks for pointing this out. It is amazing that not having this one simple thing working properly really made the sim erratic and unplayable for the most part.
Thanks
Similar issue here. gaming services keeps crashing. click free flight and flight sim crashes.
was working fine Friday.
I have exited PC Gaming and did a repair on gamingservices. Had a three cycle update this morning for windows 11. (3 cycle meaning that a warm restart was automatically done 3 times as it counted up to 100% install)
I have the same problem this afternoon. I reinstalled and got a very strange set up, there was no configure button when selecting an aircraft, had to use escape to change any screen and apart from getting error 2407, every time it would CTD.
I reinstalled again and the same.
I have tried deleting cloud saves using CMD, emptying streamed folder, and restarting PC. It’s not working.
I saw a post regarding opening MS Store and clicking on Library then clicking on updates top left, hut, I don’t see that so assume I am up to date
It definitely seems to be some kind of bug. My gaming services had an update but it might not be the same for everyone. Whatever the problem is it caused the sim to behave very erratically. I hope they can sort this out before the release of sim update 5.
Delete the gaming services app from the Microsoft store and it will automatically restore, it worked for me,
My MSFS 2024 has been working since the gaming services app updated as I mentioned in my earlier post. Thanks again. In case it happens again I can try the delete and re install method.
If it happens again or any other CTD issues I always go into the store and delete the gaming services app and it just automatially resores in 5 seconds …
Hi folks,
The team at Asobo have asked that those of you who believe this Cloud Save Error could be caused by a maxxed out Logbook (as @RevampedSine732 commented about in February) to send across some further information for them to review. If you believe this specific aspect could be the cause of this issue appearing for you all, please could I ask for you to send me a DM here on the forums and I’ll provide some more steps? If you’re unable to DM me for whatever reason, feel free to message the @moderators inbox and I’ll pick it up!
Cheers 
@RevampedSine732
Did you DM Chewwy94 as per the post above yours?
He had already DMed me… and…
… I replied:
As you can see, the format of that type of file is not allowed…
@RevampedSine732
Thanks - I’d suggest the following.
Let us all know if that works !
I may try this, but I will first wait for what he may suggest.
I’ve just responded to your DM!
Hi there.
I’m also getting the cloud error but in my case it’s 2047-6, since I updated to SU5. I’ve tried everything but deleting cloud saves and reinstalling Windows 11. Why should I lose my logbook doing that? How can anyone reinstall the OS to fix that?
I got error 2047 when I updated to SU4 as well, but the culprit was alexhome vfrnav. This time it arises even with an empty Community folder.
I can fly in free and career mode at least, but after dismissing a few error boxes.
SORT IT OUT!!! never mind world updates
The addon itself is not the issue, but one of the causes. It seems like any addon can potentially write lots of junk data to your logobook, and swell it to such a size that it breaks the cloud sync processes.
So we have two issues:
Issue one is only accelerating how fast we get to issue 2.
What’s more surprising is this hasn’t yet been logged as an actual bug, considering the number of example given of how to generate the issue, and examples of the junk data written into the logbook file.
You might try a reinstall of Windows using the Windows Update method which will save your apps, files and data, as you’ve suggested. It worked for me when I had the error a few weeks ago. It resynced with the cloud bringing back the logbook and settings!
I updated to SU5 with an empty Community folder, clearing all types of caches, scenery indexes, etc., and the error arose right after loading the sim. Why do you have to do so many things to fix anything? It shouldn’t be this way. How many bugs do we have to deal with? The sim was released months ago, and it shouldn’t have been launched in that state, even with the 2020 version not fully fixed.
I own MSFS 2020 on the Xbox store, and my logbook has been reset twice because of login or syncing problems, or whatever. There are so many problems. They don’t install the sim like every other company does; they hide folders and restrict normal access, writing, etc. I regretted the purchase, so I got the 2024 version on Steam despite the price. And here we are, trying all kinds of things just to keep it running.
This is not fair.
