An external GPU that isn’t detected on a laptop usually shows up in one of a few ways: the enclosure’s fans spin and its lights come on, but the GPU never appears in Device Manager; Device Manager shows it with a yellow warning icon labeled “Code 12,” “Code 43,” or “Unknown device”; or your eGPU software utility (such as AMD’s XG Mobile utility, a Thunderbolt control panel, or the enclosure vendor’s own app) simply lists nothing connected. Games may still run — but only on the laptop’s integrated graphics — and the external monitor plugged into the eGPU stays black or falls back to the internal display. Sometimes the GPU appears and disappears intermittently, disconnecting the moment a game launches.
This is not an emergency, but it is worth fixing promptly. A non-detected eGPU means you paid hundreds of dollars for hardware that is doing nothing, and repeated failed handshakes over Thunderbolt can occasionally leave stale driver entries that make future connections harder. Work through the fixes below in order — they go from the easiest and most common solutions to the more involved ones, and most people resolve the problem within the first three fixes.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| Cable, port, or enclosure power issue | Swap the Thunderbolt/USB-C cable; try a different port; check the enclosure’s PSU is fully seated and its switch is on | Easy |
| Thunderbolt driver or firmware out of date | Device Manager shows “Thunderbolt Controller” with a warning icon, or Intel Thunderbolt Software reports an outdated firmware version | Easy |
| GPU not authorized in Thunderbolt settings | Open the Thunderbolt icon in the system tray; the device appears under “Manage Attached Devices” but shows as “Not connected” or prompts for approval | Easy |
| Stale or conflicting GPU drivers | Device Manager shows the GPU under “Other devices” or with Code 43; Display Driver Uninstaller (DDU) reveals leftover entries from a previous card | Moderate |
| BIOS setting blocking the eGPU above the internal GPU | Laptop BIOS has options like “Discrete GPU Priority,” “Above 4G Decoding,” or “Thunderbolt Boot Support” set incorrectly | Moderate |
| Insufficient PCIe resources (Code 12) | Device Manager error reads “This device cannot find enough free resources that it can use (Code 12)” | Moderate |
| Hardware failure in the GPU, enclosure, or laptop port | GPU and enclosure work in another machine, or a known-good GPU fails in your enclosure on multiple laptops | Hard |
Fix 1: Power-Cycle the Entire Chain
What causes it
Thunderbolt and USB4 controllers cache the last negotiation state. If a handshake partially failed — for example, the laptop woke from sleep while the enclosure was connected — the controller can refuse to re-enumerate the GPU until everything is fully discharged and restarted.
How to check
If the enclosure’s fans spin but Device Manager (right-click Start, select Device Manager) shows no change at all when you plug in, and a simple replug hasn’t helped, a stale handshake state is likely.
What to do
Shut down the laptop completely (hold Shift while clicking Shut Down to skip Fast Startup). Unplug the enclosure’s power supply from the wall, press and hold its power button for 15 seconds to drain residual charge, then disconnect the Thunderbolt cable from both ends. Wait 60 seconds. Reconnect the enclosure power first, wait for its fans or lights to settle, then connect the cable to the laptop while the laptop is fully off. Boot the laptop.
How to undo it
Nothing to undo — this changes no settings. Just reconnect normally afterward.
Fix 2: Approve the Device in Thunderbolt Settings
What causes it
Thunderbolt security levels (Legacy mode, “User Authorization,” or “Secure Connect” depending on your laptop) block new PCIe devices until you explicitly approve them. If the approval prompt was missed or dismissed, the enclosure connects for display purposes but its PCIe tunnel — and therefore the GPU — never activates.
How to check
Click the Thunderbolt icon in the system tray (or search “Thunderbolt Control Center” in the Start menu). If your enclosure is listed but shows a status other than “Connected and approved,” or a prompt is waiting under “Pending devices,” authorization is the problem. You can also open Settings, go to Bluetooth & devices, then Thunderbolt devices (Windows 11 path) to see connection status.
What to do
In the Thunderbolt utility, select the enclosure and click “Approve” (check “Always connect” so it auto-approves in future). If no prompt appears, temporarily lower the security level: in the Thunderbolt utility or in BIOS, set the security mode to “No security” or “User Authorization,” reconnect, and confirm the GPU appears in Device Manager under Display adapters. You can raise the security level afterward once approval is remembered.
How to undo it
Return the Thunderbolt security level to its previous setting in the same utility or BIOS menu. Approved devices can be forgotten via “Manage Attached Devices” and the Forget Device option.
Fix 3: Update the Thunderbolt Controller Firmware and Driver
What causes it
Laptops use an Intel Thunderbolt controller (often an “Alpine Ridge” or “Maple Ridge” class chip) with its own firmware. Older firmware versions have known enumeration bugs with eGPU enclosures — the device connects at USB speeds instead of full PCIe, so the GPU never registers.
How to check
In Device Manager, expand “System devices” and find the Thunderbolt Controller entry. A warning icon here, or a driver dated more than a couple of years back, points to this cause. Intel’s Thunderbolt Software (if installed) has a Firmware Update tab that reports the current firmware version directly.
What to do
Get the Thunderbolt firmware and driver package from your laptop manufacturer’s support page for your exact model (search your model number plus “Thunderbolt firmware”). Install the driver first, reboot, then run the firmware updater — the updater typically requires the battery above a set level and no devices connected. Reboot again and reconnect the enclosure.
How to undo it
Firmware updates are permanent; drivers can be rolled back via Device Manager, right-clicking the Thunderbolt Controller, choosing Properties, then the Driver tab, and selecting “Roll Back Driver” if the option is available.
Fix 4: Clean Out Old GPU Drivers with DDU
What causes it
Leftover driver entries from a previous graphics card — or a botched GPU driver install — can prevent Windows from binding a clean driver to the newly detected eGPU, producing Code 43 or a device stuck in “Other devices.” Mixing NVIDIA and AMD driver stacks on the same system makes this worse.
How to check
In Device Manager, look for the GPU under “Other devices” or with a yellow triangle. Double-click it and read the “Device status” box: “Windows has stopped this device because it has reported problems (Code 43)” is the classic symptom.
What to do
Download the current driver package for your eGPU’s chipset (NVIDIA GeForce or AMD Adrenalin) first, so you have it offline. Disconnect the enclosure. Download Display Driver Uninstaller (DDU), boot into Safe Mode (hold Shift and click Restart, then Troubleshoot, Advanced options, Startup Settings, Restart, then press 4), run DDU, and choose “Clean and restart” for the GPU vendor in question. When Windows reloads, reconnect the enclosure, wait about 30 seconds for enumeration, then install the driver you downloaded. Reboot once more.
How to undo it
Reinstalling any driver version through the standard installer reverses the change. Windows Update will also re-offer OEM drivers if you prefer them.
Fix 5: Correct BIOS Settings for eGPU Support
What causes it
Several BIOS options gate whether a Thunderbolt-attached GPU gets PCIe resources at boot: “Above 4G Decoding” must be enabled for modern GPUs to map their BARs, “Thunderbolt Boot Support” should be set to “Pre-boot” or “Enabled,” and on hybrid-graphics laptops, a “Discrete GPU mode” or “eGPU first” option may be required for the enclosure’s card to take priority.
How to check
Restart and enter BIOS (commonly F2, Del, or F10 — check your laptop’s boot splash). Look under Advanced, PCI Configuration, or Thunderbolt Configuration menus. If “Above 4G Decoding” is disabled, or Thunderbolt Boot Support is set to “Disabled,” that matches this cause.
What to do
Enable “Above 4G Decoding.” Set “Thunderbolt Boot Support” to “Pre-boot” (or “Enabled” if Pre-boot is absent). If your BIOS offers “Resizable BAR” alongside Above 4G Decoding, leave it enabled unless the GPU still fails to detect, in which case toggle it off as a test. Save with F10 and reboot with the enclosure connected.
How to undo it
Return each setting to its prior value in the same BIOS menus, or use “Restore Defaults” (usually F9) to reset everything.
Fix 6: Resolve Code 12 Resource Conflicts
What causes it
The laptop’s PCIe bus runs out of addressable resources when the eGPU is added on top of the internal GPU, storage controllers, and Thunderbolt bridges. Windows reports “Code 12 — This device cannot find enough free resources.” Enabling Above 4G Decoding (Fix 5) resolves most cases; on systems without that option, disabling other devices frees resources.
How to check
Open Device Manager, double-click the eGPU (or the unknown device), and read the error code in the Device status box. Code 12 confirms this cause.
What to do
If your BIOS lacks Above 4G Decoding, disable the laptop’s internal discrete GPU temporarily: in Device Manager, right-click the internal dGPU under Display adapters and choose “Disable device,” then reconnect the eGPU and scan for hardware changes (Action menu, “Scan for hardware changes”). Alternatively, disable unused devices such as the built-in card reader or unused NVMe slots in Device Manager or BIOS to free PCIe resources. Connect the enclosure to the port wired directly to the CPU (usually the left-side USB-C port on many laptops) rather than one routed through the chipset.
How to undo it
Re-enable any disabled devices in Device Manager by right-clicking and choosing “Enable device.”
Fix 7: Test with a Different Cable, Port, and Machine
What causes it
Thunderbolt cables are rated for either 20 or 40 Gbps PCIe tunneling, and passive 20 Gbps cables will not carry a GPU. Ports can degrade, and some laptop models only wire one of their USB-C ports to the discrete graphics path needed for full eGPU performance.
How to check
Look at the cable’s connector or packaging for a Thunderbolt logo (a lightning bolt) and, ideally, a “40” marking. In the Thunderbolt utility, a connection running at USB speeds instead of PCIe indicates a cable or port limitation. If your enclosure connects but the GPU still never enumerates after all earlier fixes, hardware is suspect.
What to do
Borrow or purchase a certified Thunderbolt 3 or 4 cable rated at 40 Gbps (0.8 m passive cables are the safest choice). Try every Thunderbolt-capable port on the laptop, consulting your manual for which port supports PCIe tunneling. If possible, test the enclosure plus GPU on a second Thunderbolt laptop, and test the GPU itself in a desktop, to isolate whether the fault is the GPU, enclosure, or laptop.
How to undo it
Nothing to undo — reconnect your original configuration afterward if the test changes nothing.
If Nothing Works
If the GPU remains undetected after a clean driver install, updated Thunderbolt firmware, corrected BIOS settings, and cable swaps, you are most likely looking at a hardware fault. Contact the enclosure manufacturer’s support first — enclosure mainboards fail more often than GPUs. If the enclosure checks out on another machine, pursue a warranty claim on the GPU; if the GPU checks out in a desktop, the laptop’s Thunderbolt controller or motherboard is at fault and needs service. Before sending anything in, run the enclosure vendor’s diagnostic utility if one exists (many include one in their software suite), and note exactly which error code Device Manager displays, since support teams will ask for it. As a stopgap, Windows 11’s “Cast to device” and streaming options, or a cloud gaming subscription, can at least keep you gaming on an external display while hardware is in transit.
FAQ
Why does my eGPU work at first and then disconnect during games?
Intermittent disconnects under load usually mean thermal or power problems: the enclosure’s power supply is under-spec for the GPU’s transient spikes, or the Thunderbolt cable is loose or unrated for 40 Gbps. Reseat the GPU’s auxiliary power connectors inside the enclosure, verify the PSU wattage meets the GPU’s requirement, and try a shorter, certified cable. Updating the Thunderbolt firmware (Fix 3) also addresses several known disconnect bugs.
Can I use an eGPU with my laptop’s internal display, or must I connect a monitor?
You can use the internal display, but frames must travel back over the Thunderbolt cable, which costs significant performance. For the best results, plug a monitor directly into the eGPU’s video outputs. If the GPU is detected but performs poorly on the internal screen, check Settings, then System, then Display, then Graphics, and set your games to “High performance” on the eGPU.
Does my laptop need Thunderbolt for an eGPU, or does USB4 work?
USB4 supports PCIe tunneling, so many USB4 ports work with eGPU enclosures, but implementation varies: some early USB4 implementations disabled PCIe tunneling by default. Check your laptop’s specification page for the phrase “PCIe tunneling over USB4” or an explicit eGPU support statement. A plain USB-C port with only DisplayPort Alt Mode will not run an eGPU at all.
Should I disable my laptop’s internal GPU permanently once the eGPU works?
No. Leave the internal GPU enabled so you retain display output on battery and a fallback if the eGPU disconnects. If you disabled it while troubleshooting Code 12 (Fix 6), re-enable it via Device Manager and confirm the eGPU still works — with Above 4G Decoding enabled in BIOS, both GPUs can usually coexist without resource conflicts.
