Racing sim enthusiasts who fire up their Logitech G920 wheel this week may be greeted by an unwelcome surprise: dead silence, no force feedback, or Windows refusing to acknowledge the device at all. Across forums and social channels, users report a spike in G920 recognition failures, often surfacing within days of a routine Windows update or a Logitech G HUB software refresh. While neither Microsoft nor Logitech have publicly acknowledged a systemic bug, the fix follows a remarkably consistent pattern—one that zeroes in on four predictable areas where the wheel’s chain of communication breaks down.
This guide walks through the exact checks that resolve the vast majority of G920 issues on Windows 10 and 11, drawn from current user reports and official hardware troubleshooting documentation. No single fix works for everyone, but methodically working through these layers—power, USB, G HUB, and the operating system’s own game controller panel—can turn a paperweight back into a precision sim racing tool.
Where the G920’s Chain of Command Falls Apart
The Logitech G920 relies on a surprisingly fragile daisy chain: wall power feeds a motorized base, which connects to the PC over USB, where Logitech G HUB translates those signals into DirectInput commands before they reach any game. A break anywhere in that sequence renders the wheel invisible or unresponsive. The most common failure points, according to aggregated user reports, are mundane: a loose power barrel connector, a USB port that’s entered selective suspend, a G HUB update that silently swaps a driver, or a Windows feature update that resets the calibration or mapping profiles.
Anecdotal evidence points to a recent uptick after the March 2025 Windows 11 cumulative update (KB5053598) and the corresponding Windows 10 build, which reportedly altered USB power management policies for some systems. Logitech G HUB version 2025.2, released in late February, introduced new device detection logic that appears to have confused the G920’s initial handshake on certain configurations. The result is a perfect storm for users who reboot their rigs to find the wheel completely lifeless.
How to Resuscitate Your G920: A Layer-by-Layer Approach
Before you reinstall drivers or roll back Windows, start with the simplest, most frequent culprit. Each step below is independent—skip around if you’ve already tried one—but working top-down mimics the signal path and catches the majority of field issues.
1. Verify Power and Cabling
Unplug the wheel’s power adapter from the wall and from the wheel base. Inspect the barrel connector for bent pins, debris, or an incomplete insertion—this is the single most common failure reported on Logitech forums. The LED on the G920’s base should light solid green when power is applied; if it’s dark or flickering, try a different outlet and ensure the cable is fully seated. The power brick itself can fail, so if you have access to a multimeter, confirm the adapter outputs 24V DC. Without stable power, none of the following steps matter.
2. Test a Direct USB Connection
Bypass any USB hubs, extensions, or front-panel ports. Plug the G920’s USB cable directly into a USB 2.0 port on the back of the PC. USB 3.0 ports (blue) can cause intermittent disconnects due to driver conflicts, as documented in Logitech’s own support notes. If possible, test on a different PC altogether—if the wheel works there, the problem is isolated to your Windows configuration. For persistent USB handshake failures, open Device Manager, expand “Human Interface Devices” and “Universal Serial Bus controllers,” and look for devices with yellow exclamation marks. The G920 often appears as “Logitech G920 Driving Force” under “Sound, video and game controllers”; if it’s missing or error-coded, proceed to driver reinstallation.
3. Repair or Reinstall Logitech G HUB
Logitech G HUB is notorious for partial updates that leave the wheel unrecognized. Begin by completely quitting G HUB from the system tray. Then navigate to C:\Program Files\LGHUB\ and run lghub_updater.exe as administrator. If the updater finds a patch, let it install and restart the PC. If that fails, uninstall G HUB—use the “Programs and Features” control panel, then manually delete leftover folders in %APPDATA%\LGHUB and %LOCALAPPDATA%\LGHUB—and install the latest version from Logitech’s website. During installation, connect the G920 only when prompted; this forces a clean device detection. After installation, open G HUB and confirm the wheel appears with the correct firmware version. As of this writing, the latest public firmware is 108.1.64, though your unit may vary.
4. Calibrate via joy.cpl
Windows’ own game controller settings offer a hardware-level test that bypasses G HUB entirely. Press Windows+R, type joy.cpl, and hit Enter. If the G920 appears in the list, select it and click Properties. Under the “Test” tab, turn the wheel and press the pedals—all inputs should register smoothly. If they don’t, click the “Settings” tab and hit “Calibrate” to re-learn center and endpoints. If the wheel does not appear in joy.cpl at all, Windows has lost the device driver. In that case, uninstall the device in Device Manager (right-click and choose “Uninstall device,” checking “Delete the driver software for this device”), then disconnect and reconnect the USB cable to trigger a fresh driver installation.
5. Check In-Game Controller Profiles
Many racing titles—Assetto Corsa, iRacing, Forza Motorsport—maintain their own controller binding files. A Windows update can reset a game’s configuration, defaulting to keyboard or an Xbox pad. Inside the game’s options, navigate to Controls and ensure the G920 is the selected preset. Some games also require you to manually map the wheel’s axis and pedals. If the wheel is detected but force feedback is missing, verify that G HUB’s feedback settings are enabled and that the game’s FFB profile isn’t corrupted. A quick test: launch G HUB, then launch the game; if FFB returns, create a persistent profile in G HUB for that executable.
Why the G920 Is Particularly Prone to These Glitches Right Now
The G920 is a mature piece of hardware, first released in 2015, and its reliance on the older DirectInput API makes it sensitive to changes in Windows’ USB and driver infrastructure. Microsoft has gradually hardened USB Selective Suspend behavior with each feature update, which can inadvertently cut power to the wheel when it’s idle. The March 2025 cumulative update is reported to have tightened those policies further, especially for devices that draw more than 500 mA—the G920 pulls significantly more for force feedback.
Logitech’s G HUB software, meanwhile, has undergone a complete rewrite twice in the wheel’s lifetime. Each major iteration has broken backward compatibility with some previous firmware/hardware combinations, leaving users who skip updates stranded. The February 2025 release (2025.2.x) aimed to unify detection across the G29, G920, and G923 lines but inadvertently caused the G920 to drop into a bootloader mode on some systems, requiring a manual driver intervention. Logitech has not yet issued a formal acknowledgment, but community workarounds appear to resolve it.
Keeping the Wheel Alive: Long-Term Prevention
A few proactive settings can drastically reduce the odds of a repeat failure. First, disable USB selective suspend for the port used by the G920: open Power Options, click “Change plan settings” beside your active plan, then “Change advanced power settings.” Expand “USB settings” and set “USB selective suspend” to Disabled. This prevents Windows from cutting power during a race. Second, in Device Manager, right-click the G920 under “Sound, video and game controllers,” go to the Power Management tab, and uncheck “Allow the computer to turn off this device to save power.” Third, set G HUB to run at startup minimized, which ensures the wheel’s profile loads before any game. Finally, regularly check Logitech’s G920 downloads page for firmware updates that address compatibility.
What to Watch For
Logitech typically addresses wheel-detection bugs through both G HUB patches and downstream driver bundles offered via Windows Update. Monitor the r/LogitechG subreddit and Logitech’s own community forums for pinned announcements. Microsoft rarely comments on specific peripheral compatibility, but if a future Windows update breaks the G920 widely, it may be documented in known issues. For now, the four-step diagnostic described here should restore normal operation in under fifteen minutes. If your wheel is still unresponsive after completing every step, contact Logitech Support to check warranty status or request a power brick replacement—the adapter is a known point of long-term failure.
Racing sim hardware lives at the messy intersection of operating systems, driver stacks, and game engines. The G920’s current spate of troubles is frustrating but ultimately fixable, and a methodical approach almost always ends with a green LED and a working wheel.