CTD after exiting the Beta and reverting back to last stable

Yeah, I got back in via re-opting back into the beta. Managed to load into a little flight this time, seems a bit more tempermental at the moment (same settings as pre-beta), I’ll see if there’s any official word before I do a full reinstall, as it takes an age on my system :weary:
It must be something to do with some files being left over from the beta, stopping us from reloading once we’ve opted out.
At least for me, there was a 1.2gig download in the store, a very quick update on the loading/“checking for updates” screen, and then some updates on some of thr world update downloads…
But opting back out, I’m only getting the 1.2gig download in the store - then it CTD before the loading screen…so in theory, its trying to load but finding some things that arent meant to be there :man_shrugging:

Yup. MSFS his horribly bad at deleting content so that probably whats wrong. Im doing a fresh install now but had to find hidden folders and delete them manually since steam doesnt properly uninstall the game, it only uninstalls 1.2 gigs of it. Not joining the beta again, lol

Same here.

Hi, may I make a suggestion that you add an optional step (in the beta opt-in instructions) to backup the official packages folder. I believe that would help avoid a full download/reinstall in most cases. The user could simply opt-out, refresh the app, then point it to their backup packages folder during setup.

Edit - I guess this would only help on PC though.

2 Likes

Good idea, unfortunately too late for me.

1 Like

:wave: Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

No

Brief description of the issue:

I noticed that SU10 was causing visual issues with the PMDG 737-700 cockpit, so I reverted out of the SU10 beta and ever since when I start up the game it gets halfway through the loading screen then CTD with exception code 0x80000003
Edit: I started the sim in safe mode, same CTD happens

Provide Screenshot(s)/video(s) of the issue encountered:

Detailed steps to reproduce the issue encountered:

Opt into Su10 beta, load into the PMDG 737, exit FS2020, opt out of the SU10 beta, then start flight sim.

PC specs and/or peripheral set up if relevant:

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

1909424128218737502, type 4

Build Version # when you first started experiencing this issue:

After opting back into 1.26.5.0


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Yes, I was getting strange CTD during SU10 beta, tried to opt out, now it CTD’s on launch.

Provide extra information to complete the original description of the issue:

Have also tried a full reinstall, as well as deleting community folders etc. Must be something lurking somewhere.

If relevant, provide additional screenshots/video:

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

Same Fault, Fault bucket 1909424128218737502, type 4,
Problem signature:
P1: FlightSimulator.exe
P2: 1.26.5.0
P3: 00000000
P4: FlightSimulator.exe
P5: 1.26.5.0
P6: 00000000
P7: 80000003
P8: 0000000001cbc4c2
P9:

Yes, Steam, full reinstall, so nice to see players in the sim again, the amount of people “excited” for the new thing is quite low.

Trying to get back after a beta uninstall. (Xbox Insider hub). CTD everytime. Safe/standard mode startup, no updates check, showing latest world update and activities…ctd (after about 50% on the progress bar).
Would really like to get multiplaying again! (Not many beta payers out there). Praying for a fix, after all i was only trying to help debugging the beta for the new update (10). Regards Sean768

ON the PC with Steam I unfortunately went full reinstall.

Kills the better part of a day. :frowning:

Same here - on steam - CTD every time once I exited beta. I joined but did not know that this means in beta cannot use multiplayer with our friends anymore (unless they all are also go to beta verwsion). Reverted back and CTD every time no matter what.

The beta announcement sounded like we can easily revert back.

Had to do full reinstall.

I think future beta should be clear that:

  1. Multiplayer in beta is only for those in beta. You will not be abel to see other non-beta multoiplayer users.
  2. You will CTD if you exit beta.

Do you have the same issue if you follow the OP’s steps to reproduce it?

Yes

Provide extra information to complete the original description of the issue:

When I installed SU10, MSFS updated a bunch of packages. Unless I missed something, reverting back to SU9 did not result in any packages updating. Starting MSFS resulted in a CTD before I ever got to the menu.
The net result is that I had to completely reinstall the sim, including my entire Official folder. Reinstalling the sim by itself did not help: The only thing that worked was deleting my entire Packages folder and reinstalling that, too.

If relevant, provide additional screenshots/video:

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

No fault bucket given, but here:
Faulting application name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000
Exception code: 0x80000003
Fault offset: 0x0000000001cbcd92
Faulting process id: 0xd30
Faulting application start time: 0x01d89fc0518abbf1
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: f04c6af9-0181-4288-8017-f683417cf5ca
Faulting package full name: Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

1 Like

Do you have the same issue if you follow the OP’s steps to reproduce it?

Yes. Just did the same, reverted to SU9 and CTD on loading.
However, I was using the Steam process as specified here: [READ FIRST] Welcome to Sim Update 10 BETA but the end result was the same. CTD halfway through loading the sim.

Provide extra information to complete the original description of the issue:

It looks to me like the update check after reversion to SU9 isn’t working, and it leaves SU10 specific content in place which I think is what is causing the CTD on loading. If their update check worked properly and redownloaded the SU9 content then you would not have to do a full reinstall, which is just a ridiculous thing to have to do.
Why can’t they fix this? They have a high priority beta underway, but people can’t easily switch between them.
I reverted back (back actually!) to SU10 Beta and all is working ok.
That would probably be because the content matches the executable…

I believe the issue is related to settings stored on the cloud. I had two copies, one Steam at SU9, and one Store at SU10. They both worked at one time, but the other day the Su9 copy just would not start. I enrolled in the Beta in the Su9 copy, and the sim started. However, it looked like it was picking up my settings from the SU10 copy. I had vsync on in the Su10 copy but not in the SU9 copy. During the update of the SU9 copy vsync turned itself on. After the update was finished, it turned itself back off.

This has at the time been a one off as Steam is usually quite proficient.

No need for a second thread.

This has at the time been a one off as Steam is usually quite proficient.

I have no idea what that even means. This isn’t even a Steam problem, it’s an MSFS installation issue during the loading phase, likely during the update check.

No need for a second thread.

It’s not a “second thread”, if you had bothered to actually read it - similar to other recent threads where you obviously haven’t read official posts then complain about the devs not doing things you think they should be doing, when in actual fact they are doing them. ie: bug report templates with computer specs.

It’s a question for Sim Update 10 BETA: Dev Stream: SU10 Questions - Our next Live Dev Q&A will be Thursday, August 18th at 10:30am PT (1730Z) in order to get more visibility on a real problem for people transitioning between beta and live version. It had to be approved by the mods to be posted, and I included the links to this thread and the other one as reference.

If you’re not willing to help, fine, but don’t stop the rest of us from trying to get some progress happening, please.

I don’t believe I have read any posts regarding anyone having this problem reverting from the beta who was not on the Steam platform. Thus this indicates a possibility of a Steam issue. If everyone would bother to complete their profile we could expedite finding out platform specific issues.

@Sonicviz @Salem978,
Do not direct posts to others.

@Sonicviz,
Do not create a post to have users vote on other topics.

Will do. My apologies. It’s an important issue, just trying to get it more visible.

The OP was not on Steam it seems: “Exit Beta in the Insider Hub → Xbox App loads last stable client → Start Sim → CTD” so it looks to be a xplatform issue.

Do you have the same issue if you follow the OP’s steps to reproduce it?

YES

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

1914974813637256759, type 5