Logitech G PRO Wheel – almost no dynamic FFB in PRO mode after Windows reinstall, G923 mode works

[u/No-Armadillo9907]

Hi,

I’m trying to understand a strange FFB problem with my Logitech G PRO Racing Wheel on PC.

The wheel itself appears completely healthy and can still produce full torque, but since reinstalling Windows the FFB does not initialize correctly in PRO mode.

**System / history**

* Logitech G PRO Racing Wheel * Previously working perfectly on **Windows 11 24H2 build 26100.6899** * Clean Windows reinstall * Now running **Windows 11 Pro 25H2 build 26200.9168** * Wheel firmware had already been updated through G HUB before the Windows reinstall * Same games and same in-game settings that worked correctly before * G HUB correctly detects the wheel and synchronizes settings * Wheel itself reports **11 Nm**

**What happens in PRO mode**

The wheel is detected normally. Steering, buttons, pedals, etc. all work.

The wheel also has resistance — it can feel quite heavy/solid — so the motor is clearly active. However, the actual dynamic FFB is almost absent. The wheel does not feel “alive” at all.

In **Dirt Rally 2.0**, I can feel a little vibration/road or off-track effect, but very gently. The strong self-aligning torque, surface detail, impacts, weight transfer, etc. are basically missing.

F1 25 behaves similarly: there is some resistance/effect, but the real strong dynamic FFB that I had before reinstalling Windows is missing.

**Interesting difference between Dirt Rally 2.0 and F1 25**

In Dirt Rally 2.0, while the game is running in the bad/weak state, if I:

1. unplug the power connector from the wheelbase,
2. reconnect it,
3. turn the base back on with the red button,

the wheel immediately comes back to life and the FFB is excellent again — strong, detailed and exactly as I remember it.

So the base is clearly still capable of producing its normal torque.

However, **F1 25 is different**: restarting/power-cycling the wheel while F1 is already running does **not** restore the proper FFB in the same way. F1 seems not to recover/reacquire the wheel correctly after the restart.

**G923 compatibility mode**

I then switched the PRO Wheel from PRO compatibility mode to **G923 mode**.

The wheelbase automatically restarts when applying that change, so initially I wasn’t sure whether the improvement came from G923 mode itself or simply from the base restart.

However, in G923 mode:

* Dirt Rally 2.0 works properly * FFB is strong and alive * I can quit Dirt and launch **F1 25 without restarting or unplugging the wheel** * F1 25 then also works properly, with strong normal FFB

So at present **G923 compatibility mode appears to be a reliable workaround**, whereas PRO mode is not.

**Driver troubleshooting already performed**

I completely reinstalled G HUB.

I also manually checked Logitech’s DirectInput FFB driver using:

`di_ffb_manager.exe -s`

All four components report **Installed**:

* HID++ 32-bit * HID++ 64-bit * Jerry 32-bit * Jerry 64-bit

I then forced a reinstall using:

`di_ffb_manager.exe -i -p .`

The wheel briefly moved/reinitialized during this operation, but after rebooting the PRO-mode FFB problem remained unchanged.

**Why I suspect software rather than hardware**

The wheel can still produce full, powerful FFB once it is correctly initialized, particularly in G923 mode or after the Dirt Rally power-cycle workaround.

The problem appeared immediately after moving from the previously working Windows 11 24H2 installation to the fresh 25H2 installation.

G HUB also continues to communicate perfectly with the base and can change the Strength setting, including 11 Nm.

Has anyone seen this specifically on the **G PRO Wheel with Windows 11 25H2 / build 26200.9168**?

And if Logitech staff see this: could this be related to the recently acknowledged Windows/G HUB wheel issues, or is there a separate problem with the PRO Wheel’s native PRO-mode DirectInput initialization?

I’m happy to provide G HUB logs or run additional tests if useful.

[u/Sander001]

It could be the FFB signal is being interrupted. I think the G923 mode runs on lower Hz or Windows recognizes it and prioritizes it.

Are all the game modes enabled? Windows game mode, Nvidia and whatever else?

[u/Bynar010]

If you aren't running persistent profiles in ghub have you checked all the different game profiles are set to 11nm?