Share via

Windows keeps waking my external NA USB drive

WHYAHWHYA 0 Reputation points
2026-05-15T15:29:01.0066667+00:00

Hi all,

I’m trying to troubleshoot an external drive that keeps waking from sleep.

Setup:

  • Drive: 3.5" WD Red NAS drive
  • Enclosure: Sabrent 3.5" USB enclosure with dedicated power supply
  • OS: Windows 11 PRO 25H2
  • OS Build: 26200.8457
  • Drive letter: E:
  • Usage: media storage
  • Shared over the network via SMB
  • Kodi on Android TV plays videos from this drive over the network

The drive spins down / goes to sleep, which I’m fine with. The issue is that something wakes it up every so often, and I’m trying to identify what is touching the drive.

At first, I thought it might be disconnecting/reconnecting, but Event Viewer mostly shows:

Ntfs (Microsoft-Windows-Ntfs)

This appears every 20–40 minutes. From what I understand, this event alone does not indicate a problem. It just means Windows accessed or checked the NTFS volume and found it healthy.

I used Process Monitor with a filter for:

Path begins with E:\

Process Monitor log still a short burst of access around the wake time. The processes involved were:

Explorer.EXE

The paths touched included:

E:\

I checked Windows Indexing Options. E: is not selected for indexing. The only selected locations are things like:

Start Menu

The csc://... entry looks like Offline Files / Client Side Cache, not the external drive.

So, I thought it might be

GoogleDriveFS.exe

So I went ahead and quit google drive

I also:

  • Removed E: folders from Quick Access
  • Disabled recent/frequent folders in File Explorer
  • Cleared File Explorer history
  • Made sure E: is not selected in Indexing Options
  • Checked that Kodi/SMB sharing still works

The Next Log showed that the drive is still being woken up by:

Explorer.EXE

My current suspicion is that Windows is periodically touching the volume for metadata/volume identity checks, possibly through SearchIndexer, Explorer, or normal volume management, and that wakes the enclosure/drive.

I’m trying to figure out:

  1. Is SearchIndexer.exe accessing E:\System Volume Information\IndexerVolumeGuid normal even when E: is not indexed?
  2. Could svchost.exe / WUDFHost.exe / Explorer touching E:\, E:\TV, or E:\autorun.inf be enough to wake a sleeping USB enclosure?
  3. Is there a safe way to stop Windows from polling this external media drive without breaking SMB sharing to Kodi?
  4. Should I temporarily stop Windows Search with:
Stop-Service WSearch

to confirm whether SearchIndexer is the cause?

  1. Are there other common Windows services that periodically touch external drives and wake them?

The drive itself seems healthy, and Event Viewer says the NTFS volume is healthy. I’m mainly trying to stop or identify the process that wakes the drive from sleep.

Any advice on what else to check in Process Monitor, Event Viewer, or Windows settings would be appreciated.

Windows for home | Windows 11 | Files, folders, and storage
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Craig Long 17,885 Reputation points
    2026-05-16T22:54:24.4666667+00:00

    I really like these cables with a switch. Just make sure you eject the drive before switching it off. To access the drive, just switch it on. I have a KVM switch and don't want certain devices to access certain external drives. The drives stay ejected until switched on.

    USB Cable with Switch

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-05-15T15:29:27.9766667+00:00

    Explorer, SearchIndexer, and other system components can wake external USB disks simply by reading basic metadata on the volume. Any read of the NTFS volume (root, System Volume Information, or autorun.inf) is enough to wake the enclosure.

    From the provided context, the following points are supported:

    1. USB devices and power management

    USB devices are power-managed via selective suspend. When a USB device is idle, Windows can suspend it; any subsequent I/O request (for example, a read of the root directory or a metadata file) wakes the device back to D0 (fully powered) and resets the idle timer. This is normal behavior.

    The USB power model described for WinUSB devices shows that:

    • Any write or control transfer forces the device into D0 and resets the idle timer.
    • Read requests wake the device when they are submitted.

    That same pattern applies conceptually to storage devices behind USB: any access from Explorer, SearchIndexer, or a service will wake the disk.

    “All writes and control transfers force the device into the D0 power state and reset the idle timer. … Read requests wake the device when they're submitted.”

    So:

    • Yes, a simple metadata probe of E:\, E:\TV, or E:\autorun.inf by Explorer, SearchIndexer, or a service is enough to wake the USB enclosure.
    1. System energy diagnostics

    Windows provides powercfg /energy to detect energy-efficiency problems, including:

    • Ineffective use of selective suspend by USB devices
    • Excessive processor utilization
    • Increased timer resolution
    • Inefficient power policy settings

    Running this from an elevated command prompt:

    powercfg /energy

    produces an HTML report that can highlight USB devices that are not suspending efficiently or are being kept active. While it does not directly list “who touched E:\”, it can confirm whether the USB storage path is a persistent power offender.

    1. USB devices blocking deeper sleep

    Modern Standby diagnostics show that if a USB host controller stays active (for example, because a USB device does not enter selective suspend), it prevents the SoC from reaching deep low-power states. The recommended workflow in that scenario is:

    • Use a power report (SleepStudy or powercfg) to identify that USB is a top offender.
    • Then use ETW tracing to identify which USB device is staying in D0.

    Applied to this case, that means:

    • If the external enclosure or its driver does not fully support selective suspend, or is constantly woken by periodic I/O, the USB controller will stay active and the disk will keep spinning up.
    1. Specific answers to the numbered questions
    1. SearchIndexer.exe and IndexerVolumeGuid

    The context does not explicitly document IndexerVolumeGuid behavior, but it does state that powercfg /energy detects “ineffective use of selective suspend by USB devices” and “inefficient power policy settings.” That implies that background services (including indexing) can affect device power states.

    Within the given context, the only supported statement is:

    • Any access that causes I/O to the USB device will wake it from selective suspend.
    1. Can Explorer / svchost / WUDFHost touching E: wake the drive?

    Yes. The USB power-management description confirms that any I/O (read/write/control) wakes the device to D0 and resets the idle timer. Access to the root of the drive or to metadata files is sufficient.

    1. Safe way to stop polling without breaking SMB

    The context does not provide a supported method to selectively stop Windows from polling a specific external drive while keeping SMB sharing intact. It only describes:

    • How selective suspend works.
    • How to diagnose energy issues with powercfg /energy.

    No documented setting in the provided material disables all background volume touches for a single drive without side effects.

    1. Temporarily stopping Windows Search

    The context does not mention Stop-Service WSearch or stopping Windows Search as a diagnostic step, so no additional guidance can be given beyond noting that:

    • powercfg /energy is the documented tool to identify energy-efficiency problems, including USB selective-suspend issues.
    1. Other common services

    From the context, the main relevant components are:

    • USB selective suspend and its interaction with drivers and devices.
    • General system energy issues detected by powercfg /energy.

    The context does not enumerate specific Windows services (beyond USB and power-related components) that periodically touch external drives.

    Within the available documentation, the most concrete, supported next step is:

    1. Run an elevated command prompt.
    2. Execute: 
         powercfg /energy
    3. Review the generated HTML report for:
      • USB devices that are not entering selective suspend.
      • Inefficient power policy settings related to USB or storage.

    If the report flags the external USB storage or its controller as an energy offender, that confirms that background I/O and/or poor selective-suspend support is keeping the device awake or waking it frequently.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    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.