Share via

Windows disk auto mount not working

Prashant Vinod 0 Reputation points
2026-05-23T21:22:05.02+00:00

I am experiencing consistent issues with USB flash drives failing to mount in Windows 11 after transitioning from a dual-booted Ubuntu environment. Despite the drives being physically functional (verified via Partition Wizard), they frequently fail to appear in File Explorer or trigger "Access is denied" errors in diskpart.

​Technical Details:

​System Configuration: Dual-boot system (Windows 11 and Ubuntu 26.04).

​Symptoms: 1. USB drives show up as "Unallocated" space in Disk Management despite containing data or previously being recognized.

  1. diskpart returns "Access is denied" even after clearing readonly attributes.
  2. File Explorer displays "Ghost" drive letters (e.g., phantom D: drive) that do not correspond to any active hardware in Disk Management or the Registry.

​Troubleshooting Performed:

​Verified hardware integrity using MiniTool Partition Wizard.

​Attempted to clear read-only attributes via diskpart.

​Cleaned registry MountedDevices keys to remove stale drive mappings.

​Confirmed the issue occurs specifically after a warm reboot from Ubuntu to Windows.

​Suspected Cause:

The Windows "Fast Startup" feature appears to be locking the USB mass storage controller during the handoff between the Ubuntu kernel and the Windows bootloader, leading to persistent registry-level mount failures.

​Requested Assistance:

I would like to know if there is a recommended configuration to prevent the Windows storage controller from entering a locked state during the dual-boot transition, or if there is a specific driver update that improves USB bus stability in this multi-OS environment.

Windows for home | Windows 11 | Devices and drivers
0 comments No comments

1 answer

Sort by: Most helpful
  1. Hendrix-V 15,775 Reputation points Microsoft External Staff Moderator
    2026-05-24T06:20:30.32+00:00

    Hi Prashant Vinod,

    This behavior usually occurs when Windows is unable to automatically assign a drive letter to newly detected volumes, often due to AutoMount being disabled or mount records needing to be refreshed.

    You can try the following steps:

    1, Verify AutoMount is enabled

    • Open Command Prompt as Administrator and run:
    diskpart
    automount
    
    • If it shows disabled, run:
    automount enable
    
    • Restart your PC

    2, Reset mount records (if issue persists)

    diskpart
    automount scrub
    automount enable
    

    3, Re-enable via MountVol

    mountvol /E
    

    4, Check Disk Management

    • Open Disk Management
    • Ensure the disk is:
      • Online
      • Initialized
      • Assigned a drive letter
    • If a drive letter is missing, manually assign one.

    Let me know if you need further assistance, feel free to ask me by clicking "Add Comment" or "Add Answer" if you cannot add comment so your response will be visible. Thanks for your effort.


    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.