Learn how to completely uninstall Logitech/Saitek flight-control drivers from Windows, clear hidden devices and prepare for a clean reinstall.
To completely uninstall Logitech/Saitek flight-control drivers from Windows, disconnect every flight device, remove all Logitech/Saitek flight software in Installed apps, uninstall the related devices in Device Manager with driver removal selected, then delete any matching third-party packages from the Windows Driver Store using PnPUtil. Restart before reconnecting anything.
This is a general Windows 10 and Windows 11 procedure rather than a setting inside Microsoft Flight Simulator, X-Plane, Prepar3D or another simulator. If the controller appears and responds in joy.cpl, removing its driver may not solve the fault; first use our Windows detection checks for a Saitek yoke, throttle quadrant and pedals.
How do I remove every Logitech/Saitek driver component?
A complete removal has three separate layers: the vendor’s software, the device instances recorded by Windows and the reusable driver packages held in the Driver Store.
| Layer | What it contains | Why remove it |
|---|---|---|
| Installed apps | Profiling tools, services, panel software and uninstallers | Stops vendor software and background services loading |
| Device Manager | Present and disconnected device instances | Clears the controller’s Windows registration |
| Driver Store | Third-party driver packages Windows can reuse | Prevents the same package being silently installed again |
- Back up custom profiles. Save any Logitech or Saitek programming profiles you want to keep. Simulator bindings are normally stored separately, but screenshots of working axis and button assignments are sensible insurance.
- Disconnect the hardware. Unplug the yoke, joystick, throttle quadrant, pedals and flight panels. Include devices attached through a powered hub. Keeping them disconnected prevents Plug and Play from rebuilding the entries during removal.
- Uninstall the flight-control software. Open Settings, Apps, then Installed apps; Windows 10 may call the list Apps & features. Remove entries explicitly associated with the affected Logitech G Flight or Saitek product, including its programming software, panel packages and old SST software. Do not remove unrelated Logitech mouse, keyboard, webcam or headset software merely because the publisher is the same. For older equipment, follow our steps for stripping out conflicting SST and legacy Saitek packages.
- Remove the device instances. Open Device Manager and select View, then Show hidden devices. Check Human Interface Devices, Sound, video and game controllers, Universal Serial Bus devices and any product-specific category. Right-click entries clearly belonging to the disconnected flight control, select Uninstall device and enable Attempt to remove the driver for this device or Delete the driver software for this device when Windows offers it. Remove each recognisable interface belonging to that controller, but never delete every generic USB Input Device entry; one may belong to the keyboard, mouse or another controller.
- Inspect the Windows Driver Store. Open Windows Terminal or Command Prompt as administrator and run
pnputil /enum-drivers. Look for third-party packages whose provider, original name, class and date identify the affected Logitech/Saitek product. Older packages may retain an earlier vendor label. Note the package’s Published Name, such asoem42.inf, then runpnputil /delete-driver oem42.inf /uninstall, substituting the actual published name. Repeat only for packages you can positively identify. - Deal with an in-use package carefully. If PnPUtil reports that a confirmed flight-control package is in use, restart with every flight device unplugged and run the command again. Use
pnputil /delete-driver oem42.inf /uninstall /forceonly after verifying the package; forcing removal of a shared or unrelated Logitech driver can disable other hardware. - Remove profile data only if you want a factory-clean software reset. An uninstaller may leave product-specific profiles under
%AppData%,%LocalAppData%or%ProgramData%. These are not drivers. Delete only folders that clearly belong to the removed flight-control software, and do not erase an entire shared Logitech folder if you own other Logitech devices. Registry cleaners and manual service deletion are unnecessary. - Restart while everything remains disconnected. Check Installed apps and PnPUtil again. If you intend to reinstall, follow the clean Logitech/Saitek installation order for Windows 11 and connect each device only when the installer requests it.
Why does Windows reinstall the driver after removal?
Windows reinstalls a connected controller because every USB device needs either a Microsoft class driver or a third-party vendor driver.
A returning HID-compliant game controller with Microsoft listed as the provider is usually normal. Many yokes, joysticks and pedals use Windows components such as hidclass.sys and hidusb.sys; do not attempt to remove these system files.
If the specific Logitech/Saitek package returns, it was probably still present in the Driver Store or obtained through Windows Update. Keep the controller unplugged, repeat pnputil /enum-drivers and confirm that every package belonging to that product has gone before reconnecting it.
How do I verify that the uninstall is complete?
The vendor driver is fully removed when its software, device instances and matching Driver Store packages are all absent.
- No relevant Logitech G Flight, Saitek, SST or product-specific panel entry remains in Installed apps.
- Device Manager shows no present or greyed-out entry bearing the affected product’s name.
pnputil /enum-driversshows no third-party package belonging to that controller.- No associated profiling utility or tray application starts after rebooting.
Microsoft HID and USB drivers will remain, which is expected. If a cleanly reinstalled control still fails, use our checks that separate driver faults from USB, calibration and simulator-profile problems.
Will uninstalling the drivers erase simulator bindings?
Usually not, because simulators store control profiles separately from the Windows driver package. However, Windows can register the reconnected hardware as a new device instance, causing a simulator to show an empty profile, duplicate controller or missing assignments.
After reinstalling, open the simulator’s controls page and verify the pitch, roll, yaw, throttle and brake axes before flying. Watch especially for duplicated axis assignments: automatic profiles often bind the same control to both the yoke and another connected device.