📎 AI Summary:
The thread is about a TP-Link/TX201 Realtek NIC not being detected in Windows, preventing driver installation. The main guidance was that this isn’t a driver issue when the card doesn’t enumerate (including Code 45 / “ghost” entries), so contributors focused on reseating the card, trying another PCIe slot, disabling fast startup, and checking BIOS/PCIe settings, with a Linux live test suggested to rule out faulty hardware. Sentiment was problem-solving and practical; the original poster later reported the issue was resolved, with a brief post-fix checklist to confirm stable link/adapter settings.
The thread is about a TP-Link/TX201 Realtek NIC not being detected in Windows, preventing driver installation. The main guidance was that this isn’t a driver issue when the card doesn’t enumerate (including Code 45 / “ghost” entries), so contributors focused on reseating the card, trying another PCIe slot, disabling fast startup, and checking BIOS/PCIe settings, with a Linux live test suggested to rule out faulty hardware. Sentiment was problem-solving and practical; the original poster later reported the issue was resolved, with a brief post-fix checklist to confirm stable link/adapter settings.
Solution
Got it. If the TX201 doesn’t appear anywhere in Device Manager, the driver installers won’t run because Windows doesn’t see any matching hardware. Work through these steps in order until it shows up.
Hardware and BIOS checks
3) See if Windows is enumerating anything for it
6) Boot a live Linux USB (you used Slax before)
Hardware and BIOS checks
- Cold power cycle and reseat
- Shut down, switch off PSU/unplug power, hold the power button 10 seconds.
- Reseat the TX201 firmly; try a different PCIe slot if available.
- Check the switch/router port LED and the NIC’s link LED with a cable plugged in.
- BIOS/UEFI
- Load Optimized Defaults, then:
- Set the PCIe slot Link Speed to Gen3 or Auto (not Gen4-only).
- Disable Fast Boot for this test.
- If there’s a setting to enable/disable the slot, make sure it’s Enabled.
- Update motherboard BIOS and chipset drivers (Intel/AMD) from the board vendor.
3) See if Windows is enumerating anything for it
- Open Device Manager:
- View > Show hidden devices.
- Look under “Network adapters” and “Other devices” for Unknown device or Realtek/TP‑Link entries.
- Action > Scan for hardware changes.
- PowerShell (run as admin):
- List network-class devices:
Get-PnpDevice -PresentOnly -Class Net | ft Status,InstanceId,FriendlyName -Auto - Search for the Realtek vendor ID (10EC) or the RTL8125 device ID:
Get-PnpDevice -PresentOnly | ? { $_.InstanceId -match 'VEN_10EC|DEV_8125' } | ft Status,InstanceId,FriendlyName -Auto - If nothing shows, Windows is not seeing the card at all (points back to slot/BIOS/hardware).
- Pre-install the driver anyway (so it binds as soon as the card enumerates)
- Extract the TP‑Link or Realtek package so you can see the .INF files.
- Admin CMD/PowerShell:
pnputil /add-driver "C:\Drivers\TX201*.inf" /install - Then Device Manager > Action > Scan for hardware changes.
- Look for OS clues
- Event Viewer > Windows Logs > System, filter by source “Kernel‑PnP” around boot. If the device enumerates with an error you’ll see it; if there’s nothing, it’s not enumerating.
6) Boot a live Linux USB (you used Slax before)
- Run: lspci | grep -i realtek
- The TX201 (RTL8125) should appear (vendor 10ec, device 8125). If Linux also can’t see it, it’s a slot/card issue.
- Try the card in another PC (quickest way to rule out the card).
- If it works elsewhere, your motherboard slot/BIOS is the culprit; if it fails elsewhere, the card is likely faulty.
- Right‑click > Update driver > Browse my computer > Let me pick > Have Disk and point to the extracted INF you pre-installed.
- Also check Core Isolation/Memory Integrity: Settings > Privacy & security > Windows Security > Device security > Core isolation. If On, and the driver is old/unsigned, it may block loading. Turn it Off temporarily to test, then update to a signed driver.
- What you see in Device Manager (including “Other devices”),
- The output of the two PowerShell lines above,
- Whether lspci in Linux shows the Realtek device,
and I’ll tell you the exact next step (slot/BIOS fix vs. driver bind).
Code 45 means Windows isn’t seeing the card at the hardware (PCIe) level right now. It’s not a driver problem. The “Realtek PCIe 2.5GbE Family Controller” entry you’re clicking is a ghost from when it previously enumerated; Windows is telling you it’s no longer physically present.
Do this in order (most effective first)
1) Cold power cycle and reseat
Do this in order (most effective first)
1) Cold power cycle and reseat
- Fully shut down: Win+X > Shut down or “shutdown /s /t 0”.
- Switch off PSU/unplug power. Hold the power button 10–15 seconds to drain.
- Reseat the TX201 firmly; move it to another PCIe slot if you can (avoid risers/adapters). Tighten the bracket screw so it can’t lift.
- Plug in and boot. Check Device Manager again.
- Disable Fast startup (Control Panel > Power Options > Choose what the power buttons do > uncheck “Turn on fast startup”), then shut down and boot.
- Device Manager > View > Show hidden devices. Under Network adapters, right‑click any greyed “Realtek PCIe 2.5GbE…” entries > Uninstall device (check “Delete driver software” if offered). Action > Scan for hardware changes.
- Load BIOS defaults. Then:
- PCIe slot Link Speed: Auto or Gen3 (don’t force Gen4).
- PCIe ASPM/Active State Power Management: Disabled (just to test).
- Fast Boot: Disabled (test).
- Ensure the slot is Enabled (some boards let you disable a slot).
- Update motherboard BIOS and chipset drivers.
- Admin PowerShell:
Get-PnpDevice -Class Net | Format-Table Status,Problem,InstanceId,FriendlyName
Get-PnpDevice | Where-Object InstanceId -match 'VEN_10EC|DEV_8125' | Format-Table Status,Problem,InstanceId,FriendlyName - Event Viewer > Windows Logs > System, filter by “Kernel-PnP” around boot for errors on that PCI bus.
- Boot a Linux live USB on this PC (or move the card to another PC). If lspci doesn’t show the Realtek RTL8125 (VEN_10EC, DEV_8125), it’s a hardware/slot issue. If it does show there but not here, it’s your board/slot.
- Pre‑install the driver so it binds immediately:
pnputil /add-driver "C:\Path\To\Driver*.inf" /install - Then Device Manager > Scan for hardware changes.
Great—glad the TX201 is showing again.
Post‑fix checklist (quick):
Post‑fix checklist (quick):
- Verify link speed: in admin PowerShell run
Get-NetAdapter | ft Name,Status,LinkSpeed - Re‑apply the stable NIC settings if needed (these sometimes reset after reseat/slot changes):
- Disable: Advanced EEE, Energy‑Efficient/Green/Gigabit‑Lite
- Flow Control: On
- LSO v2 (IPv4/IPv6): Disabled if you previously needed it for stability
- Buffers: Rx 512, Tx 4096 (or driver max allowed)
- Speed & Duplex: Auto Negotiation
- Power Management: uncheck “Allow the computer to turn off this device” on the NIC.
- Optional: update motherboard BIOS/chipset and keep the TP‑Link/Realtek driver you found stable.
