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

Yes, Prepar3D generally works on Windows 11, but compatibility depends on the Prepar3D release and, more often, on older aircraft, scenery and utilities. Use a supported 64-bit release where possible, install its prerequisites and updates, configure controls first, then add third-party content gradually so failures are easy to isolate.

Which Prepar3D versions work best on Windows 11?

Prepar3D v6 is generally the cleanest choice for a new Windows 11 installation, provided the aircraft and scenery you need support it. Working and being formally supported are not identical, so check the published operating-system requirements for your exact Prepar3D build when vendor support matters.

Prepar3D v4 and later are 64-bit. An old in-process 32-bit gauge or module DLL cannot load into these versions, although ordinary textures and some scenery may still be usable.

How should I install Prepar3D on Windows 11?

The safest Windows 11 setup is a clean base installation followed by one change at a time. Do not copy an entire Prepar3D folder from another PC and expect its registry entries, prerequisites and add-on registrations to follow it.

1. Check version compatibility. Confirm that your licence, installer and essential add-ons target the same Prepar3D generation. Keep the components from a matched installer set rather than mixing files from different updates.
2. Prepare Windows. Complete pending Windows updates, install a suitable graphics driver and restart. Allow the Prepar3D installer to add its supplied Microsoft runtime and DirectX components; never solve a missing-DLL message by downloading a loose DLL from an unknown source.
3. Choose the installation location. The normal default folder is valid. A short custom path outside Program Files can reduce permission trouble with old add-on installers, but avoid OneDrive-synchronised locations and do not weaken folder security for every user.
4. Run the installer with administrative approval. Use a Windows account with administrator rights and accept the UAC prompt. This does not mean Prepar3D itself should always run as administrator; mixed privilege levels can stop external utilities from communicating with it.
5. Test the clean simulator. Start Prepar3D before installing anything else, load a default aircraft at a default airport, fly briefly and close it normally. This establishes whether the core installation works.
6. Configure controls and graphics. Assign aileron, elevator, rudder, throttle, brakes and view controls, then remove duplicate axis assignments automatically placed on other devices. Begin at the display’s native resolution with moderate anti-aliasing, shadows, traffic and scenery density.
7. Add content gradually. Install one aircraft, scenery package or utility at a time and test after each addition. Prefer Prepar3D’s package-based add-on.xml method where the product supports it; our scenery registration and priority guide for Prepar3D v5 explains the method in detail. Local applications normally use the included SimConnect components, while remote programs require the correct SimConnect configuration for local and networked applications.

Which Windows 11 settings should I change?

Prepar3D does not require wholesale Windows 11 optimisation or disabled security features. Change only settings connected to a diagnosed problem.

• Laptop graphics: assign Prepar3D to the discrete, high-performance GPU in Windows graphics settings and test while connected to mains power.
• Controlled Folder Access: if Prepar3D cannot save settings or scenarios, allow the application through the protection feature rather than switching Windows Security off.
• Compatibility mode: leave it disabled for v5 and v6 unless documentation for a specific release requires otherwise. It often creates new problems rather than fixing add-ons.
• Administrator mode: do not force Prepar3D.exe to run elevated by default. Prepar3D and any utility communicating with it should normally run at the same privilege level.
• Overlays and overclocking: disable them temporarily only when investigating crashes, device-hung errors or erratic frame pacing.

Why does Prepar3D fail to start or lose add-ons?

Most Windows 11 failures come from a blocked configuration folder, an incompatible binary add-on, a missing runtime or an add-on loaded before the clean simulator was tested.

• Prepar3D closes during startup: temporarily rename its generated configuration file in %APPDATA%\Lockheed Martin\Prepar3D vX\, where vX is your installed generation. Prepar3D will create a fresh file at the next launch; rename rather than delete so your settings remain recoverable.
• A crash began after installing an add-on: disable the most recently added package first. Windows Event Viewer’s Application log may identify the faulting DLL, which is more useful than reinstalling every package at once.
• Gauges are black or missing: confirm that the aircraft supports your exact Prepar3D generation and architecture. Our diagnostic checklist for missing or blank Prepar3D gauges covers blocked files, dependencies and 32-bit gauge incompatibility.
• An aircraft is absent from the selection screen: check for an extra nested folder, an invalid aircraft configuration or a package that was never registered. Follow these aircraft folder and add-on registration checks before moving files into the core simulator directory.
• You see a device-hung or device-removed error: return the GPU to standard clock speeds, update or cleanly reinstall its driver, and reduce texture resolution, shadows or other settings that consume graphics memory.

Once the unmodified simulator launches reliably, controls respond correctly and the same test flight can be repeated without errors, preserve that baseline. Add-on problems can then be traced to the last change instead of being mistaken for a Windows 11 compatibility failure.