Re: use a drives guid instead of its letter - where is the drive root ?

Vanguard,

> Weird scenario: can create at root, but cannot delete at root.

Somewhat : I cannot delete a *file* at root.   Creating and deleting a 
*folder* doesn't seem to be a problem.

> However, seems the UNC syntax you use is invalid as it is supposed
> to point to a shared resource, like a folder. Looks like you found
> a loophole.

I have a different POV : that volume guid(s usage) never was an UNC, and you 
just assumed it had to be.

https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/mountvol

Take a look at the example provided in the above.  You might notice that it 
*doesn't* include a foldername after the volume guid part.   And mind you : 
thats MS own information.

> As an experiment, I ran mountvol to get the GUID for the C: drive.
[snip experiments]

Your tests confirm the ones I did.

Funny that your Win10, several versions after my own WinXP, still has the 
same "loopholes" :-)

Regards,
Rudy Wieser