Confirmed
- Windows is presenting the storage connection as removable or hot-pluggable.
Device · reviewed 2026-09-01
Internal disk appears as removable in Windows
A disk can appear in the removable-device interface when the storage controller, firmware, port metadata, or driver reports that connection as hot-pluggable.
Moderate for the presentation mechanismRequires exact controller and firmware evidence
Try a scenario
Resume a saved session — paste a Resume Capsule
The capsule is validated and restored only in this browser. An invalid capsule changes nothing.
Meaning & limits
What this diagnostic record establishes
Not confirmed
- The icon alone does not prove the disk is external, failing, or safe to eject.
- It does not justify a registry override or storage-controller change without the exact hardware and firmware context.
Context changes the route
Which storage device is affected?
Choose the context that matches your incident. These are alternatives, not a sequence of fixes. Follow only the matching check and keep its verification and rollback together.
Windows system disk
Likely layer: Firmware or storage-controller port metadata
First safe check: Do not eject it—record the storage path first
Expected: You will have the exact controller and firmware context needed for the OEM path without risking the boot disk.
Steps, verification and rollback
- Confirm the affected disk is the Windows system disk and record its model in Disk Management or Device Manager.
- Record the storage controller name and PC or motherboard model.
Verify: Compare the same disk identity in Disk Management and Device Manager; do not test the Eject action.
Rollback: No system change is made by this check.
Internal data disk
Likely layer: Firmware or storage-controller port metadata
First safe check: Protect data and identify the port before changing presentation
Expected: The OEM can confirm whether the port is intentionally hot-pluggable or needs a firmware or supported-driver correction.
Steps, verification and rollback
- Back up important data and record the disk model, controller, and whether the firmware exposes hot-plug for that port.
- Do not apply a generic registry value copied for a different controller.
Verify: Confirm the disk remains stable across a normal restart and that the identity matches the intended internal disk.
Rollback: No system change is made by this check.
Before any second repair step
Verify the observation and preserve the evidence
After the first safe check, record whether the reviewed intermediate result occurred, whether the original problem was retested, and the exact output. An expected observation is not automatically a repair.
Outcome boundaries
- Observed as expected
- Observed something different
- Result unclear
- Could not complete the check
Then separately record whether the original problem still occurs, was not reproduced once, or has not been retested yet. Every session ends in stop, one repeat of the same check, one named missing fact, or escalation—never an open-ended repair sequence.
Evidence fields for this task
- Exact device nameAs shown in Device Manager
- Hardware IDsCopy the first one or two IDs, after reviewing them
- Driver provider/version/dateProvider · version · date
- Port/device comparisonWhat changed on another port, PC, cable, or reconnect
The browser-local Evidence Pack combines the selected context, safe action, actual observation, sources, review date, missing evidence, and stop boundary. It can be copied or printed without creating an account or uploading a log.
After you perform the safe check
Read the evidence you collected
Paste bounded driverquery or PnPUtil enumeration text and extract driver, package, provider, class, version, signer, state, path, and device-relation facts without recommending a download or naming a culprit.
Review trail
Official and first-party sources
- Error codes in Device Manager in Windows Microsoft Support · primary
- Driver signing and digital signatures Microsoft Learn · primary