Skip to content
littleden.blogEvidence-led Windows troubleshooting, without the guesswork
FixesError codesComponentsCommandsWindows updatesWindows 11
Research statusMethodology
Windows command reference

Get-Volume

List Windows volume objects, including drive letter, file system, health status and free/total size where available.

Risk: LowReviewed: 2026-09-17
Get-Volume

When to use it

Use to separate physical disk visibility from a mounted volume/file-system problem.

When not to use it

A healthy volume status does not rule out every physical-disk or controller problem; correlate with physical disk evidence when a drive disconnects or reports hardware warnings.

Primary reference

Reviewed source

Related authority records

Continue with the same failing system

These links share the same component or repair context; they are not generic keyword suggestions.

GuideFile-system errors in Windows 11: start with CHKDSK scan before repair switches

Use CHKDSK for a volume/file-system integrity problem—not as a generic slow-PC command—and distinguish a scan from /f or /r repair operations.

GuideDrive not showing in File Explorer: check Disk Management before formatting anything

Determine whether Windows sees the disk, whether a volume exists, and whether the problem is only a missing drive letter before destructive changes.

CommandGet-Disk

List disks visible to the Windows Storage subsystem so physical disk detection/status can be separated from File Explorer or drive-letter problems.

CommandGet-PhysicalDisk

List PhysicalDisk objects visible through Windows Storage providers, including operational and health status fields.

CommandGet-StorageReliabilityCounter

Read reliability counters exposed by supported disks/providers, including fields such as temperature, errors, wear and time in use.

CommandGet-WinEvent — storage timeout/retry events

Read recent storage reset, I/O retry and surprise-removal events to establish whether a storage-path problem is repeating and when it occurs.