Freedom251 › Virtual Drive Software
Mount-DiskImage

What Mount-DiskImage is
Mount-DiskImage is a free Windows PowerShell cmdlet for making an existing VHD or ISO available as a disk. To use it, provide the image file’s full path. The StorageType parameter can identify an ISO, VHD, VHDX, or VHDSet; if you omit the type or choose Unknown, the cmdlet determines it from the file extension.
VHDs can be mounted for read-only or read-write access, but ISO images are read-only regardless of the selected parameter. Mounting a VHD requires administrator privileges. ISO privilege requirements differ by Windows version: Windows 8 does not require administrator privileges for ISO mounting, while Windows Server 2012 permits only administrators to mount or eject an ISO. NoDriveLetter lets you mount an image without assigning a drive letter.
By default, the command runs in the local computer session. CimSession can direct it to a remote computer, and AsJob can run long operations in the background. The cmdlet produces no output unless you use PassThru, which returns an object representing the mounted image. For VHD work on Hyper-V, the available guidance points to New-VHD and Mount-VHD or Disk Management. In failover clusters, Storage cmdlets operate across the cluster’s servers.
Who it suits
Mount-DiskImage suits Windows users who need to make existing VHD or ISO files available as disks, including administrators working with remote sessions or failover clusters. It is also relevant when a command needs to run in the background or avoid assigning a drive letter.
What it does well
- Free PowerShell cmdlet for mounting VHD and ISO images.
- Supports ISO, VHD, VHDX, and VHDSet formats.
- VHDs can be mounted read-only or read-write.
- Can run commands remotely through CimSession.
- AsJob runs long operations in the background.
What to know first
- VHD mounting requires administrator privileges.
- ISO images are mounted read-only.
- The cmdlet requires the full image-file path.
Limits
ISO images are read-only, and mounting a VHD requires administrator privileges. ISO mounting does not require administrator privileges on Windows 8, but Windows Server 2012 allows only administrators to mount or eject an ISO.
Getting started
- Open the Windows PowerShell environment.
- Provide the full path to the VHD or ISO file.
- Optionally specify ISO, VHD, VHDX, or VHDSet as the storage type.
- Choose read-only or read-write access for a VHD; ISO files remain read-only.
- Optionally use NoDriveLetter, CimSession, AsJob, or PassThru as needed.
Verdict
Choose Mount-DiskImage if you need a free Windows command-line option for mounting an existing VHD or ISO, with control over access mode and drive-letter assignment. For creating or mounting VHDs on Hyper-V, the guidance points to New-VHD and Mount-VHD or Disk Management instead.
Questions
What does Mount-DiskImage do?
It mounts an existing VHD or ISO so it appears as a normal disk.
Which image types does it support?
The StorageType parameter accepts ISO, VHD, VHDX, VHDSet, or Unknown. When omitted or set to Unknown, the type is determined from the file extension.
Can a mounted image be writable?
VHD files can be mounted read-only or read-write. ISO files are always mounted read-only.
Does mounting require administrator privileges?
Mounting a VHD requires administrator privileges. ISO mounting does not require them on Windows 8; Windows Server 2012 permits only administrators to mount or eject an ISO.
Can it run against a remote computer?
Yes. CimSession directs the command to a remote session or computer; otherwise, it uses the local computer session.
Facts from Mount-DiskImage's own pages
- Access modes
- VHD files can be mounted read-only or read-write, while ISO files are mounted read-only regardless of the parameter value. · learn.microsoft.com, 4 Oct 2026
- Background jobs
- The AsJob parameter runs the cmdlet as a background job for commands that take a long time to complete. · learn.microsoft.com, 4 Oct 2026
- Cluster behavior
- When Storage module cmdlets are used in a failover cluster, they operate at cluster level across all servers in the cluster. · learn.microsoft.com, 4 Oct 2026
- Drive letter
- The NoDriveLetter parameter specifies that no drive letter should be assigned after mounting. · learn.microsoft.com, 4 Oct 2026
- Hyper-V guidance
- For creating and mounting a VHD on a computer running Hyper-V, the page points to New-VHD and Mount-VHD in the Hyper-V module, or to Disk Management. · learn.microsoft.com, 4 Oct 2026
- Output
- The cmdlet produces no output by default; with PassThru it returns an object representing the mounted disk image. · learn.microsoft.com, 4 Oct 2026
- Path requirement
- The cmdlet requires the full path of the VHD or ISO file. · learn.microsoft.com, 4 Oct 2026
- Privileges
- Mounting a VHD requires administrator privileges; the page says ISO mounting does not require them on Windows 8, while Windows Server 2012 permits only an administrator to mount or eject an ISO. · learn.microsoft.com, 4 Oct 2026
- Purpose
- Mount-DiskImage mounts a previously created virtual hard disk or ISO so it appears as a normal disk. · learn.microsoft.com, 4 Oct 2026
- Remote execution
- The CimSession parameter runs the cmdlet in a remote session or on a remote computer; by default it uses the local computer session. · learn.microsoft.com, 4 Oct 2026
- Supported image types
- The StorageType parameter accepts ISO, VHD, VHDX, VHDSet, or Unknown; when omitted or set to Unknown, the type is determined from the file extension. · learn.microsoft.com, 4 Oct 2026
- Windows support
- The MSFT_DiskImage Mount method lists Windows 8 desktop apps as its minimum supported client and Windows Server 2012 desktop apps as its minimum supported server. · learn.microsoft.com, 4 Oct 2026
Where Mount-DiskImage stands on Freedom251
- Virtual Drive Software#23 of 24