Does Prepar3D work on Windows 11, and how do I set it up?

Yes. Prepar3D works on Windows 11, with v6 the sensible choice for a new installation and v5 often practical for established add-on collections. Install the latest build available for your licensed major version, test the untouched simulator first, then add aircraft, scenery and utilities individually; older add-ons cause most compatibility failures.

Which Prepar3D version works best on Windows 11?

For a new Windows 11 PC, Prepar3D v6 is the best default unless an essential aircraft, scenery package or utility only supports an earlier version.

Prepar3D v4 and later are 64-bit. A 32-bit in-process gauge or module cannot load in these versions, even if its aircraft model and textures remain usable. Compatibility with one Prepar3D generation never guarantees compatibility with the next.

Running successfully and qualifying for formal support are also different matters. If vendor support is required, use the operating-system requirements published for your exact Prepar3D build and licence as the final authority.

How do I install Prepar3D on Windows 11?

Install Prepar3D from a fully extracted, matched installer set and confirm that the unmodified simulator works before adding third-party content.

1. Choose the major version. Check your essential aircraft, scenery, weather engine, hardware interface and other utilities first. Selecting v6 and then discovering that a required compiled add-on only supports v5 is a common and costly mistake.
2. Download and extract the installer. Save it to a local drive, extract the complete archive and run the top-level installer rather than launching files from inside a compressed folder. Our complete Prepar3D download, extraction and activation walkthrough covers the full installer sequence.
3. Prepare Windows. Finish pending Windows updates, install the appropriate graphics driver and restart. Let the Prepar3D installer add its supplied Microsoft runtime and DirectX prerequisites. Never fix a missing-DLL message by downloading an individual DLL from an unrelated source.
4. Select a sensible location. The default folder is valid. A dedicated local folder outside Program Files may help with old add-on installers, but avoid OneDrive-synchronised folders, removable drives and broad changes to Windows folder permissions.
5. Run the main setup program. Start Setup_Prepar3D.exe with an administrator-capable Windows account and approve the UAC request. Keep Client, Content and Scenery components from the same release unless the supplied update instructions explicitly say otherwise.
6. Test a clean flight. Start Prepar3D, load an included aircraft at an included airport, fly for several minutes and close the simulator normally. Repeat the same scenario once more so you know the base installation is stable.
7. Configure controls and graphics. Set up the essential axes and buttons before adding complex aircraft. Begin with conservative display settings, then increase them while repeating the same test flight.

Do not copy an entire Prepar3D directory from another computer. That misses prerequisites, registry information, activation data and package registrations. Reinstall the simulator and add-ons properly, then copy only documented user files such as saved scenarios or controller profiles.

What should I configure on the first launch?

Set up controls, confirm the correct GPU is being used and establish a repeatable graphics baseline before installing add-ons.

Controls and USB devices

Open joy.cpl in Windows and confirm that every controller responds before assigning it in Prepar3D. Bind aileron, elevator, rudder, throttle and brakes, then inspect every connected device for duplicate automatic axis assignments.

Two devices controlling the same axis can produce twitching, weak control response or throttles that jump back after movement. Add only enough null zone to suppress genuine sensor noise; a large null zone masks useful control travel. Older yokes, pedals and joysticks may also need Windows 11-compatible device software even when Prepar3D itself is working correctly.

Graphics settings

Use the monitor's native resolution and start with moderate anti-aliasing, shadows, traffic, autogen and scenery density. High-resolution textures, dense scenery and heavy shadows can exhaust graphics memory before average frame rate appears low.

Laptop users should assign Prepar3D to the discrete GPU under Settings > System > Display > Graphics and test while connected to mains power. Our Prepar3D graphics and performance baseline explains which settings to reduce first when frame pacing or graphics memory becomes a problem.

Which Windows 11 settings should I change?

Prepar3D does not require disabled security, aggressive system optimisation or blanket compatibility settings.

• Compatibility mode: leave it off unless the documentation for a specific Prepar3D release or add-on requires it.
• Administrator mode: do not force Prepar3D.exe to run as administrator for ordinary use. Prepar3D and programs communicating with it should normally run at the same privilege level.
• Controlled Folder Access: if settings or scenarios cannot be saved, allow the relevant executable through Windows Security rather than disabling protection entirely.
• Power and GPU selection: use an appropriate performance power mode and confirm that a laptop is not launching Prepar3D on its integrated GPU.
• Overlays and overclocking: leave them alone when the simulator is stable. Disable overlays temporarily and return CPU, GPU and memory clocks to standard settings when diagnosing crashes or erratic frame pacing.
• Antivirus exclusions: add a narrow exclusion only after confirming a false positive involving a trusted file. Do not exclude the whole drive or switch off protection permanently.

Will older Prepar3D add-ons work on Windows 11?

Older add-ons work only when their Prepar3D version, architecture, dependencies and installer remain compatible; Windows 11 compatibility alone is not enough.

Test one package at a time and prefer the package-based add-on.xml method where it is supported. It keeps third-party files away from the core simulator folders and makes a faulty package easier to disable. Our guide to installing and managing Prepar3D add-ons safely covers aircraft, scenery, utilities, package registration and legacy installation methods.

• Aircraft: confirm the exact supported Prepar3D generation. A visible exterior model does not prove that compiled gauges or systems are compatible.
• Scenery: check required libraries, simulator generation and scenery priority. Do not assume every FSX or earlier Prepar3D package can be copied directly.
• Utilities: verify the required SimConnect client and run the utility at the same privilege level as Prepar3D.
• Installers: an old installer may reject Windows 11 or write to the wrong simulator folder even when the add-on files themselves could work.

Several SimConnect client versions can exist side by side because older utilities may require the interface against which they were built. Use the supplied redistributables rather than replacing DLLs manually; our SimConnect setup and connection instructions cover local programs, networked applications and firewall checks.

Why does Prepar3D fail to start on Windows 11?

Startup failures usually come from damaged generated settings, an incompatible add-on, a missing prerequisite or a graphics driver problem rather than Windows 11 itself.

After a graphics driver change or unexplained visual corruption, close Prepar3D and rename the generated Shaders folder inside the version-specific Prepar3D directory under %LOCALAPPDATA%\Lockheed Martin\. The simulator will rebuild it at the next launch.

Use Windows Event Viewer's Application log when the program still closes without an on-screen error. A named faulting module often identifies an add-on DLL or driver component. Reinstallation should be the last step because uninstalling Prepar3D can leave the same damaged user configuration behind.

Once the clean simulator, controls and repeatable test flight work reliably, preserve that baseline. If a later problem appears, disable the last aircraft, scenery package or utility added instead of changing Windows settings at random.