F5F Stay Refreshed Hardware Desktop TP-Link AX1800 WiFi and Bluetooth PCIe adapter fails to activate during startup.

TP-Link AX1800 WiFi and Bluetooth PCIe adapter fails to activate during startup.

TP-Link AX1800 WiFi and Bluetooth PCIe adapter fails to activate during startup.

S
SpiritClaws
Member
217
01-11-2026, 03:09 AM
#1
Hello everyone! I recently purchased an AX1800 WiFi and Bluetooth PCIe adapter from tp link (model: Archer TX20E(UN) Ver 1.0). It functions well most of the time, but after shutting down the computer and restarting it, the Bluetooth feature stops working. In Device Manager, the status shows "Windows has stopped this device because it has reported problems (Code 43)." The Event Viewer records two setup events: one about a timeout with the adapter ("A command sent to the adapter has timed out...") and another indicating the driver was unloaded. After removing the adapter and running "Scan for hardware changes," the Bluetooth works again. The Wi-Fi remains functional at startup. I’ve updated the drivers from the official site and kept Windows updates current. Have anyone experienced this issue? Would it help if you could automate the removal and reinstallation process?
S
SpiritClaws
01-11-2026, 03:09 AM #1

Hello everyone! I recently purchased an AX1800 WiFi and Bluetooth PCIe adapter from tp link (model: Archer TX20E(UN) Ver 1.0). It functions well most of the time, but after shutting down the computer and restarting it, the Bluetooth feature stops working. In Device Manager, the status shows "Windows has stopped this device because it has reported problems (Code 43)." The Event Viewer records two setup events: one about a timeout with the adapter ("A command sent to the adapter has timed out...") and another indicating the driver was unloaded. After removing the adapter and running "Scan for hardware changes," the Bluetooth works again. The Wi-Fi remains functional at startup. I’ve updated the drivers from the official site and kept Windows updates current. Have anyone experienced this issue? Would it help if you could automate the removal and reinstallation process?

1
10th_Doctor_
Posting Freak
768
01-16-2026, 07:00 AM
#2
Check if your BIOS is current and then reinstall the USB header from the card along with the card itself.
1
10th_Doctor_
01-16-2026, 07:00 AM #2

Check if your BIOS is current and then reinstall the USB header from the card along with the card itself.

K
kooky670
Junior Member
20
01-18-2026, 01:45 AM
#3
Welcome to the forums! This seems unusual. If Ski's rec doesn't resolve the issue, I recommend reaching out to customer support. These problems should be very secure. There might be some Windows corruption, so you could run sfc or dism. If you have another drive, try a clean installation of Windows. AutoHotKey doesn't seem to work well with it, and there aren't obvious command-line options in devmgmt.msc. However, a Windows tool appears to help—check the link provided: https://learn.microsoft.com/en-us/window...ext=Change device settings DevCon Just be careful with it.
K
kooky670
01-18-2026, 01:45 AM #3

Welcome to the forums! This seems unusual. If Ski's rec doesn't resolve the issue, I recommend reaching out to customer support. These problems should be very secure. There might be some Windows corruption, so you could run sfc or dism. If you have another drive, try a clean installation of Windows. AutoHotKey doesn't seem to work well with it, and there aren't obvious command-line options in devmgmt.msc. However, a Windows tool appears to help—check the link provided: https://learn.microsoft.com/en-us/window...ext=Change device settings DevCon Just be careful with it.

W
W_O_L_F_R_A_M
Member
125
01-18-2026, 03:17 PM
#4
Hey! Glad you got the responses. Updating bios, reseating the card, and using a different USB port helped a bit, but sfc and dism didn’t fix it. I haven’t tried reinstalling Windows yet. My old PC is pretty outdated—12 years old, Z77A G45 from 2012—and the adapter came out in 2023. Could there be an issue with the motherboard compatibility?
W
W_O_L_F_R_A_M
01-18-2026, 03:17 PM #4

Hey! Glad you got the responses. Updating bios, reseating the card, and using a different USB port helped a bit, but sfc and dism didn’t fix it. I haven’t tried reinstalling Windows yet. My old PC is pretty outdated—12 years old, Z77A G45 from 2012—and the adapter came out in 2023. Could there be an issue with the motherboard compatibility?

R
robbie172
Member
63
01-18-2026, 06:01 PM
#5
I think the adapter might be the issue, though it could also be a failing motherboard or a corrupted Windows setup. My confidence leans toward the adapter. If someone else has another PC, try installing it there to check. If it remains problematic, your card is likely faulty. Running a Linux live USB on your current machine can help determine if the problem is with Windows itself—if it persists, you may need to reinstall. Keep in mind that SSDs are affordable now, so if you don’t want to erase your existing data, consider swapping drives, installing Windows again, and testing.
R
robbie172
01-18-2026, 06:01 PM #5

I think the adapter might be the issue, though it could also be a failing motherboard or a corrupted Windows setup. My confidence leans toward the adapter. If someone else has another PC, try installing it there to check. If it remains problematic, your card is likely faulty. Running a Linux live USB on your current machine can help determine if the problem is with Windows itself—if it persists, you may need to reinstall. Keep in mind that SSDs are affordable now, so if you don’t want to erase your existing data, consider swapping drives, installing Windows again, and testing.

O
OKNK
Member
231
01-18-2026, 06:59 PM
#6
I tried it on a Linux live USB and Bluetooth stayed active every time the system booted. I chose to clear the main drive and reinstall Windows—it now functions at startup! Thanks @OddOod!
O
OKNK
01-18-2026, 06:59 PM #6

I tried it on a Linux live USB and Bluetooth stayed active every time the system booted. I chose to clear the main drive and reinstall Windows—it now functions at startup! Thanks @OddOod!