Detection layer
Absent in BIOS/firmware, Device Manager, Disk Management, or only the application.
Storage, USB, or add-in hardware is not detected
Use this flow after a new install, cable/port change, driver update, or BIOS change. The key split is firmware, Windows, or application visibility—and whether a disk contains existing data.
Protect the device and data: do not initialize or format an existing disk, open a powered system, change BIOS settings, or install random drivers before the detection layer is known.
What this flow is for
A storage drive, USB device, Bluetooth accessory, or PCIe card is missing after installation or a firmware/driver change. A device can be present in firmware but absent from Windows or only from one application.
First safe checks
- Record model, connection path, recent changes, and exact missing layer.
- Check firmware/BIOS, Disk Management, and Device Manager without changing state.
- For USB/Bluetooth, confirm power, pairing mode, known-good port/cable, and unknown-device status.
- Read the Device Manager problem code and use Scan for hardware changes only when safe.
- For a new empty disk only, confirm the intended initialization plan; existing data switches to preservation.
Best evidence
Capture this before changing hardware
Connection path
Device model, port/cable/slot, power, and known-good host comparison.
Recent change
Install, BIOS, driver, update, cable, power, or physical change with exact error.
Likely causes
Most likely problem buckets
Physical connection
Power, cable, port, seating, or enclosure prevents detection.
Firmware/resources
BIOS settings, lane/resource conflicts, or compatibility affect visibility.
Windows driver
Device Manager problem codes or incomplete enumeration block the device.
Disk state
The disk is offline, missing a letter, uninitialized, or contains data at risk.
Next safe steps
Take one step at a time
ACT-HW-020
Record the device, connection path, recent changes, and missing layer.
ACT-HW-021
Compare firmware, Disk Management, and Device Manager without initializing or formatting.
ACT-HW-022
Test one known-good port, cable, host, or supported driver/scan step.
ACT-HW-023
Hand off internal reseating, BIOS/firmware changes, or storage actions involving existing data.
Best follow-up ask
Is the device absent in BIOS/firmware, Device Manager, Disk Management, or only the application—and is the disk new or does it contain data?
When to stop and hand off
Escalate before physical reseating, BIOS/firmware/security changes, or disk initialization/formatting when existing data may be present.
Source provenance
Reviewed against Microsoft hardware guidance
This flow uses Microsoft guidance for Disk Management, Device Manager problem codes, hardware enumeration, and supported driver/scan steps. New empty disks and existing data-bearing disks are treated differently.
Map the device
Record the hardware, port, host, driver, and system-map relationship privately.
Open private discoveryContinue in support chat
The support assistant can identify the detection layer without collecting serials, keys, or private screenshots.
Open support chat