MSFS 2020 (Steam) launcher crashes after Asobo/Blackshark screens on startup

A few things jump out from your specs + symptoms

The fact you get past the Asobo/Blackshark splash and then it just vanishes a few seconds later usually means the sim is dying right as it starts initializing core components (WASAPI audio, MS Gaming Services/Xbox bits, C++ runtimes, permissions, or a bad config/cache). Since you’re on Steam and you already did the “big hammer” reinstalls, I’d focus on the usual early-start crash culprits.

Step-by-step things to try (in this order)

1) Force a clean start with no community content (even if you think it’s empty)
MSFS will still crash early if it’s reading an old path or leftover config.

• Go to your MSFS packages location (wherever you had Official/Community before).
• Temporarily rename the Community folder to something like Community.OFF
• If there’s an Official folder there too, leave it alone for now (or rename it only if you’re sure you’re fully re-downloading).

2) Delete the MSFS config file(s) so it rebuilds them
This is separate from “folders related to MSFS” if Windows/Steam left your user profile files behind.

• Go here:
  %AppData%\Microsoft Flight Simulator\

• Also check:
  %LocalAppData%\Packages\
  (You may or may not have a MS Store style folder here on Steam installs, but it’s worth checking.)

• You’re looking for the user config / settings that may be forcing a bad graphics mode, bad audio device, etc. Safest approach: rename the whole Microsoft Flight Simulator folder to Microsoft Flight Simulator.BAK and let it rebuild.

3) Disable all overlays and “hooking” apps for one test run
These can crash MSFS right after the splash screens.

• Steam Overlay (disable for MSFS)
• Discord overlay
• Radeon/AMD overlay and recording features
• MSI Afterburner / RivaTuner (if installed)

4) Run MSFS once as Administrator
Not as a permanent fix, just as a test to confirm it’s a permissions / security policy issue.

• Right-click the MSFS exe (or Steam shortcut) and run as admin.

5) Audio device sanity check (surprisingly common for “crash after splash”)

• Unplug any USB headsets/audio interfaces for the test.
• Set one normal device as default in Windows Sound settings (Speakers/Headset).
• Disable “exclusive mode” temporarily on the default playback device (Advanced tab).

6) Check Windows Event Viewer for the faulting module
This is the quickest way to avoid guessing.

• Open Event Viewer
• Windows Logs -> Application
• Find the error at the time of the crash (it’ll mention the faulting application + faulting module)
• Post the “Faulting module name” and “Exception code”

Important note about “MiniOS Win10 Pro”

This is the one thing in your post that makes me raise an eyebrow. A lot of “lite”/stripped Windows builds remove or partially disable components MSFS expects (Media Foundation, Xbox/Gaming services dependencies, certain runtimes, etc.). MSFS can appear to “install fine” and then crash right after the splash screens because a required Windows component simply isn’t there.

I’m not saying “reinstall Windows” right away, but if the Event Viewer points to missing/failed Windows components (or if nothing else changes the behavior), that’s where this often ends up.

A few targeted questions so I don’t send you down the wrong rabbit hole

• When it crashes, do you get any error message at all, or does it just close to desktop?
• What does Event Viewer show for the crash? (faulting module + exception code)
• Are you using any USB headset/DAC or any special audio software?
• Did MSFS ever run successfully on this PC before, or has it never launched since install?
• What exact AMD driver version are you currently on?

If you paste the Event Viewer crash entry details, I can usually tell you the next “surgical” fix in one or two steps.