Why is my VR headset not detected in MSFS 2020 or 2024?
Microsoft Flight Simulator 2020 or 2024 usually fails to detect a VR headset because Windows has the wrong OpenXR runtime selected, the headset’s PC connection is not active before VR mode starts, or the simulator is running on a platform without VR support. Connect the headset first, select its OpenXR runtime, then toggle VR mode.
First check whether your platform supports VR
VR detection is available in both releases on Windows PC, but console support differs and cannot be enabled through an in-game setting.
| Platform | MSFS 2020 | MSFS 2024 |
|---|---|---|
| Windows PC | PC VR supported through OpenXR | PC VR supported through OpenXR |
| Xbox Series X|S | VR not supported | VR not supported |
| PlayStation 5 and PS5 Pro | Not released for PlayStation | PSVR2 support is provided through a free 2026 update; detection requires that update to be available and installed |
The Steam and Microsoft Store PC editions use the same OpenXR system. Buying MSFS through Steam does not mean SteamVR must be the active runtime. For a new installation, our PC VR setup checklist for MSFS 2020 and 2024 covers the required software and initial activation.
How do I fix a VR headset not detected by MSFS?
The fastest fix is to establish a working headset session outside MSFS, select the matching OpenXR runtime, restart the software stack and then invoke the simulator’s Toggle VR Mode command.
- Test the headset outside MSFS. Open its manufacturer software and confirm that the PC VR environment starts. For a wireless headset, establish the PC streaming connection first. If the manufacturer software cannot see the headset, MSFS will not see it either.
- Select the correct OpenXR runtime. Use the headset or VR platform software to make its OpenXR runtime active. Windows uses one active OpenXR runtime at a time, so installing several VR platforms can leave the wrong one registered.
- Restart after changing the runtime. Close MSFS, the headset software and any other VR platform. Reopen the required headset software, confirm that the headset is awake and connected, and only then launch the simulator.
- Invoke Toggle VR Mode.
Ctrl+Tabis the usual default shortcut, but bindings can be changed or removed. Search the Controls options forToggle VR Modeand assign it to the active keyboard or controller profile. - Remove competing VR layers. Temporarily disable OpenXR API layers, overlays, hand-tracking utilities, foveated-rendering tools and other software that inserts itself between MSFS and the runtime. Restore them one at a time after detection works.
- Update and reboot the complete stack. Install compatible graphics drivers, headset software and headset firmware, then restart Windows. Rebooting matters because OpenXR registration and headset services may not reload cleanly without it.
- Check the physical or wireless connection. For wired headsets, avoid an unpowered hub and test another suitable USB port or cable. A direct-display headset should be connected to the discrete graphics card rather than a motherboard video output. For wireless VR, confirm that the PC connection remains active when MSFS launches.
Reinstalling Microsoft Flight Simulator is rarely the first useful step. If the headset works in its own PC environment but MSFS displays No headset detected, the OpenXR runtime or launch sequence is the more likely fault.
Which OpenXR runtime should I use for Microsoft Flight Simulator?
Choose the runtime that directly manages the headset connection, not the store from which you bought the simulator.
| Headset connection | Runtime to try first | Common mistake |
|---|---|---|
| Meta Quest through Link or Air Link | Meta OpenXR runtime | Starting SteamVR unnecessarily and registering a different runtime |
| Headset managed by SteamVR | SteamVR OpenXR runtime | SteamVR is running but is not set as the active OpenXR runtime |
| Windows Mixed Reality headset | Windows Mixed Reality OpenXR environment on a supported Windows installation | An operating-system upgrade has removed or no longer supports the required WMR components |
| Headset with its own native OpenXR software | The manufacturer’s OpenXR runtime | Leaving another platform registered as active |
A Windows Mixed Reality headset that stopped working after an operating-system change deserves special attention. If the installed Windows release no longer includes the required WMR components, changing an MSFS graphics option will not restore detection.
Why does Ctrl+Tab do nothing in MSFS?
Ctrl+Tab usually does nothing because Toggle VR Mode is unassigned, a different control profile is active, the simulator window lacks keyboard focus or no valid OpenXR headset session exists.
- Search the Controls options for
Toggle VR Moderather than assuming the default survived an update or profile change. - Click inside the simulator window before using the shortcut.
- Check that another application has not captured the same key combination.
- If MSFS immediately reports that no headset is connected, the command is working; return to the runtime and connection checks.
What if MSFS detects the headset but the display stays black?
A black display after MSFS enters VR is usually a rendering, driver or OpenXR-layer problem rather than failed headset detection.
Disable third-party VR layers, restart the runtime and test with conservative settings. Once the headset reaches the cockpit, use a clean MSFS 2024 VR performance baseline before reintroducing higher render scaling or demanding features. Graphics settings can fix a black frame or unstable session, but they cannot make an absent OpenXR headset appear.
If entering VR closes the simulator or produces a driver timeout, treat that as a crash rather than a detection fault. Our steps for separating VR-related crashes from wider MSFS crashes cover drivers, add-ons, memory pressure and stability checks.