How do I fix MSFS crashing when switching to VR?

Microsoft Flight Simulator usually crashes when switching to VR because the active OpenXR runtime does not match the headset connection, an overlay or ReShade hook conflicts, an add-on fails, or the VR load exposes driver, VRAM or hardware instability. Restart the VR stack, select one runtime, disable injectors and add-ons, then lower VR settings.

These Windows PC steps apply to Microsoft Flight Simulator 2020 and MSFS 2024. Xbox does not support VR. PSVR2 support for MSFS 2024 on PS5 and PS5 Pro is a separate console implementation supplied through a free 2026 update; it does not use the Windows OpenXR, Quest Link or ReShade fixes below.

What should I do first when MSFS 2024 crashes while switching to VR?

A clean, low-load VR test is the fastest way to separate an OpenXR problem from an add-on, graphics or hardware fault.

1. Restart every part of the VR stack. Close MSFS and the headset software, restart the PC and power-cycle the headset. Reconnect a wired headset directly to a suitable motherboard USB port rather than an unpowered hub. Confirm that tracking and the headset display work before launching the simulator.
2. Select the runtime used by the connection. Quest Link and Air Link normally use the Meta OpenXR runtime; a route that deliberately depends on SteamVR needs the SteamVR runtime. Restart MSFS after changing it. Follow our headset-specific OpenXR setup procedure if you are unsure which runtime is active.
3. Disable all injectors and overlays. Turn off ReShade, optional OpenXR API layers, performance overlays, recording hooks, monitoring tools and third-party motion-reprojection or foveated-rendering utilities. Closing an overlay window may leave its hook loaded, so disable it in the parent application.
4. Test without add-ons. Use Safe Mode if MSFS offers it after the crash. Otherwise, move the contents of the Community folder elsewhere, then choose a default aircraft, a modest default airport, clear weather and no AI traffic. Safe Mode does not remove external tools such as ReShade or driver overlays.
5. Reduce the actual VR settings. Lower VR render scaling, texture resolution, clouds, terrain level of detail and object level of detail. Changing only the flat-screen graphics preset may leave the separate VR profile untouched. Close browsers, capture software and other GPU-heavy applications as well.
6. Return the PC to stock settings. Remove CPU and GPU overclocks or undervolts. If the crash continues, temporarily disable XMP or EXPO to test memory stability. A VR transition can expose marginal tuning that appears stable during flat-screen flying.
7. Use a controlled launch order. Start the headset connection first, launch MSFS in 2D, load the simple test flight and then run the assigned Toggle VR command. Ctrl+Tab is common on a default PC profile, but a customised control profile may have a different binding.
8. Restore items one category at a time. Re-enable the runtime feature, overlay, add-on or higher setting that you actually need, then retest. For a large Community folder, restore half at a time. If it crashed again, the last restored group is the place to investigate.

Which OpenXR runtime should MSFS use?

The correct OpenXR runtime is determined by the software carrying the headset connection into Windows, not by the store where you bought MSFS.

A Steam copy of Microsoft Flight Simulator does not automatically require SteamVR. Windows uses one active OpenXR runtime, but optional API layers can still load around it. Changing the runtime without disabling an old toolkit or injector is a common reason the crash remains.

Why does MSFS crash only when entering VR?

Switching to VR creates an OpenXR session and sharply increases render-target, driver, VRAM and system-memory demand, so a flight that is stable on a monitor can still fail at the transition.

For a suspected graphics fault, use a clean display-driver installation if the installer provides that option. If the problem began immediately after a driver update, test the previous stable driver available for your GPU. Keep the Windows page file system-managed and ensure its drive has free space.

MSFS 2020 users can also test DirectX 11 if the crash occurs under DirectX 12. MSFS 2024 uses its supported DirectX 12 path, so do not waste time searching for a DX11 switch there. If MSFS reports Your graphics device has encountered a problem, follow our diagnosis for MSFS 2024 graphics-device errors.

Can I use MSFS VR with ReShade?

ReShade may work in some configurations, but it must be completely removed from the test path when MSFS crashes with ReShade installed.

