@cyberponk

Hello, I have two questions for you.

I'm using version v1.6 of your code, so I should use:

CALL :RequestAdminElevation "%~dpfs0" %* || goto:eof

or

CALL :RequestAdminElevation "%~dpf0" %* || goto:eof

Which is better? "%~dpfs0" or "%~dpf0" ???

The second question is (see the attached screenshot).

When I run a batch code file converted from .cmd to .exe, for example, TEST.exe, with elevated administrator privileges on a shared folder on a Windows 10 x64 system in VirtualBox, I get a path error.

When I run the same file without administrator privileges, it runs correctly, but with elevated administrator privileges, it doesn't and displays a path error.

I need to copy the file from the shared folder to the desktop in VirtualBox and run it from there – then it works properly with elevated administrator privileges.

Is there any way to get the permissions and current path also work when I run TEST.exe directly through VirtualBox from the shared folder on my PC?

When I run TEST.cmd itself before converting it to .exe format, I can run it directly from the shared folder in VirtualBox without copying it to the desktop, and it also runs with elevated administrator privileges.

The problem only occurs when I run it in .exe format and directly from the shared folder in VirtualBox without moving the file.