ISO Won't Mount in Windows 10 or 11? Fix Missing Mount Option and Disc Image Errors

Prerequisites and Scope​

Before modifying system defaults or file attributes, confirm the following requirements:

• Supported Operating Systems: Windows 10 (all editions, version 22H2 and earlier supported builds) and Windows 11 (all editions, including versions 22H2, 23H2, 24H2, and later).
• Account Permissions: Standard user accounts can mount and eject .iso images in Windows 10 and Windows 11 client editions, and can change per-user default app associations. However, clearing NTFS sparse flags with fsutil, reconfiguring the Virtual Disk service (vds), or repairing optical drive class filters requires an Administrator account.
• File System and Storage Access: Ensure you have enough free space on a local internal drive (such as C:\) to hold a copy of the .iso image if it currently resides on a network share, USB flash reader, or cloud-synced folder.

Restore Windows Explorer as the Default App for ISO Files​

When third-party archive utilities (such as WinRAR, 7-Zip, or PeaZip) or optical disc emulators take over the .iso file extension, double-clicking the file opens an archive browser instead of attaching a virtual DVD drive, and the Mount verb disappears from the right-click menu. Restoring Windows Explorer (Windows.IsoFile) immediately returns the native Mount action.

Set the Default Handler via File Explorer (Windows 10 and Windows 11)​

The fastest way to restore the association on both operating systems is through the file's Properties dialog, which bypasses version-specific Settings menus:

1. Locate any .iso file on your PC, right-click it, and select Properties.
2. On the General tab, look at the Opens with: line. If it lists anything other than Windows Explorer, click the Change... button next to it.
3. Select Windows Explorer from the list of recommended programs.
4. Click OK (in Windows 10) or Set default (in Windows 11), then click Apply and OK to close the Properties window.

Set the Default Handler via Settings in Windows 11​

If you prefer using the Windows 11 Settings interface or if the right-click menu is customized:

1. Press Win + I to open Settings and select Apps > Default apps.
2. In the Enter a file type or link type search box near the top, type .iso.
3. Click the current default application shown for .iso in the results.
4. In the pop-up window, select Windows Explorer and click Set default.

Set the Default Handler via Settings in Windows 10​

1. Press Win + I to open Settings and navigate to Apps > Default apps.
2. Scroll to the bottom of the right pane and click Choose default apps by file type.
3. Scroll down the alphabetical list of extensions in the left column until you find .iso.
4. Click the application currently assigned next to .iso and select Windows Explorer from the pop-up menu.

Move the ISO to a Local Folder and Clear Blocking Attributes​

Even when Windows Explorer is the default handler, Windows will refuse to mount an .iso file if the storage stack cannot lock the file cleanly or if NTFS attributes mark the image as sparse or untrusted. Microsoft's storage troubleshooting documentation notes that sparse files and certain drive-letter layouts frequently trigger "Sorry, there was a problem mounting the file" or "You don't have permission to mount the file."

Follow these steps in order to prepare the file from a clean local path:

1. Move or copy the ISO to a simple local folder: If the .iso is stored on a UNC network path (\\server\share), an external SD/flash card reader, or an on-demand cloud folder (such as OneDrive with Files On-Demand enabled), copy the file to a short path on your primary local drive, such as C:\ISO\. As documented by Microsoft, copying the file to a new local folder or saving it under a new filename also often strips the sparse attribute automatically.
2. Unblock the downloaded file: Right-click the local .iso file and select Properties. On the General tab, look at the bottom for the message: "This file came from another computer and might be blocked to help protect this computer." If present, check the Unblock box, click Apply, and click OK.
3. Clear the Read-Only flag: While still on the General tab of the Properties window, look at the Attributes: row near the bottom. If Read-only is checked, uncheck it and click Apply and OK.
4. Inspect the NTFS attributes for the SparseFile flag: Press Win + X and select Terminal (Admin) or Windows PowerShell (Admin). Run the following command, replacing the sample path with the exact path to your .iso file:
   (Get-Item "C:\ISO\image.iso").Attributes
   Expected result: If the output lists SparseFile (for example, Archive, SparseFile), the Windows disk image mounter will fail to attach the file.
