Wi-Fi works but Bluetooth is missing after a PCIe card install

Data reviewed October 22, 2026 · By Weerasak

Document-based guide · Methodology and limits

Quick answer

On many desktop PCIe Wi-Fi/Bluetooth adapters, the radio module uses the PCIe connection for Wi-Fi and a separate internal USB connection for Bluetooth. Working Wi-Fi therefore does not prove that the Bluetooth path is connected. Identify the exact carrier card, follow its manual, inspect both ends of its supplied USB cable and only then move to driver or hardware conclusions.

First confirm that this is the same kind of installation

This guide addresses one precise post-install symptom: a desktop PCIe Wi-Fi/Bluetooth adapter has been fitted, Wi-Fi networks work, but Bluetooth is absent from Windows. The adapter must be a carrier card whose own instructions show a small cable from the card to an internal motherboard USB connector. It is not a general AX210 compatibility guide and it is not the correct procedure for a laptop, a USB wireless dongle or Wi-Fi built into a motherboard.

The distinction matters because the two functions can reach the system through different paths. Intel's AX210 specifications list PCIe for Wi-Fi and USB for Bluetooth, while the AX210 module brief lists an M.2 connector interface that includes PCIe and USB. The physical module can therefore provide working Wi-Fi while its Bluetooth side is not being detected. That split narrows the investigation; it does not, by itself, prove that the module or cable is faulty.

Carrier-card manuals make the desktop wiring visible. TP-Link's PCIe WLAN adapter Bluetooth guide connects the adapter through PCIe and directs the Bluetooth cable to the motherboard's F_USB connector. ASUS gives the same separate-cable step for its PCE-AX58BT installation example, and the Gigabyte GC-WBAX210 manual shows a USB cable between the installed card and a motherboard USB connector. Apply only the instructions for your exact adapter revision; similar-looking carrier cards can use different card-side connectors or cable wiring.

Read the symptom before changing anything

What each Windows result establishes
What you observe	What it supports	What remains unresolved
Wi-Fi adapter is listed and connects; no Bluetooth category or radio appears	The Wi-Fi side and at least part of the PCIe installation are operating	The carrier's USB cable, USB header, Bluetooth driver and Bluetooth hardware path still need checking
Wi-Fi works; an unknown USB device appears	Windows is seeing activity on a USB path	The result does not identify whether the cause is the cable, header, controller, driver, firmware or adapter
Intel Wireless Bluetooth is listed, but the Bluetooth control is missing	Windows has enumerated a Bluetooth adapter	Continue with Windows and driver troubleshooting before reopening the PC
Bluetooth appears and devices pair, but range or audio is poor	The Bluetooth path is present	This is a signal, antenna, interference or peripheral problem—not the missing-hardware symptom covered here

Record the adapter names and any warning symbol in Device Manager before uninstalling a driver. A screenshot preserves evidence that can be lost after a reboot. Do not use a Wi-Fi speed test as a Bluetooth test: the working Wi-Fi connection travels through the path that is already known to work.

Check the documented USB path with the PC powered off

Identify the complete adapter model and hardware revision. Read the label on the PCIe card or its box, not only the Intel module name displayed in Windows. Download the matching card-maker manual. The carrier manufacturer defines its cable and connector.
Identify the exact motherboard model and revision. Open its manual and locate the internal USB 2.0 headers. F_USB is not a universal printed name; a board may use another label. Match the connector diagram and location from the manual rather than choosing a header because its pins look close enough.
Shut the computer down and disconnect external power. Follow the case, adapter and motherboard safety instructions before removing the side panel. Do not move an internal cable while the system is energized.
Inspect the card-side connection. Confirm that the supplied Bluetooth USB cable is fully seated in the exact socket shown by the carrier manual. Do not substitute a fan, RGB or front-audio connector, and do not force a plug that does not align.
Inspect the motherboard-side connection. Confirm that the other end is on the documented internal USB connector and aligned as the manual shows. A one-row offset or the wrong header can prevent enumeration and can create electrical risk.
Check whether the header is already shared. If a case controller, cooler or lighting hub occupies the connector, do not splice wires or rearrange individual pins. Use only a hub, splitter or alternative connection explicitly supported by the relevant manufacturers, or leave Bluetooth disconnected and choose a separate supported solution.

The TP-Link Archer TXE72E user guide explicitly tells the installer to seat the PCIe adapter and connect its Bluetooth USB cable to an available F_USB connector. That is strong evidence for that product family, not permission to assume every generic AX210 carrier has the same connector or pinout. If the card arrived used and its original cable is missing, obtain the exact replacement from the card maker or seller instead of buying by appearance.

Check Windows after restoring power

