15 minutes ago, MarcG said:

reports of some people who were never in a beta being affected. 

there have been problem reports ever since release, unrelated to this phantom issue. some people have corrupted downloads, bad directory/path strategy, and all sorts of misconfigured systems. the support zendesk speaks volumes. and there are users in this forum who joined the beta and now don't know how to leave it. how reliable are their reports. at least some users who got hurt (I only lost my logbook) have learnt their lesson and understand that 100% loss risk as a beta tester is not for them. we'll see how that plays out in the next beta round.

Edited March 23, 20251 yr by turbomax

Hello,
I tried everything after seeing the recommended “solutions” for error 0xc0000005 obtained after the nth attempt to desinstall/reinstall FS2024 and nothing worked.
I think I'll stick with MFSF2020 for a while...

And if I went to beta, that's what was recommended for IniBuilds A350 to work properly.

Man I don't know about you guys but I think this update messed something up on my computer. My computer keeps randomly restarting and I'll be looking at a web page and it resets and say, "Something went wrong".

I have opted out of the insider program and did a complete reinstall  of MSFS as others and still have the same issue. 

My computer never randomly restarted until this update. I have reinstalled the graphics driver and it still happens. Unreal that this has happened. I cant even get this  post typed out before the web page reset. WHAT IN THE WORLD IS GOING ON.

Funny thing is and maybe the irony as well is that it was Inibulds with their 350 which required I get the first beta. In fact I wasn't even aware of the beta. When I did opt in it was geat. Nothing was really effected and it allowed me to use the 350. So here we are the second beta and a complete $hit show. I reinstalled 350 and it doesn't even show up now. LOL.  Then when this build is pushed what am I supposed to do? I installed it following  the first. Maybe I should blame one of their own developers, Inibuild after having paid over $ 100 Canadian for the 350 requiring me to opt in on this whole beta fiasco just to use their plane only to now become unuseable now along with the mess created by this beta! 

I have at all times  a custom community folder. Which I pointed in MSFS (gear) to my custom location.

Despite that it is not recognizing several things including the 350 and numerous airports I bought and installed.

I had to today locate what were now empty locations and default locations of airports.

Now I have tried to start the sim twice and it crashed to the desktop both times.

This is a mess and unacceptable.

Edited March 23, 20251 yr by lenny777

10 minutes ago, LarryImler said:

Man I don't know about you guys but I think this update messed something up on my computer. My computer keeps randomly restarting and I'll be looking at a web page and it resets and say, "Something went wrong".

I have opted out of the insider program and did a complete reinstall  of MSFS as others and still have the same issue. 

My computer never randomly restarted until this update. I have reinstalled the graphics driver and it still happens. Unreal that this has happened. I cant even get this  post typed out before the web page reset. WHAT IN THE WORLD IS GOING ON.

Maybe try a third party uninstall program that gets rid of any debris leftover. Something like Revo uninstaller. You can use the free trial. 

Edited March 23, 20251 yr by RobJC

18 minutes ago, LarryImler said:

I have opted out of the insider program and did a complete reinstall 

a re-install may no be enough. I would de-install first:

https://flightsimulator.zendesk.com/hc/en-us/search?utf8=✓&query=uninstall&commit=Search

Edited March 23, 20251 yr by turbomax

10 minutes ago, RobJC said:

Maybe try a third party uninstall program that gets rid of any debris leftover. Something like Revo uninstaller.

I doubt they would know better than Microsoft how to deal with such complex install requirements, for starters:. wrong time zone, or how to reset the xbox gaming app, run the Gaming Services Repair tool, or reset the store (WSReset.exe) to name just a few

https://flightsimulator.zendesk.com/hc/en-us/articles/4412971935762-How-to-uninstall-and-reinstall-the-Xbox-app-to-fix-installations-and-updates-issues

 

I'll redo this, Thankyou.

Not sure why people are defending Asobo with this fiasco. I mean if it were a one off, sure. But it’s not. It’s just mess after mess. 

2 hours ago, turbomax said:

there have been problem reports ever since release, unrelated to this phantom issue. some people have corrupted downloads, bad directory/path strategy, and all sorts of misconfigured systems. the support zendesk speaks volumes. and there are users in this forum who joined the beta and now don't know how to leave it. how reliable are their reports. at least some users who got hurt (I only lost my logbook) have learnt their lesson and understand that 100% loss risk as a beta tester is not for them. we'll see how that plays out in the next beta round.

100% agree, I can't say it better. I'm following the steam reviews on steam meticulously since release (stable version). And it's astonishing how constant the bad reviews are regarding the many issues of the MSFS2024; and many of those reviewers are very detailed and laboured to show up their problems (worth a read).

And between all these bad reviews there are plenty of typical and uncommunicative "word not allowed" comments, or - most likely - payed reviewers from MS/Asobo - for saving the stats not falling into oblivion.

In total, all these smells fishy in such a high degree meanwhile, that no one with a minimum of common sense in his mind can deny it.

Edited March 23, 20251 yr by Grisu

I thought I had opted out of Beta but guess not.  I was able to recover my community folder by running Navigraph Hub and MSFS Addons Linker.

 

Opened the xbox insider app, settings and removed my PC.

Edited March 23, 20251 yr by Burnhaven

47 minutes ago, Ianrivaldosmith said:

Not sure why people are defending Asobo with this fiasco. 

Because they basically wrote in the disclaimer of the Beta that exactly such things can happen? People using the betas to get early access to the SU must expect such things to a certain extent. 

6 minutes ago, AnkH said:

Because they basically wrote in the disclaimer of the Beta that exactly such things can happen? People using the betas to get early access to the SU must expect such things to a certain extent. 

You’re just repeating what others have all ready said. However, the beta finished weeks ago. And those still signed up in Xbox insider app had zero problems. So, why was this ‘update’ pushed? With zero warning. They have pushed a mess out on a Friday evening and caused chaos. It’s not like it was even SU2. Again, it’s indefensible. Anybody that finds this defensible is crackers. This is past ‘a certain extent’. It’s just bonkers. 

Edited March 23, 20251 yr by Ianrivaldosmith

7 minutes ago, AnkH said:

People using the betas to get early access to the SU must expect such things to a certain extent. 

THIS!! 'To a certain extent'. But deleting the data of millions of users ... well ... SMH.

BTW - I'm missing 'certain' people 😄 in this thread, defending Asobo and blaming the users.

Edited March 23, 20251 yr by flying_carpet

2 minutes ago, AnkH said:

Because they basically wrote in the disclaimer of the Beta that exactly such things can happen? People using the betas to get early access to the SU must expect such things to a certain extent. 

I think you have to read more carefully this thread because your post is generating confusion and ignorance. Please read what's happening for real.