5. Remove the SparseFile flag: In the same elevated PowerShell or Command Prompt window, run fsutil to clear the sparse flag:
   fsutil sparse setflag "C:\ISO\image.iso" 0
   Verify that the flag is gone by querying it:
   fsutil sparse queryflag "C:\ISO\image.iso"
   Expected result: The utility should output This file is NOT set as sparse.

Check the Virtual Disk Service (vds)​

Windows relies on the Virtual Disk service (vds.exe, running under the LocalSystem account) to manage virtual volumes, assign drive letters, and coordinate with the Windows Storage Management API when attaching .iso and .vhd files. By default in both Windows 10 and Windows 11, Virtual Disk is set to Manual (Demand Start), meaning Windows starts it automatically whenever you mount an image. If a third-party tweaking tool or policy has set the service to Disabled, or if its dependency (Remote Procedure Call) is unhealthy, mounting will fail.

Warning: Modifying core Windows storage services affects Disk Management (diskmgmt.msc), diskpart, and virtual drive mounting. Do not disable the Virtual Disk service or change the logon account away from LocalSystem.

Click to expand...

1. Press Win + R, type services.msc, and press Enter to open the Services console.
2. Scroll down the alphabetical list and double-click Virtual Disk.
3. Check the Startup type drop-down menu. If it is set to Disabled, change it to Manual.
4. Click Apply, then click the Start button under Service status to verify that the service can launch without errors.
5. Click OK to close the properties window.

If you prefer to reset and start the service from an elevated Command Prompt or PowerShell window, run:

sc config vds start= demand
net start vds

Rollback: Because Manual (demand) is the factory default startup state for vds across all versions of Windows 10 and Windows 11, no rollback is needed once the service is returned to Manual.

Verify That the ISO Mounts and Check Its Drive Letter​

Once the file association, local path, file attributes, and Virtual Disk service are verified, test the mount operation:

1. Open File Explorer (Win + E) and navigate to your local folder (for example, C:\ISO\).
2. Right-click the .iso file and click Mount (in Windows 11, if a third-party menu handler crowds the top-level menu, click Show more options > Mount, or click Mount on the top command bar).
3. Open This PC in the left navigation pane of File Explorer. Under Devices and drives, confirm that a new virtual DVD Drive appears with an assigned drive letter and displays the internal contents of the disc image when opened.

Important Microsoft-documented quirk: In some drive-letter configurations, Windows may display a pop-up error stating "Couldn't Mount File: You don't have permission to mount the file" even though the .iso mounted normally in the background. Always check This PC or query the image state in PowerShell before assuming the mount failed:

Get-DiskImage -ImagePath "C:\ISO\image.iso" | Get-Volume

If Get-DiskImage shows Attached : True and Get-Volume returns a DriveLetter, the image is mounted and ready to use.

Alternate Method: Mount and Dismount via PowerShell​

If the File Explorer context menu is still unresponsive or if you want a direct diagnostic error code from the Windows Storage module, mount the image using PowerShell. In Windows 10 and Windows 11 client editions, mounting an .iso does not require administrator privileges (whereas Windows Server requires elevation by default).

1. Open Windows PowerShell or Terminal and run:
   Mount-DiskImage -ImagePath "C:\ISO\image.iso" -PassThru | Get-Volume
2. Expected result: PowerShell attaches the .iso in read-only mode and outputs the assigned DriveLetter, FileSystemLabel, FileSystem (typically UDF or CDFS), and Size.
3. When you are finished using the image, eject it either by right-clicking the virtual DVD drive in This PC and choosing Eject, or by running:
   Dismount-DiskImage -ImagePath "C:\ISO\image.iso"

Test Whether the ISO File Itself Is Damaged​

