Windows 10: Cannot mount network drives - drive letters not available

Hi

I have a strange problem. I have some harddrives on a "server" computer in my homenetwork running win 7. From my "client" running windows 10 I am mounting these drives using

psexec \\server -u username -p password -d net share F=F:\ /GRANT:user,Full /GRANT:media,read 2>nul
net use F: \\server\F

Today my client crashed and I had to remove the graphics card. Since then I cannot enter my network drives anymore, the commands seem to run, but when I try accessing the drives I get a message indicating I should put a media into these drives. Also, I cannot mount them manually using "map network drive" since the drive letters are not available. I tried removing them from HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices (they are listed there as "\DosDevices\F" etc.), but once I restart, they are there (in the registry) again.

Any idea how I could fix this? Win10 somehow seems to remember that thes drives once have been there before and keeps blocking the drive letters...

:)

 

Mount ISO image that persists or mount at start-up

Using Windows 10 Home.

I want to have an ISO disk image mounted permanently and assigned to drive letter U - rather like mapping a network drive.

I know how to mount an ISO image in file explorer and assign it a drive letter in diskmgmt. But, when I re-start the computer, the mount does not persist and I have to do the mount/drive-letter assignment all over again.

I know there are 3rd party utilities which can do this, but how do I do it in Windows 10?

Is there a way of making the mount and drive-letter persist?

Or perhaps a command that can be executed at start-up to mount and assign a drive letter?

Or can it be done by kidding the "Map network drive" to map it somehow?

 

Mount ISO image that persists or mount at start-up

I think you may be misinterpreting my query - please read again.

I mounted the ISO file using file explorer - it allocated the drive letter E:. I then changed it to U: using diskmgmt. The reason is that I have a family history program that needs a CD to be available when I use it, and Ive told it that the CD is in drive
U:

This works fine until I re-boot, so I then have to repeat the process.

So, I need a way of either making the mount and drive letter persist after a restart (like network drives) or to mount and assign a drive letter at start-up.

 

Hi, dont know if this is relevant anymore, but in my case the H drive (which what was missing from the list of letters to choose from when mapping a new network drive) was actually used and just overlooked. Poweriso had shifted its drive lettering when I removed the previous mapping to H before adding new drives to a NAS device where H was pointing to.
Careful look at contents of "This PC" and there was H, a virtual CD Rom drive. Poweriso number of drives set to none, restart, H was in the list again ready for mapping.