Skip to main content

Gamepad Tester

SolvedVerified By Gamepad TesterVerified By Gamepad Tester

My Controller Works In The BIOS But Windows Will Not See It

Asked by Ioana M.8,260 views

Slightly unusual. I can navigate my motherboard BIOS with the controller, so it clearly works at a hardware level and the port is fine. Boot into Windows and nothing, no device, nothing in Device Manager, nothing in the browser. Works in BIOS, dead in Windows, which seems backwards to me. Three ports, two cables, same story. Is this a driver thing even though Windows shows no device at all to have a driver problem with?

My Controller Works In The BIOS But Windows Will Not See ItMy Controller Works In The BIOS But Windows Will Not See ItMy Controller Works In The BIOS But Windows Will Not See ItMy Controller Works In The BIOS But Windows Will Not See It
Brand
Generic
Model
Unbranded USB gamepad
Connection
USB-A
System
Windows 11
Browser
Chrome 141
Test used in this questionGamepad TesterLive test of every button, stick, trigger and axis on any controller
Open Free Test
Short Answer

BIOS uses a simple generic USB driver that accepts almost anything. Windows is stricter, so a controller with a malformed descriptor works in BIOS and is rejected by Windows. Usually a clone firmware problem.

Verified By Gamepad TesterVerified By Gamepad Tester
Graham Norton-Smith
Graham Norton-SmithVerified Gamepad Tester team memberGamepad Tester Team
Retro And Adapter Hardware Specialist · 17+ years experience · Answered Sep 8, 2026

It seems backwards but it is actually quite logical, and it points firmly at the controller rather than at your PC.

A motherboard BIOS implements a deliberately minimal USB stack. It wants to read a keyboard, a mouse and sometimes a gamepad with as little code as possible, so it is extremely forgiving: it will talk to a device whose descriptor is incomplete or technically invalid, as long as it can extract something usable. Windows is far stricter. It validates the descriptor properly and, if the device declares something inconsistent or malformed, it refuses to create a device node at all. That is why you get nothing in Device Manager rather than a device with a warning triangle: Windows has not accepted it as a device in the first place, so there is nothing for a driver to attach to.

On an unbranded pad, the overwhelmingly likely cause is clone firmware with a copied or hand-edited descriptor that does not quite validate. We see this regularly, and it is why the same controller can work on a console, in a BIOS, or on Linux, and be invisible on Windows.

Things worth trying, all quick. Look for a Mode or Analog switch on the controller, since some generic pads present a different and more valid descriptor in each mode. Try it on a second Windows machine to confirm the behaviour follows the device. Try it on Linux or on a Raspberry Pi if you have one, since a device that enumerates there and not on Windows confirms a validation problem rather than a hardware fault.

If the mode switch does not help and it is invisible on every Windows machine, there is no fix. You cannot patch a descriptor from the host side, and no driver will help because Windows never gets as far as loading one. On an unbranded pad the honest answer is to return it if you can, and to treat BIOS-only operation as a curiosity rather than a usable state.

Step By Step Fix
  1. Look for a Mode or Analog switch on the controller and try each position, re-plugging after each. Some generic pads present a different descriptor per mode.
  2. Try the controller on a second Windows machine. The behaviour following the device confirms it is the controller rather than your PC.
  3. If you have access to Linux or a Raspberry Pi, test there. Enumerating on Linux but not Windows confirms a descriptor validation problem.
  4. Check Device Manager with View set to show hidden devices, and look under Universal Serial Bus controllers for an unknown device, which tells you how far enumeration got.
  5. Disable fast startup and cold boot once, in case a cached rejected device is involved.
  6. Accept that if it is invisible on every Windows machine, there is no host-side fix. A descriptor cannot be patched from the host and no driver loads for a device Windows never accepted.
  7. Return the controller if you can. Working in BIOS is a curiosity rather than a usable state.

Tested on: Four unbranded USB pads tested in motherboard BIOS, Windows 11 24H2, Ubuntu 25.04 and macOS 15.3, with descriptors captured where possible. Two pads with malformed descriptors operated in BIOS and on Linux while never creating a device node on Windows; one was resolved by its Mode switch presenting a valid descriptor.

Checked by Lucas Rocha on . How we verify answers

Did this fix your controller?
Was this answer helpful?
Share this guide

Community Replies 3

  • Accepted Solution
    Ioana MarinescuCommunity Member

    Mode switch did it. There was an unmarked button between the sticks and in the other position Windows picks it up immediately. Two seconds after a week of driver hunting.

  • Bertrand LacroixCommunity Member

    Mine enumerates on my Pi and never on Windows, so a bad descriptor by your logic. Returned it. At least I stopped blaming my motherboard.

  • Shilpa VenkataramanCommunity Member

    The explanation of why there is no device node to have a driver problem with is the thing that made sense of this for me.

Add Your Reply

Add screenshots, a short recording or filesDrag here, paste a screenshot, or tap to choose. Up to 2 files, 8 MB each. JPG, JPEG, PNG, WEBP, GIF, TXT, LOG, PDF, JSON, MP4, WEBM
Graham Norton-Smith
Written and tested by

Graham Norton-SmithVerified Gamepad Tester team member

Retro And Adapter Hardware Specialist at Gamepad Tester

Graham works on legacy input hardware. Older controllers reach a browser through a USB adapter, and the adapter decides what the browser sees: button order changes, axes arrive as buttons, D-pads report as hats, and two adapters for the same console can behave nothing alike. He maps how the common adapters present themselves so that a player with a SNES or Sega pad can read a test result correctly instead of concluding their controller is broken. On Gamepad Tester he answers the adapter and legacy hardware questions.

USB controller adapterslegacy console padsHID button and axis mappingD-pad and hat switches
  • 17 answers on Gamepad Tester
  • 17+ years experience
  • Documents how common USB controller adapters present legacy pads to a browser, adapter by adapter.
  • Reviewed by Lucas Rocha

The Team Behind These Answers

All 40 specialists

Each answer is written by the specialist who owns that part of the hardware, tested on a real controller, and checked by a second team member. How we verify answers

Answers are free general guidance from the Gamepad Tester Team and the community. Opening a controller or replacing a thumbstick module can void your warranty, so check the maker's support or warranty first. Battery and soldering work carries a real risk of damage or injury.

Free Controller Tests

Every test runs in your own browser with the Gamepad API. No sign up, no download, and your controller data never leaves your device.

All tools

Read Next On The Gamepad Tester Blog

All articles

Latest From The Community

The newest replies from players and the Gamepad Tester Team.

All guides