The simultaneous "inability to mount a file in Windows Explorer" and "inability to access cdrom resources" is highly likely tied to security software or setting which restricts cdrom access. This can be verified if you are able to load the image in powershell with: Mount-DiskImage -ImagePath "c:\sims.iso"
Gives a result like this:
Attached : True
BlockSize : 0
DevicePath : \.\CDROM0
FileSize : 3550216192
ImagePath : c:\sims.iso
LogicalSectorSize : 2048
Number : 0
Size : 3550216192
StorageType : 1
PSComputerName :
This means the iso was mounted. You will see an extra drive under you devices but will be unable to access this resource because some setting is blocking cdrom access.
Also please check the following key with Registry Editor:
| Registry Hive | HKEY_LOCAL_MACHINE |
|---|---|
| Registry Path | Software\Policies\Microsoft\Windows\DeviceInstall\Restrictions |
| Value Name | DenyDeviceIDs |
| Value Type | REG_DWORD |
| Enabled Value | 1 |
| Disabled Value | 0 |
Make sure it is disable.
If you were unable to mount the file either the iso is corrupt or you have corrupted your Windows installation.
Virtual Drive makers of any and all kinds will also run into the same problem; ability to mount ok, ability to read mounted contents denied. The more intelligent ones will report a mount failure error simply because the contents cannot be read thus cannot be verified.
Windows Overlord
Applies to All Editions of Windows (11 - 2000)
Superseding Microsoft Tech support by a Mile.