Fix ERROR_UNABLE_TO_INVENTORY_TRANSPORT (0X000010E7)

Cause 1: Corrupted Bluetooth driver stack (most common)

On Windows 10 build 1909 and later, the Bluetooth stack can get tangled up after a bad driver update or a Windows Update that partially fails. I see this error most often right after pairing a new Bluetooth device — the system tries to inventory the transport (i.e., check the status of the Bluetooth radio) and gets back nothing useful, so it throws 0X000010E7.

The fix is to completely nuke the Bluetooth driver and let Windows reinstall it fresh.

1. Press Windows Key + X and select Device Manager.
2. Expand the Bluetooth section. You'll see something like "Intel(R) Wireless Bluetooth(R)" or "Realtek Bluetooth Adapter".
3. Right-click each Bluetooth device listed (there might be one or two) and select Uninstall device.
4. In the confirmation dialog, check the box that says "Delete the driver software for this device". This is critical — if you skip this, the old corrupted driver stays on disk and will be used again.
5. Click Uninstall. Repeat for every Bluetooth entry.
6. After you've removed them all, restart your computer. Don't skip the restart.
7. Once Windows comes back up, it should auto-detect the missing Bluetooth hardware and install a fresh driver from its cache or via Windows Update. You'll see the Bluetooth icon reappear in the system tray.
8. Check if the error is gone by trying to use Bluetooth or run msdt.exe -id DeviceDiagnostic in an admin command prompt.

If the error persists after the restart, you can also manually scan for hardware changes in Device Manager by clicking the Action menu and selecting Scan for hardware changes.

Cause 2: Corrupted network transport driver stack

Less common but happens: the TCP/IP stack or the underlying network transport drivers (like WFP, NetIO, or the NDIS layer) get corrupted. This shows up as 0X000010E7 when the system tries to inventory network transports — maybe after a VPN install or an aggressive firewall change. You'll see this error in Event Viewer under System logs with source "Tcpip" or "NetIO".

The real fix here is a network stack reset. Skip all the third-party "network optimizer" tools — they're junk. Do this instead:

1. Open a command prompt as Administrator (right-click Start, choose "Windows Terminal (Admin)" or "Command Prompt (Admin)").
2. Run these commands one at a time, pressing Enter after each. They reset the Winsock catalog, the TCP/IP stack, and flush the DNS cache:
   

   netsh winsock reset
   netsh int ip reset
   ipconfig /release
   ipconfig /renew
   ipconfig /flushdns

3. After the last command, restart your computer.
4. Check if the error reappears by running sfc /scannow in an admin command prompt to verify system file integrity. If sfc finds corrupted files, run DISM /Online /Cleanup-Image /RestoreHealth and restart again.

I've seen this fix work on machines where Bluetooth drivers were fine but the network transport layer itself was broken — for example, after a failed Cisco VPN client uninstall.

Cause 3: Third-party filter driver conflict (security software or VPN clients)

This one's sneaky. Some security suites (like Symantec Endpoint Protection, McAfee, or older versions of Malwarebytes) install kernel-mode filter drivers that intercept transport inventory calls. When those drivers are buggy or conflict with Windows updates, you get 0X000010E7. Same goes for certain VPN clients — especially those that use TAP-Windows adapters (like OpenVPN or older Cisco AnyConnect).

The fix is to temporarily uninstall the offending software, not just disable it.

1. Open Settings > Apps > Apps & features.
2. Find your security software or VPN client in the list.
3. Select it and click Uninstall. Follow the prompts to fully remove it. Some antivirus tools require a reboot during uninstall — let them do it.
4. After the uninstall is complete and the machine is back up, check if the error is gone by trying the same action that triggered it before.
5. If the error is gone, you have two choices: update the software to the latest version (check the vendor's site directly, not through Windows Update) or keep it uninstalled and use Windows Defender instead. Windows Defender has been rock solid since Windows 10 version 2004 and won't cause this error.

I've personally had to fix three workstations at a client site where McAfee's filter driver caused 0X000010E7 after the Windows 10 21H2 feature update. Uninstalling McAfee and switching to Defender resolved it permanently.

Quick-reference summary table