I have succeeded in getting rid of the 2047 error but with an “important” cost:
I have deleted the cloud server data. Consequently my logbook is back to zero and the devices and input setup. Maybe the same for the career mode. I will see that at the end of the beta.
So if, like me, you are not bothered to reset your logbook here is the explaination:
Close Microsoft Flight Simulator 2024
In the search box, type “CMD” then select “Open” to open a Command Prompt
In the window that appears, copy-paste the following command:
Running your suggested shell results in “Windows cannot find shell:appsFolder\Microsoft.Limitless_8wekyb3d8bbwe!App -DeleteCloudSaves”
My Win 11 25H2 FS2024 1.6.22.0 system contains one folder with the name
Microsoft.Limitless_8wekyb3d8bbwe. Within that folder I find only the LocalState folder. Within LocalState I find the only WASM folder. There are two folders in WASM: MSFS2020 and MSFS2024. Within MS2024 there is a folder for an addon and nothing else.
I ‘sorta understand the shell:appFolder… as being only a virtual folder and it really just pointers to application folders. But I can find nothing on the system indicating that it has anything to do with a CloudSave.
When I run shell:appsFolder it does find the FS2024 app and opening that app runs the app.
I use the Everything app to search all drives for a folder containing the name Microsoft.Limitless_8wekyb3d8bbwe which is in C:\users\userid\AppData\Local\Packages
OK, if you go to your run command and enter ‘shell:appsFolder\Microsoft.Limitless_8wekyb3d8bbwe!App’ what happens?
On my system it starts up MSFS2024.
So therefore if you go to the run command and type “shell:appsFolder\Microsoft.Limitless_8wekyb3d8bbwe!App -DeleteCloudSaves” then it stands to reason that the game will start WITH the additional parm that you want to run.
If you are not sure try the first command to prove that it starts. Then you can shutdown and do the command that you want.
Been There - Done that - first sim session after delete works OK with no errors. Every session after the first gives the cloud error.
Just followed your suggested method and then verified \2537590 was deleted.
When I started FS2024 I received the 2047\Cloud Save error prior to the home screen loading. The I got the same error every time I switched screens in the sim.
As I said above - using my method resulted in five sim sessions in a row with no error and then in the sixth session it started again.
I did the steps I listed in the post above and had several days of good sim sessions with no Cloud Save errors. All my settings and input profiles were restored to just as they were prior to my -DeleteCloudSaves as described above.
This evening I downloaded 1.6.23.0 and the first thing it said to me when I started in under Steam was 2046 Cloud Save error.
All my custom profiles are still in place and can be selected but their settings have changed. My sim settings changed in places but stayed the same in most. For example, all the visual assist AI piloting options had been turned on in the update.
And I cannot save the new custom profile settings because everytime I try to save I get the 2046/Cloud Save error.
Things were working perfectly in 1.6.22.0 and now the sim is almost unusable again.
I don’t want to jinx it, but it looks like I’ve fixed the 2047 error by deleting some of the control settings preset saved. I’ve relaunched the game three times, and the issue hasn’t come back. I’ll keep you posted if it does. I had created quite a few — basically one for every aircraft I’d flown — even though most of them were essentially just identical copies with no real differences. Who knows whether the issue was caused by having too many of them, or if one of the deleted files had somehow gotten corrupted during an update or while switching between the official and beta versions…
After reading Albigheros76’s previous message, I also deleted my control settings preset (control profile). I had about ten profiles that I was able to list using the “MSFS Control Profile Backuptool” utility (flightsim.to). After restarting MSFS once or twice, the utility confirmed that I no longer had any custom control profiles.
I was then able to try a few flight sessions and error 2407 disappeared (whereas the error 2407 had been displayed systematically since yesterday with the new Beta 1.6.23.0 version).
If other simmers can try this and confirm that it works to get around (permanently solve?) the problem, please let us know in this thread.
Note: I saved my various profiles using the “MSFS Control Profile Backuptool” utility, but I chose not to restore them to be sure I didn’t reintroduce corrupted configurations. I preferred to recreate the 3 or 4 control profiles that were important to me.
finally I did the cloudsave reset and it works well now after meanwhile 30 restarts of MSFS2024 SU4. Fortunately I took screenshots of all my controler settings before, because the reset with the MSFS Control Profile Backup Tool did not work. It took me around 2 Hrs but the Sim is running a lot better than before.
I did the reset in SU3, then I uninstalled the sim and reinstalled it with the beta SU4. Some work to do, but it was worth it. Anyhow I wish there is a much easier and less time intensive solution out there.
Oh lordy. I opted back into the beta, thinking it must be stable by now, after opting out at the start, and I immediately hit this issue.
Do y’all find the XML export/import built into the sim for control profiles works okay? I just exported everything, and if it reliably will re-establish my control assignments I could just delete the cloud saves rather than reverting to SU3.
Deleting my control profiles is not a viable option. I have a Winwing HOTAS setup and MS’s lack of support for it means every dang button/axis/etc. would have to be rebult. It sounds like the third-party control backup tool couldn’t be trusted…
[EDIT: Reverted to SU3 again. I thank you all in the name of flight sim players for the beta service that you do.]
The few people I have dealt with in this regards found that the sim will ask when you restart it.
Deleting the cloud save did not wipe out the sim settings that were in the local files, and as mentioned, the sim asked which they wanted to use.
If you also exported them, I would think you should be safe.
However like a lot of things, particularly these sims, your results could vary!
The problem started after selecting the PMDG 777. During taxi, takeoff, cruise, and landing I noticed a very slight stutter every few seconds - barely visible, but still there. After landing at EPKK I taxied to the apron and returned to the main menu. Right after that, a cloud-save error popped up, and I’m pretty sure that this sync issue was the real cause of the micro-stutters, not the PMDG 777 itself.
To ask quite modestly, is there any intention to fix the error at all?
If so, when can the community expect a solution?
OR should this problem simply be ignored?
Please don’t misunderstand my questions; they are not meant to be offensive or provocative in any way, let alone discriminatory.
These are questions that simply interest the community.
They are questions that also concern the future of many frequent flyers.
AND, as a good company, it might be nice to provide answers to these questions.
AGAIN:
Please do not misunderstand my questions; they are not meant to be offensive or provocative in any way, let alone discriminatory.
I get this 2047 error now when I start up post-SU4-update MSFS today. Is the solution people have found seriously just to reset all cloud data? That’s not an option for me due to extensive control bindings across a dozen or more peripherals. Surely there must be some other fix
I have the same problem, probably no solution except for complete reset. But I think if you backup the wgs folder from \AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\SystemAppData\ then you can have all the bindings back. Maybe backup UserCfg.opt from LocalCache folder as well for the graphics settings.