If both File Explorer and Mount-DiskImage fail with "The disc image file is corrupted" or HRESULT 0xc03a0005 ("The version does not support this version of the file format"), you must determine whether the .iso file itself was truncated or damaged during download.

1. Check the exact byte size: Right-click the .iso file and select Properties. Compare the Size value against the file size listed on the software vendor's download page. An interrupted browser download occasionally saves a partial file with an .iso extension that lacks a valid ISO 9660 or UDF volume descriptor.
2. Compute the SHA-256 cryptographic hash: Open PowerShell and run the built-in Get-FileHash cmdlet:
   Get-FileHash -Path "C:\ISO\image.iso" -Algorithm SHA256
   Wait for PowerShell to read the file and return the 64-character hexadecimal Hash string. Compare this string against the official SHA-256 checksum published by Microsoft or the vendor who supplied the ISO. If the hashes do not match, the file is genuinely corrupt and must be downloaded again.
3. Test with a second known-good ISO or archive reader: If no official hash is published, try mounting a different .iso file on the same PC. If another .iso mounts immediately, the first .iso is damaged. You can also test whether a free archive utility such as 7-Zip can inspect the internal file table of the .iso; if 7-Zip reports an unexpected end of archive or header error, the download is incomplete and cannot be repaired—re-download the image from the original source.

Troubleshooting Persistent Mounting Failures​

If your .iso passes the SHA-256 hash check, resides in a local folder with no SparseFile flag, and still fails to mount, match your symptom to the targeted fixes below.

Symptom: "You don't have permission to mount the file" When USB Drives or Card Readers Are Connected​

Microsoft documents a specific drive-letter ordering conflict when removable media (such as multi-slot flash media readers or external USB drives) occupy drive letters immediately ahead of the auto-assigned virtual DVD drive:

• Fix: Safely eject any connected USB flash drives or empty removable media card readers, or open Disk Management (diskmgmt.msc) and reassign your removable USB drive to a higher drive letter (such as F: or G:) so that the lower drive letter immediately following your local partitions (such as E:) is free for Windows to auto-assign to the mounted .iso.
• Unmount stale virtual drives: If you already have multiple .iso or .vhd images attached, eject them in This PC before mounting the new image.

Symptom: Mounting Fails Across All ISO Files After Uninstalling 3rd-Party CD/DVD Software​

As documented by Windows administration reference Windows OS Hub, uninstalling legacy optical drive burning or virtual CD emulation utilities can leave orphaned UpperFilters or LowerFilters driver entries in the Windows CD/DVD device class registry key, preventing both physical and virtual optical drives from initializing.

Warning: Editing the Windows Registry incorrectly can disable physical and virtual optical drives. Back up the registry key before deleting any values, and do not delete UpperFilters.bak or LowerFilters.bak if present.

Click to expand...

1. Press Win + R, type regedit, and press Enter to open Registry Editor.
2. Navigate to the following key:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318}
3. Create a rollback backup: Right-click the {4D36E965-E325-11CE-BFC1-08002BE10318} key in the left pane, select Export, and save it as cdrom-class-backup.reg on your Desktop.
4. In the right pane, look for the values named UpperFilters and LowerFilters. If either value exists, right-click it and select Delete.
5. Close Registry Editor and restart your computer. Windows will rebuild the default optical drive class configuration upon reboot.
6. Rollback: If you need to restore the previous filter configuration, double-click cdrom-class-backup.reg, confirm the prompt, and restart your PC.

Symptom: PowerShell Reports Component Store or System File Corruption (Error: 17098)​

If Mount-DiskImage or Windows Explorer fails because the underlying Windows storage binaries (vds.exe, virtdisk.dll, or storage providers) are damaged:

1. Open Terminal (Admin) or Command Prompt (Admin).
2. Repair the Windows component store using Deployment Image Servicing and Management (DISM):
   DISM.exe /Online /Cleanup-image /Restorehealth
3. Once DISM reports that the restore operation completed successfully, run the System File Checker:
   sfc /scannow
4. Restart your computer when the scan finishes and mount the .iso file again from your local folder.