Why is my VR headset not detected in MSFS 2020 or 2024?

If Microsoft Flight Simulator says no headset is detected, first check whether the headset appears in its own PC runtime. If it does, MSFS/OpenXR or the VR-mode binding is at fault; if MSFS enters VR but shows black or frozen imagery, detection succeeded and rendering has failed. Steam ownership does not require SteamVR.

What does “no headset detected” actually mean?

The point at which VR fails tells you which part of the chain needs attention.

First check whether your MSFS edition supports VR

PC OpenXR VR is available in installed Windows editions of MSFS 2020 and MSFS 2024; an unsupported console edition cannot be made to detect a PC headset through settings or adapters.

The Steam and Microsoft Store PC editions use the same OpenXR interface. Owning MSFS on Steam does not by itself mean SteamVR should manage the headset. If compatibility is uncertain, check the supported headset, platform and connection combinations for MSFS before changing software.

How do I fix a VR headset not detected by MSFS?

The reliable sequence is to establish a working PC VR session, register the runtime that manages that session, and only then ask the simulator to enter VR.

1. Test the headset outside MSFS. Open the headset platform and confirm that it reports the headset as connected, awake and tracked. For a standalone headset such as Quest 3, enter its PC VR mode first; reaching the headset’s standalone home screen is not enough.
2. Select the matching OpenXR runtime. Only one runtime is registered as active in Windows at a time. Use the runtime supplied by Meta, SteamVR, Windows Mixed Reality, Virtual Desktop or the headset manufacturer according to the connection actually being used.
3. Restart the complete VR stack. Close MSFS and all VR platforms. Start only the software needed for this headset, connect it, confirm that it is ready, and then launch MSFS in 2D.
4. Use Toggle VR Mode once. Ctrl+Tab is the usual default, but the assignment can be changed or removed. Click inside the simulator window, invoke the command once and allow the OpenXR session time to start; pressing it twice can return the simulator to 2D.
5. Check the connection. For USB headsets, avoid an unpowered hub and confirm that the cable carries data rather than charging only. Connect direct-display headsets to the discrete graphics card. For wireless VR, make sure the PC streaming session remains connected while MSFS loads.
6. Remove competing layers. Temporarily disable OpenXR API layers, frame-generation injectors, ReShade, hand-tracking tools, capture hooks, FPS overlays and foveated-rendering utilities. Do not remove the core runtime that the headset needs.
7. Update and reboot. Install compatible graphics drivers, headset software and firmware, then restart Windows. A reboot reloads headset services and OpenXR registration that may survive an ordinary application restart.

Reinstalling the simulator is rarely a useful first step. If the headset cannot enter its own PC VR environment, MSFS has nothing to detect; if that environment works, concentrate on OpenXR registration, the launch sequence and the control binding.

Which OpenXR runtime should I use for MSFS?

Choose the OpenXR runtime that manages the headset connection, not the shop that supplied Microsoft Flight Simulator.

Runtime controls vary between headset applications. Our step-by-step OpenXR setup and launch order explains how to identify and select the correct one without relying on a guessed menu location.

Quest 3: Link, Air Link and Virtual Desktop

A Quest 3 must be connected to a VR-capable Windows PC; the standalone headset cannot run the Windows version of MSFS VR by itself. With a cable, charging does not prove that a working USB data session exists. With Air Link or Virtual Desktop, the streaming session must be active before MSFS enters VR.

Use Meta OpenXR for Link or Air Link. When using Virtual Desktop, use the runtime selected for that route and do not open competing Quest or SteamVR paths unless the chosen configuration requires them. The Quest-specific runtime and connection checks cover the usual Quest 3 launch-order, cable and wireless failures.

Do I need SteamVR or a Steam frame overlay for MSFS?

Steam, SteamVR, the SteamVR OpenXR runtime and Steam’s frame tools are separate components, and only some headsets need all of them.

• Steam is the store, licence manager and launcher for a Steam copy of MSFS.
• SteamVR is a PC VR platform used to connect and track headsets managed through SteamVR.
• The SteamVR OpenXR runtime is the registered interface through which MSFS communicates with a SteamVR-managed headset.
• A Steam frame display, frame-timing graph, FPS counter or dashboard overlay is a diagnostic tool. It cannot make MSFS detect a headset, and an injected overlay or frame-generation layer can interfere with testing.

For a headset that genuinely requires SteamVR, use this order:

1. Close MSFS and other VR platforms. This prevents another application from retaining the OpenXR session.
2. Connect the headset. Start any manufacturer driver that the headset requires before SteamVR.
3. Start SteamVR. Confirm that it reports the headset as ready and tracked.
4. Register SteamVR as the OpenXR runtime. Use SteamVR’s runtime setting, then verify it again if another headset platform has been launched.
5. Launch MSFS in 2D. It can be the Steam or Microsoft Store edition; store ownership does not change this sequence.
6. Invoke Toggle VR Mode. While diagnosing, disable the Steam desktop overlay, optional SteamVR dashboard overlays, FPS counters and third-party frame-generation or injection layers.