Turning off individual effects or hiding the ReShade interface does not necessarily unload its graphics hook. Disable or uninstall it using the same installation method, restart Windows and retest with no other post-processing or OpenXR layer active. Avoid manually deleting guessed DLL files because the filenames and installation locations vary.

If VR becomes stable, restore ReShade by itself before adding any other overlay. Then enable effects in small groups. A crash that returns only with ReShade points to that hook, an effect or a conflict with another layer; reinstalling the entire simulator is unlikely to fix it.

What if Toggle VR just does nothing or gives a black screen?

If Toggle VR does nothing, first confirm that the command is bound and the headset runtime already has a working connection; a black headset display does not always mean MSFS has crashed.

• The MSFS process has closed: this is a real application crash. Return to the clean runtime and no-overlay test.
• The desktop view still moves and audio continues: MSFS is running, but the compositor or headset display route has failed. Restart the headset software, verify the active runtime and remove optional layers.
• The shortcut produces no reaction: search the controls for Toggle VR, assign an unambiguous binding and make sure the simulator window has focus. Another application may be intercepting the shortcut.
• The headset remains in its home environment: the OpenXR session probably was not created. Confirm that the headset is detected before MSFS starts and that the connection route matches the active runtime.

A crash can also leave a stale compositor session, so a full PC and headset restart is more reliable than repeatedly pressing Toggle VR. Our VR error and headset black-screen checklist covers the wider detection and display-routing checks.

What changes if I am using Wi-Fi with Meta Quest 3?

For a Meta Quest 3 using Air Link or another wireless route, first determine whether the failure is an MSFS crash, an OpenXR route conflict or simply the wireless stream disconnecting.

• With Air Link: make the Meta OpenXR runtime active and avoid starting SteamVR unless your chosen route explicitly requires it.
• With Virtual Desktop: use the OpenXR route selected for that application rather than stacking a second route on top of it.
• Test a suitable Link cable: if wired Link works repeatedly but Wi-Fi fails, concentrate on the wireless route and local network rather than reinstalling MSFS.
• Check the local connection: connect the PC to the router by Ethernet where possible and keep the headset on a strong, low-congestion 5 GHz or 6 GHz connection. Internet speed is not the same as the local Wi-Fi quality carrying the VR stream.
• Compare the failure point: if wired and wireless connections both crash at the same Toggle VR moment, Wi-Fi is unlikely to be the root cause.

Connection modes and runtime choices are covered in our Meta Quest 3 and Oculus connection guide for MSFS 2024.

How can I find what actually crashed?

Windows Reliability Monitor and Event Viewer can distinguish an MSFS application fault from a headset module, graphics-driver reset or wider system failure.

1. Open Reliability Monitor. Search Windows for View reliability history and inspect the failure recorded at the crash time.
2. Record the useful fields. Note the faulting application, faulting module and exception code. A headset, overlay or ReShade module is more informative than a generic reference to the main simulator executable.
3. Check Event Viewer. Inspect Windows Logs > Application for the application crash and Windows Logs > System for display-driver resets, hardware errors or unexpected restarts.

A related LiveKernelEvent supports checking the GPU driver, temperatures, power and hardware stability, but does not prove that the graphics card is defective. Event 41 only records that Windows shut down unexpectedly; it does not identify the cause.

Is there a fix coming, or should I reinstall MSFS?

There is no single update that can fix every VR transition crash because a wrong runtime, ReShade hook, unstable overclock and defective add-on are separate faults.

Keep MSFS, Windows, the headset software, headset firmware and graphics driver updated, then repeat the clean baseline. A simulator or runtime update may correct a specific regression, but waiting for a patch will not repair a mismatched OpenXR route or an external injector. If the fault began after one particular graphics-driver update, testing a previous stable driver is a reasonable isolation step.

No, a full Microsoft Flight Simulator reinstall should not be the first response. Repair the headset software, reset the simulator's VR graphics settings, remove Community content and use the launcher platform's file-verification or repair function first. Do not delete the Official package folder as an early test; that can trigger a large content download without replacing the conflicting VR component.

Consider reinstalling only when the clean setup still fails, file verification finds damage or MSFS is also unstable in 2D. If every PC VR application fails, repair the headset runtime or graphics stack instead. If only one aircraft or location fails, remove that package and its dependencies rather than reinstalling the simulator.