Execution of ".exe" fails in shared folders, with Windows 10 or 11

[FelixG]

Host Windows 10. Guest Windows 10 or 11. (Windows XP x32 and Windows 7 x64, work fine)

When an ".exe" is run inside a shared folder, it gives the error "The specified path does not exist" depending on the number of characters in the path + the file name, and the text entered in "Folder name" (sharename).

Examples with mountpoint = "X:":

sharename = "1":

OK    X:\1234567.exe

NOK  X:\12345678.exe

sharename = "12":

OK    X:\12345678.exe

NOK  X:\123456789.exe

sharename = "123":

OK    X:\123456789.exe

NOK  X:\1234567890.exe

... sharename = "12345678":

OK    X:\12345678901234.exe

NOK  X:\123456789012345.exe

Interestingly, the more characters sharename has, the more characters the ".exe" file name allows.

[fth0]

After some own experimentation, to give a few hints to the developers: ;)

"\\VBoxSvr\VM Transfer"   <- determines the buffer space
"12345678901234567.exe"   <- filename without path component
"VBox-Windows\1234.exe"   <- backslash counts as one character

"\\VBoxSvr\1"
"1234567.exe"

[fth0]

Another hint to the developers:

The issue only occurs when using the drive mapping (e.g. "Z:"), but not when using the UNC-Path.

[landgraph]

Hi, I have an issue, which might have same root cause with yours. But in my case I have a machine reboot if I try to run .exe on a shared folder.

Could you check in your VM settings: System -> Processor, is checked "Enable PAE/NX"?

It looks like solved the issue in my case.

P.S. I'm using VirtualBox 7.0.8

[FelixG]

Hi, with version 6.1.32 the error occurs regardless of whether the PAE/NX option is checked.

I will try version 7 after the summer, at the moment I can't.