If a Quest Link session works through Meta OpenXR, adding SteamVR creates another moving part without improving detection. Use SteamVR only when the headset or selected streaming route is actually managed by it.

Why does Ctrl+Tab do nothing?

Ctrl+Tab usually fails because Toggle VR Mode is unassigned, the wrong control profile is active, the simulator lacks keyboard focus or no valid OpenXR headset session exists.

• Search the simulator’s Controls options for Toggle VR Mode; do not assume the default survived an update or profile change.
• Check the active keyboard or controller profile rather than editing an unused profile.
• Remove any conflicting assignment and click inside the MSFS window before trying the command.
• If MSFS displays No headset detected, the binding worked. Return to the runtime and connection checks.
• If MSFS briefly enters VR and immediately returns to 2D, check for a sleeping headset, dropped connection, runtime crash or duplicate toggle input.

What differs between MSFS 2020 and MSFS 2024?

Both PC simulators use OpenXR, but their control profiles, add-on locations and settings are separate and must be tested separately.

MSFS 2020 detection path

Connect the PC headset and start its OpenXR runtime before launching MSFS 2020. Check Toggle VR Mode in the active MSFS 2020 control profile, then test with that simulator’s own Community folder empty. A working MSFS 2024 profile or add-on setup does not repair MSFS 2020.

MSFS 2024 detection path

Repeat the runtime and binding checks inside MSFS 2024 rather than assuming an MSFS 2020 profile transferred correctly. Test the MSFS 2024 Community folder and external tools independently. On Xbox, PC headset detection remains unsupported; on PS5 and PS5 Pro, PSVR2 requires the dedicated free 2026 update rather than PC OpenXR software.

Has Windows 11 removed support for my WMR headset?

Windows Mixed Reality was removed from Windows 11 version 24H2 and later, including Mixed Reality Portal and Windows Mixed Reality for SteamVR. A WMR headset cannot use the former Microsoft runtime on those Windows releases, and changing an MSFS setting or reinstalling the simulator cannot restore operating-system components that no longer exist.

The realistic paths are limited:

• Keep an existing Windows 11 version 23H2 WMR installation only as a temporary legacy setup. Microsoft’s WMR compatibility window extends through November 2026, and the Windows edition itself must still be within its applicable servicing period.
• Use the Windows rollback option or restore a known 23H2 system image if that option is still available, understanding that this is not a sound long-term path once the Windows edition leaves security support.
• Use an alternative manufacturer-supported runtime only if the headset maker explicitly provides one for that WMR model.
• Move to a headset with a vendor-supported OpenXR or SteamVR runtime on a supported Windows release.

Installing Windows 10 is not a general long-term fix: its normal support ended on 14 October 2025. This limitation is outside MSFS 2020 and MSFS 2024.

What if the display is black, returns to 2D or crashes?

These symptoms usually mean the headset was detected but the OpenXR session failed during rendering or became unstable.

• Black or frozen headset: if the desktop VR mirror continues moving, inspect the compositor, headset display connection and overlays. If the mirror also freezes, suspect the graphics driver, an injected layer or an overloaded rendering configuration.
• Immediate return to 2D: keep the headset awake, check its proximity sensor and connection, make sure the toggle was not invoked twice, and inspect the headset platform for an OpenXR session error.
• Crash or driver timeout: treat this as a stability fault. Disable frame generation and other hooks, return GPU tuning to default, test a compatible graphics driver and use an empty Community folder.

Once MSFS has attempted to draw the VR view, repeating headset-detection changes is unlikely to help. Use the focused MSFS black-screen and frozen-display diagnosis for the next checks.

Done all this and it is still the same? (Nadal to samo?)

If every attempt produces the same result, stop repeating restarts and isolate the simulator, binding and runtime in this order.

1. Test a clean simulator environment. Move the contents of the relevant MSFS 2020 or MSFS 2024 Community folder somewhere safe, leaving the folder empty. Disable external SimConnect utilities and every third-party injected tool, including OpenXR layers, ReShade, overlays, capture hooks and frame-generation modifications.
2. Recreate Toggle VR Mode. Remove the existing assignment, save the profile, create a clean control profile if necessary, and assign Toggle VR Mode again. Check for duplicate or conflicting inputs before testing.
3. Verify the runtime after every headset-platform launch. Meta, SteamVR and other headset applications can reclaim OpenXR registration when opened or updated. Recheck which runtime is active immediately before launching MSFS.
4. Collect the exact failure details. Record the full MSFS message, whether the simulator entered VR at all, the MSFS release and build, Windows version from winver, graphics driver, headset firmware, connection method and active runtime. For crashes, retain the Windows Reliability Monitor or Event Viewer faulting-module details and any error shown by the headset runtime.
5. Send the evidence to the correct support team. Contact the headset vendor when its own PC environment cannot find the device, tracking fails or its runtime reports the error. Contact MSFS support when the headset and other OpenXR content work through the correct runtime but a clean MSFS 2020 or 2024 installation alone fails. If the fault returns only after one overlay or injector is re-enabled, report it to that tool’s developer instead.