Windows 11

SideWinder FFB2 force feedback on Windows 11.

Windows 11 can still see the Microsoft SideWinder Force Feedback 2 through the built-in HID-PID / DirectInput stack. FFB-Bridge uses that stack to drive force feedback from MSFS 2024 and X-Plane telemetry.

Download for Windows Windows install docs
FFB-Bridge first launch safety prompt before enabling SideWinder FFB2 force feedback
The first launch flow starts with safety acknowledgement before any force output can be armed.
Windows facts
OS
Windows 10 1809+ and Windows 11
Driver
Built-in HID-PID / DirectInput
Installer
Per-user, no admin required
Warning
Unsigned beta may trigger SmartScreen or SAC
No driver hunt

The stick is class-driver hardware.

You do not need an old Microsoft SideWinder driver package. Plug in the USB FFB2 and confirm it appears as VID 045E PID 001B.

Install guide
Beta trust

SmartScreen and Smart App Control

The beta installer is not code-signed. SmartScreen can warn on first run, and Smart App Control can block unsigned apps until you allow the first launch path.

Download and trust notes
Stability

DirectInput pid.dll work

Beta.11 keeps compact hardware mode as the default, adds faster MSFS pause recovery, and preserves a neutral spring while paused.

Beta.11 changelog
First Run

What to check before flying.

Windows support is mostly straightforward once the unsigned-beta warning is understood.

FFB-Bridge Doctor page with SideWinder FFB2 hardware compatibility checks
Doctor can verify device access and run hardware checks if Windows force output behaves strangely.
Device lamp green The bridge sees the FFB2 and can open it for force output.
Close other FFB tools Diagnostic utilities can hold exclusive access to the same DirectInput device.
Use Doctor if it crashes Doctor can run the hardware-effect probe and suggest software-blended periodics if needed.
Windows 11 FAQ

Common Windows questions.

Do I need old Microsoft SideWinder drivers?

No. The USB SideWinder Force Feedback 2 uses the built-in Windows HID-PID / DirectInput stack.

Why does SmartScreen warn on first launch?

The beta installer is not code-signed yet. SmartScreen may show an unrecognized-app warning until code-signing is in place for 1.0.

What should I do if another tool has the stick open?

Close other joystick or force-feedback utilities before arming FFB-Bridge. They can hold exclusive access to the same DirectInput device.

What changed in beta.11 for Windows?

Beta.11 keeps compact hardware mode as the fresh-install default, makes Doctor and runtime agree on the active mode, drives output at 95%, and handles MSFS pause / Active Pause without leaving the stick limp.

Windows 11 is supported, with beta trust caveats.

Read the download page before first launch if SmartScreen or Smart App Control is new to you.

Open download page Troubleshooting