I'm getting a weird issue in Windows 11 where executables will not run from a VirtioFS mounted drive when mounting them using the script from the recommended post. Instead, Windows will show a network error stating that it cannot access the file path. This only happens with some executables though, not all. I have tried to follow the directions on the gitlab page to see if I can get it working that way, but the commands always return "access denied".
In one case, a file gave an error that windows cannot access the temporary version of the executable in the %appdata%\local\temp folder, and another gave a ShellExecuteEX failed; code 1203 error. But most cases the error just says that windows cannot access that file path. This does not happen if the executables are run from the vdisk.
Does anyone have any theories as to what might be going on?
Edit: just checked, error 1203 is "ERROR_NO_NET_OR_BAD_PATH: The network path was either typed incorrectly, does not exist, or the network provider is not currently available. Please try retyping the path or contact your network administrator." Which is basically the same as the other issues; windows can't access the file. When using network shares, I've had to use a registry edit that allows the system to see the shares, which is necessary to run executables. Could there be something similar going on here?