After reconnecting power and booting, open Device Manager. Look separately under Network adapters, Bluetooth and Other devices. If Bluetooth now appears, the physical connection was material to the symptom. If it remains absent, preserve the observed device names and continue in a controlled order.

For a branded PCIe adapter, start with the driver package and support page for that exact adapter and revision. For a prebuilt computer, use the system maker's packages when it provides customized drivers. Intel publishes a clean Bluetooth driver installation procedure for Intel wireless Bluetooth, but installing software cannot repair an absent or incorrectly wired USB connection. Avoid registry edits, unofficial driver bundles and repeated random uninstall cycles; they make the original state harder to diagnose.

Microsoft's Bluetooth driver guidance covers updating, reinstalling and checking Windows Update. Its Bluetooth-disappeared procedure also begins with Windows troubleshooting and a complete shutdown before escalating. Follow those supported steps after the carrier cable and header match their manuals. Obtain chipset, USB-controller and BIOS updates only from the motherboard or complete-system manufacturer, using the instructions and warnings for the exact model.

Isolate one variable at a time

If the motherboard manual documents a second compatible internal USB 2.0 header and it is genuinely free, testing that header can help distinguish a header-specific problem from a carrier-side problem. Power down and disconnect power before moving the cable. Do not disconnect a pump controller, security device or other required component merely to run this test.

If another simple USB device is already documented to work on the same internal header through a supported connection, that is useful context, but it does not certify the Wi-Fi card's cable. Conversely, an unknown USB entry is not proof that the Bluetooth driver alone is at fault. Record what changes after each single action: cable reseat, alternate documented header, driver installation or firmware update. Changing all four at once hides the cause.

When the exact supplied cable is correctly connected, two documented headers produce the same result, and the manufacturer-supported Bluetooth driver still finds no Bluetooth device, contact the adapter maker with the card revision, motherboard model, BIOS version and Device Manager evidence. The remaining fault could be in the cable, carrier, wireless module, motherboard integration or firmware. A responsible diagnosis does not declare the AX210 module dead from the missing Bluetooth icon alone.

Mistakes that waste time or add risk

Reinstalling the Wi-Fi driver only. Wi-Fi and Bluetooth can have separate driver packages, and the Wi-Fi side is already working.
Assuming PCIe carries both functions on every carrier. The official examples above document a separate USB cable for Bluetooth.
Connecting by header name alone. F_USB, JUSB and similar labels must be confirmed in the exact motherboard manual.
Buying a visually similar replacement cable. The card-side connector and wiring are properties of the carrier product, not merely of the AX210 module.
Applying this desktop procedure to a laptop. A laptop's socket, USB routing, antennas, firmware approval and serviceability are system-specific, and there may be no user-accessible carrier cable.
Blaming antennas for a missing Device Manager entry. Antennas affect radio operation and range; they do not replace the host interface required for Windows to enumerate Bluetooth hardware.

Common questions

Does working Wi-Fi prove that the combo card is installed correctly?

It proves that the Wi-Fi side is operating. On the documented AX210 carrier designs in this guide, Bluetooth uses a separate USB path, so that connection and its driver remain independent checks.

Is JUSB the same thing as F_USB?

Those names are manufacturer labels, not a sufficient compatibility test. Use the motherboard manual to identify an internal USB connector with the layout required by the adapter manual. Never connect the cable to a fan, RGB, audio or other header because the pin count appears similar.

Can I test a different internal USB header?

Yes, if the motherboard manual identifies it as compatible, it is free and the PC is fully powered down before the cable is moved. A second result can help isolate the fault, but it does not make an unsupported cable or carrier compatible.

Should I replace the AX210 module first?

No. First verify the exact carrier instructions, supplied cable, motherboard header and supported Bluetooth driver. Replacing the module before checking its USB path can reproduce the same symptom with a new module.

What if Bluetooth worked before and disappeared later?

Begin with Microsoft's supported Bluetooth-disappeared steps and inspect Device Manager. If the PC was moved or serviced, also recheck the carrier cable with power disconnected. An intermittent symptom has more than one possible cause, so do not assume a loose cable without evidence.

If you are still choosing a wireless module rather than diagnosing an installed desktop carrier, use the related AX210-versus-AX211 guide. It covers PCIe/USB versus CNVio2, M.2 keying and exact-system support; this page intentionally does not repeat that purchase decision.

Sources and review scope

Official Intel interface specifications, adapter installation manuals and Windows troubleshooting documents checked October 22, 2026. This guide covers desktop PCIe Wi-Fi/Bluetooth carrier cards that document a separate internal USB cable. It does not diagnose a laptop, soldered radio, motherboard-integrated wireless module, USB dongle, unlisted cable pinout or every card sold with an AX210 module.