Isolate an external USB device that changes or blocks Windows startup

Windows starts only when a USB device is removed, repeatedly starts Windows Setup, enters the wrong recovery environment, stalls before Windows, or changes behavior depending on which external device is connected.

Searchable Windows error codes and exact messages

There is no single Windows code for “USB device blocks boot.” A boot-order loop or firmware/POST stall commonly produces only screen text: Press any key to boot from USB, the Windows Setup language screen after every restart, No bootable device, Checking media presence, Start PXE over IPv4/IPv6, PXE-E61, or PXE-M0F.

Codes that can apply to specific USB-related branches are:

Device Manager codes are usable only after Windows starts with the suspect device disconnected or through another boot path. They do not explain a pre-Windows firmware freeze by themselves.

Use this procedure when the computer's startup behavior reliably changes after connecting or disconnecting USB storage, a dock, a hub, a card reader, an installation USB, or another peripheral.

Do not use it when the internal system drive disappears even with every external device removed, or when the computer cannot complete its normal firmware self-test.

The USB device model, Windows build, and reason the firmware reprioritized devices may remain unknown initially. The procedure identifies the triggering device by controlled reconnection.

• Ability to shut the computer down completely
• Access to firmware boot order if a USB storage device is involved
• A written list or photograph of the currently connected devices

Shut the computer down. Do not merely restart it. Disconnect USB storage, hubs, docks, card readers, printers, phones, cameras, controllers, and nonessential peripherals. Leave only power, one display, a basic keyboard, and a basic mouse.

1. Start the computer with the minimal device set.
2. Record whether Windows reaches the desktop.
3. Shut down again.
4. Reconnect one device directly to the computer—do not reconnect the entire hub yet.
5. Start Windows and record the result.
6. Repeat the shutdown, single-device connection, and startup cycle until the failure returns.
7. Repeat once with the suspected device removed to confirm that the result follows that device.

If an installation or recovery USB starts repeatedly

1. Remove the USB after Windows Setup completes its first file-copy phase and the computer begins its first restart, unless setup explicitly instructs otherwise.
2. Enter firmware boot order.
3. Place the verified internal Windows Boot Manager ahead of generic USB storage for normal startup.
4. Use the one-time boot menu when the USB intentionally needs to start; do not leave it permanently ahead of Windows unless required.

If an external hard drive, SSD, or card reader takes boot priority

1. Leave the device disconnected and boot Windows.
2. Correct the permanent boot order so Windows Boot Manager is first.
3. Shut down, reconnect the external storage, and test again.
4. If firmware still chooses it, check that device for an old EFI partition or bootable image. Do not delete anything from it until its contents and purpose are known.

If a non-storage peripheral blocks startup

1. Test the device without a hub, using another USB port.
2. Test the hub with no downstream devices.
3. If the hub alone works, add its devices one at a time.
4. Once Windows starts without the problematic device, install the current manufacturer driver or firmware only if the exact model is known.
5. Reconnect and retest.
6. If the problem follows the device across ports and another computer, replace or discontinue that device.

If Windows starts only while a particular USB is connected

1. Do not treat the USB as the repair.

2. In firmware, verify whether the USB is supplying boot files for the internal Windows installation.

3. With the USB connected and Windows running, enumerate firmware and BCD entries:

   bcdedit /enum all /v
   bcdedit /enum firmware /v
   

4. If the internal Windows volume relies on an EFI partition located on the removable device, use FIX-003 to restore boot files and a Windows Boot Manager entry on the intended internal system disk.

• Windows starts with all nonessential USB devices removed: Reconnection testing should identify the trigger.
• The failure follows one device across ports: The device, its firmware, or its boot metadata is implicated.
• The failure follows one USB port with multiple devices: The port, internal header, power path, or controller may be implicated.
• Windows Setup repeats after each reboot: Boot order or leaving installation media selected is the likely cause.
• Windows requires the USB to remain connected: Boot files may reside on the USB; repair the internal boot path before removing it permanently.

• Do not delete partitions from an external drive solely because it appears in the boot menu.
• Do not reconnect all devices at once after a successful minimal boot.
• Do not update unrelated drivers.
• Do not assume the last connected device is responsible until removal reproduces the recovery.

Restore the original firmware boot order from the recorded values if a change makes startup worse. Reconnect required peripherals only after the internal Windows boot path has been confirmed.

• Windows starts twice with the known-good device set.
• The isolated problematic device reproduces the failure at least twice or fails independent testing.
• Internal Windows Boot Manager remains first for normal startup.
• Installation media no longer restarts Setup unintentionally.

Confidence is approximately 90% when startup behavior repeatedly follows one device or boot-order change. Stop if the internal system drive becomes intermittent, a USB device contains the only copy of needed data, or the computer fails before firmware can enumerate devices.