Windows 10: Can't mount ISO as drive K:, but drive V: works fine

Hello everyone

A bit of background: I use Office 2003 alongside Office 2016. Office 2003 is installed from an ISO file created from the original Office 2003 CD. Every now and then, however, something on the computer causes Office 2003 to "break", and I suspect it may be Windows or Office 2016 updates that do that. Anyway, the solution has always been simple: whenever Office 2003 tells me that it needs to "repair" itself, it would look for the installation files in drive V:, and so mounting the ISO in drive V: would cause Word to repair itself. However, after my most recent reinstall of Windows 10, Office 2003 is looking for the installation files in drive K:, not drive V:. And you can't change which drive the installer looks in.

So, at this time, when I want Office 2003 to repair itself, I mount the ISO file as drive K:, but: when I do that, drive K: does not work. After mounting it, it shows up as a "CD Drive" in This PC, and I can't browse it, nor can I unmount it (the only way to unmount it is to reboot). Mounting the same ISO as drive V: works fine: I can browse it and I can unmount it. For mounting ISO files, I usually use wincdemu, but I've also tried Windows' built-in mounting facility -- same result.

What do I need to do so allow me to mount an ISO file as the K: drive in such a way that I can browse the drive and also unmount it, i.e. so that the Office 2003 installer recognises it as a "CD" with the installation files?

(Or: do you perhaps know how to tell Office 2003 to look for the installation files in drive V: instead of drive K:?)

Thanks
Samuel

Added: If I switch to the Administrator user, the ISO mounted as drive K: works fine, and I can let Office 2003 repair itself while logged in as Administrator, so at least there is a workaround to my problem.

:)

 

Mounting .iso from a network drive

Hi everyone,

I'm trying to mount an ISO-file from a network drive using powershell, but it doesn't mount properly from the network drive. It does however mount properly from a local disk. Now I'm not very experienced with powershell, but I am comfortable with batch files,
which is why I might use some unorthodox techniques to do what I want to achieve.

The situation:

I have an .ISO of a CD with a program on it. The program needs to run from the disc, due to a check that is built into the software. I know windows 10 has a mounting tool built-in, which works for my issue. I've already searched online on how to do this
using powershell and have made/copied a working script that does this. However, when I try to run the script with the .ISO being on a shared network drive, it doesn't work. When the .ISO is saved to a local disk, it does work.

My script:

I use the DriveLetter.txt file to build a batch file which starts the program.

I have tested the script both in normal powershell, as well as in an elevated powershell. I do see a virtual drive come up what I try to mount the iso from the network drive, but I can't access it in any way. The only way to get rid of it, is to run the
Dismount-ImagePath command. Running it from a local disk works both in normal and elevated powershell and allows me to access the iso normally. If I mount the iso manually from the network drive, I get a virtual drive with an iso mounted on it that I can access
normally.

My question:

What is going wrong and how can I fix this/where can I find documention/a solution?

I have a work-around for the issue, but I would like to have a solution where I don't need to save the iso locally. I've tried to create as clear of an image of my situation as possible, but if I need to provide more information, let me know. My google-fu
is quite strong, but I have not yet found a solution/similar question I can get info from.

Thank you very much in advance!

 

Strange Error mounting an iso on an external drive in Hyper-V


I got this rather odd error message when trying to mount an iso from an external drive using Hyper-V.

The external drive is formatted as NTFS, so the second part does not apply.

The iso does mount if I copy it to an "internal" drive in Hyper-V (C drive in my case).

It also mounts from external drive using a 3rd party tool (virtual clonedrive).

Not a big deal as easy enough to get round but I am curios to now if this is a bug, or if it is the way an external drive is interfaced somehow?

 

Error mounting .ISO files in Windows 10

Hi,

There are several reasons why you are having issues mounting ISO files on your Windows 10 Home computer. To assist you better, kindly answer the questions below:

• What other troubleshooting steps have you done so far?
• Have you tried mounting the ISO files on another computer?
• Have you tried copying the ISO file to your desktop and mount it from there?
• Do you have a CD/DVD drive installed on your computer?

Regards.