Nine times out of ten, a Thrustmaster wheel that Windows refuses to see is not broken. It is either plugged into a USB port it doesn’t like, stuck in bootloader mode after a botched firmware update, or fighting a driver install that went in the wrong order. I have owned a T150, a T300 RS GT, a TX with the Leather 28 rim, and a T-GT II over the years, and every single one of them has “died” on me at least once. All of them came back. The one that actually needed an RMA had a burnt smell, which is its own kind of diagnostic.
So the verdict up front: work through the steps below in order, do not skip the boring ones, and do not reflash firmware until you’ve ruled out the USB port and the base’s mode switch. Most people jump straight to firmware because it sounds like the serious fix. It’s also the step most likely to turn a “not detected” wheel into an “actually bricked” one if the cable drops out mid-flash.
First, figure out what “not detected” actually means
There are three different failures that people lump under this search, and they need different fixes.
The first is that the wheel does nothing. No calibration sweep when you power it, no LED, no sound from the base. That is a power problem, not a detection problem. Check the barrel connector on the back of the base is fully seated (the T300’s is notoriously loose and will back out a few millimetres if you move the base), check the brick’s own LED, and if you have a T-GT or T300, listen for the relay click. No click, no life, and it isn’t Windows’ fault.
The second is that the wheel calibrates (rim rotates lock to lock, centres itself) but Windows shows nothing in Game Controllers. This is the common one, and it’s what most of this article is about.
The third is that Windows sees it but sees it wrong: it appears as “Thrustmaster Bootloader” or some generic HID device, or it shows in Device Manager with a yellow triangle. That’s firmware territory, covered lower down.
Open the Windows Run box (Win+R), type joy.cpl, and hit Enter. That’s the fastest way to see what Windows actually thinks is plugged in. Leave it open while you work through the rest.
Step 1: The USB port. Yes, really.
Thrustmaster bases are picky about USB in a way that Logitech gear mostly isn’t, and it’s the single most common cause. Rules that hold across the whole range:
Plug directly into a motherboard USB port on the back of the PC. Not the front panel, not a hub, not the USB passthrough on your monitor. Front panel headers on a lot of cases are wired badly enough that a T300 will enumerate, drop, re-enumerate, and drop again, which looks in Device Manager like the wheel flickering in and out of existence.
Use a USB 2.0 port if your board still has one. USB 3.x ports work fine on most systems but there’s a known cluster of problems with certain ASMedia and older Intel XHCI controllers, and the Thrustmaster bases were designed in the USB 2.0 era. If you only have blue ports, try a different one anyway. Ports on the same controller behave the same; ports on different controllers do not. On an ATX board the top block near the PS/2 port is usually a different controller than the block near the Ethernet jack.
Try the cable. The T150 and TMX have a captive cable, so you’re stuck. The T300, TX, T-GT and T248 use a detachable one, and the stock cable is not great. A generic USB-A to USB-B (the square printer-style plug) from any drawer works. Cable faults present as intermittent detection rather than none at all, but it costs nothing to check.
If the wheel appears the moment you move ports, stop reading and go drive. You’re done.
Step 2: The mode switch
This catches a genuinely surprising number of people, including me, twice.
The T300 RS, TX, T-GT, and T-GT II have a small physical slider on the base. On the T300 it’s on the back, next to the ports, labelled PS3/PS4 (or PS4/PS5 on newer stock). On the TX it’s Xbox/PC-ish in behaviour but the same idea. That switch changes the USB descriptor the base presents to whatever it’s plugged into. In the wrong position, Windows either sees nothing at all or sees a device it doesn’t have a driver for.
For PC use on a T300, the switch should be in the PS3 position. Not PS4. I know that reads backwards. The PS4 mode uses an authentication handshake the console expects, and on PC it mostly just causes the base to sit there sulking. The T-GT II wants PS4/PS5 mode on console and generally works on PC in either, but if it isn’t detected, flip it and reconnect.
The T150 and TMX have a similar switch, also PS3/PS4 on the T150. PS3 for PC. The T248 and T128 don’t have one and auto-detect.
Power the base down, flip the switch, power it back up, and wait for the calibration sweep before you look at joy.cpl. Switching with the base powered doesn’t reliably take.
Step 3: Drivers, and why install order matters
Thrustmaster’s driver package is a single installer that covers the whole range, and it’s genuinely fine once installed. The problem is that it installs a bunch of things at once (the HID driver, the force feedback layer, the Control Panel applet, the firmware updater) and it is fussy about the base being unplugged during install.
Do this exactly:
- Unplug the wheel’s USB cable from the PC. Leave it powered if you like; it just can’t be enumerated.
- Uninstall any existing Thrustmaster driver from Apps & Features. If it errors out or claims nothing’s installed but you know something is, that’s worth noting for Step 5.
- Reboot. Not optional. The old driver stays resident until you do.
- Install the latest package from Thrustmaster’s support site for your specific base. Don’t use the disc, don’t use a driver you downloaded in 2019.
- Reboot again when it asks.
- Only now plug the wheel in. Wait for the Windows “setting up device” toast to finish before you touch anything.
The reboot steps are where people get impatient. If you skip them, the new driver installs alongside remnants of the old one and you get the classic symptom where the wheel shows in the Thrustmaster Control Panel but not in joy.cpl, or vice versa.
One more thing that isn’t in the manual: if you have any Fanatec or Logitech software installed on the same machine, it can interfere. Logitech G HUB in particular runs a HID filter that occasionally grabs devices it shouldn’t. I’m not saying uninstall it, but if you’re still stuck after a clean Thrustmaster install, killing lghub.exe and lghub_agent.exe in Task Manager and reconnecting the wheel is a useful five-second test.
Step 4: Check Device Manager, not just joy.cpl
Open Device Manager and expand “Human Interface Devices” and “Universal Serial Bus controllers”. Then plug the wheel in and watch what appears.
If you see “Thrustmaster T300RS Racing Wheel” (or your model) under HID, the driver’s working and any remaining problem is in the game, not Windows. Skip to the sim-specific section.
If you see “Unknown USB Device (Device Descriptor Request Failed)” the base is being seen electrically but isn’t handing over a valid descriptor. That’s either the mode switch (go back to Step 2) or, more seriously, a firmware issue (Step 5).
If you see “Thrustmaster Bootloader” or “TM Bootloader”, the base is in firmware recovery mode. This is actually good news, because it means the microcontroller is alive and the fix is a known one.
If nothing appears anywhere, not even a flicker in USB controllers, the base isn’t reaching the PC at all. Back to Step 1, and start suspecting the cable or the USB-B socket on the base itself. On T300s that get a lot of desk use, the socket can crack its solder joints. Gently wiggling the plug while watching Device Manager tells you a lot.
Step 5: Firmware, including the bootloader rescue
This is the section people arrive at too early, so I’ve put it late on purpose.
The Thrustmaster Control Panel (installed with the driver) has a Firmware Update tool. If your wheel is detected but on old firmware, and everything else works, updating it is fine but not urgent. Firmware updates on these bases fix specific things (the T300’s early firmware had a known FFB dropout under high load in ACC, for instance) and don’t generally add features. If it’s working, don’t touch it.
If your wheel is showing as “Thrustmaster Bootloader”, the update tool is exactly what you need. Open the Firmware Update tool with the wheel connected. It should detect the base in bootloader mode and offer to flash. Let it run, do not touch the cable, do not let the PC sleep. It takes a couple of minutes and the rim will do a full calibration sweep when it’s done.
If the base isn’t in bootloader mode but you need to force it there (because it’s half-dead, showing as an unknown device, or the normal update keeps failing), there’s a manual procedure. For the T300, TX, and T-GT: power the base off, hold the Mode button on the base (the small one near the USB, not the one on the rim), and power it on while still holding. The Mode LED should behave differently, either flashing or staying solid depending on the model. Release after a few seconds, and Windows should now see “Thrustmaster Bootloader”. Then run the Firmware Update tool.
For the T150 and TMX the procedure is similar but uses the button combination on the wheel itself. Thrustmaster’s support site has the exact steps per model, and they’re worth reading before you try it, because I’m giving you the T300 procedure from memory and I’d rather you didn’t brick a T150 on my say-so.
A warning that belongs here: do not flash firmware over a USB hub, over a flaky front port, or on a laptop running on battery. The failure mode of an interrupted flash is a base that sits in bootloader forever, and while it’s usually recoverable, “usually” is doing a lot of work in that sentence.
The “it’s detected but the game doesn’t see it” problem
If joy.cpl shows the wheel and you can see the axes moving in its Properties tab, Windows is done and the problem is the sim.
iRacing is the most forgiving. Go into Options > Controls, hit the Reset button next to the steering axis, and turn the wheel. If it doesn’t pick up, iRacing’s known issue is that it needs to be launched after the wheel is connected, so close it, reconnect, relaunch.
ACC is the fussiest. It uses a device enumeration that gets confused if the wheel wasn’t present at launch, and it has a habit of losing the binding entirely if you change USB ports between sessions. Delete Documents\Assetto Corsa Competizione\Config\controls.json and rebind. Ten minutes of work but it fixes it every time.
Le Mans Ultimate and rF2 share the same problem: the controller profile system stores the device by a GUID that changes if the USB path changes. Make a new profile rather than fighting the old one.
Gran Turismo 7 isn’t a PC issue, but people do search this from a console. If a T300 or T-GT isn’t detected on PS5, it’s almost always the mode switch. PS4 mode for GT7. The reverse of PC.
What actually fails on these bases
Since you’re here anyway, some honest texture on what breaks and what doesn’t.
The T150 and TMX are belt-and-gear hybrids with a brushed motor and they run hot. Their common failure is the motor driver overheating and cutting FFB mid-race, which is not a detection issue and isn’t fixable short of adding airflow. Detection failures on these are almost always the captive USB cable being crushed under a desk leg.
The T300 RS is the workhorse and it’s still a genuinely good base at around $300 with the GT rim, roughly 4 Nm of belt-driven torque. What fails: the USB-B socket cracking, the power connector loosening, and very occasionally the internal fan. The base is also sensitive to being run without the rim attached, which triggers a fault state that looks like “not detected” but is fixed by attaching the rim before power-on.
The T-GT II is the expensive one at around $800. Detection issues on it are rarer, but the firmware updater has been flaky since launch and the Discord regulars will tell you to update it from a USB 2.0 port only. That’s not folklore; it’s a repeated pattern in the support threads.
The T248 is the newer hybrid at around $350 and it’s the one I’d actually point a beginner at over a T150 now. Detection problems on it are almost exclusively driver install order, because it shipped after the current driver package was written and older installers don’t know it exists.
If your base is genuinely dead, meaning no power, burnt smell, or a bootloader that won’t take a flash, the options are Thrustmaster support (slow, but they do repair out of warranty for a fee) or replacement. If you’re replacing a T150, a Thrustmaster T248 is the sensible step up. If you’re replacing a T300, the conversation gets more interesting, because a Moza R5 bundle at around $400 is a direct drive base with more torque and none of the belt maintenance, and a Fanatec CSL DD at around $350 is the other obvious option if you can stomach Fanatec’s shipping lottery. Neither is a required upgrade, but I wouldn’t spend $300 on another belt base in 2026 unless I already had a drawer of Thrustmaster rims to keep using. Which, to be fair, I do.
FAQ
Why does my Thrustmaster wheel show up as “Bootloader”? The base is in firmware recovery mode, usually because a firmware update was interrupted or because the mode button was held during power-on. Run the Firmware Update tool from the Thrustmaster Control Panel with the wheel connected and let it complete. The base isn’t broken.
Does the T300 need to be in PS3 or PS4 mode for PC? PS3. The PS4 position uses a console authentication mode that mostly just prevents Windows from enumerating the device properly. Power off, flip to PS3, power on, wait for calibration.
Can I use a USB hub with a Thrustmaster wheel? You can, and it sometimes works, but it’s the first thing I’d remove when troubleshooting and the last thing I’d do during a firmware flash. Powered hubs are less bad than unpowered ones. A motherboard port is still the right answer.
Before you order a replacement
Check, in this order, and actually do all of them: motherboard USB 2.0 port, mode switch in PS3 position (T150/T300/TX), rim attached before power-on, clean driver reinstall with both reboots, then Device Manager to see whether it’s bootloader or nothing at all. If you get to the end of that list and Device Manager shows nothing while the rim still calibrates on power-up, the USB-B socket or its cable is the suspect, and a $6 printer cable is a cheaper test than a new base. Only if the base doesn’t calibrate at all, or a bootloader flash fails twice from a motherboard port, is it time to look at that Moza or T248 page.