MOUNTVOL "The parameter is incorrect."

[N3rdR4ge]

Running Windows 10 1703. I am trying to make a .bat to dismount and another .bat to remount. I cant get MOUNTVOL to mount and assign a drive letter.

MOUNTVOL F: /P
Works

MOUNTVOL F: \\?\Volume{229DC16C-D60F-11E6-BFB2-D05099530E5F}\
The parameter is incorrect.

Why am I getting this error? Is there another way I can mount in cmd based on uniqueid?

 

[Nigel Spike]

Try MOUNTVOL F: \\?\Volume\{229DC16C-D60F-11E6-BFB2-D05099530E5F}\

Nigel

 

[N3rdR4ge]

no luck :/

 

[Nigel Spike]

I have never used this command myself, so I checked some sites, and it seemed you were only missing that one backslash. I'm sorry it didn't work, and I can't help any further.

Nigel

 

[N3rdR4ge]

thanks for trying anyway!

 

[Colif]

I looked too, as far as I could tell you had the right command

https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/mountvol#BKMK_examples

I can't find anything specific to creators edition which might have been where it stopped working... are you sure you have right guid?

whether it needs that extra \ seems to vary - https://superuser.com/questions/295913/how-to-mount-and-unmount-hard-drives-under-windows-the-unix-way

 

[N3rdR4ge]

Thanks for the response Colif. I used to have these commands in a bat file when my computer was running an older version of windows 10. I used it to disconnect and reconnect all internal drives on a regular basis and it worked fine. It only stopped working after 1703 as far as i'm aware. I haven't used the bat file in a while, but I confirmed the commands were correct. They won't work when manually typed either. Just using regular command prompt with admin on win 10 pro.

 

[Colif]

I would be tempted to ask on Superuser or tenforums, more Windows users on both... not saying no one knows it here but you may get answer faster on there.

Creators edition broke a few things, debugger doesn't cope with it very well, so less used commands are probably just as bad.

If either can help, show us answer so others can know as well

 

[julian.poyntz]

I have just had this myself as I use it for a monthly / weekly robocopy routine in an attempt to deal with rasonsomware (dismount drives, bitlockered - does not know it is there and then copy)

anyway, found it had stopped working for me too
I could mount the volume via disk manager
once mounted I then ran a "mountvol <drive letter> /P"
This then in mountvol gave me the message about needing to create a mount point
I then went back to disk manager, assigned it back to the drive letter
For now I can use mountvol to mount / unmount the volume