Tweet
We have had a report of an error when using OSFMount. This post is to document the error messages and work around.
Problem:
Error messages, "Incorrect function" & "ShellExecuteEx failed code 1", when running executables from a volume created with OSFMount.
Conditions:
Using OSFMount V3.1.1003 on Windows 11 Pro x64 24H2, attempting to run an executable within a logical disk emulation drive ramdisk can fail to execute. This ONLY happens with 24H2, only with executables requiring UAC Admin elevation permission and only with logical volumes. Other executables not requiring UAC elevation work fine on the ramdisk. Win10 was also OK.
Windows seems to fail to display the UAC Admin prompt window (so the user never becomes Admin) and then because the executable can only run as Admin, there is an error. So maybe a Windows bug or maybe something missing in the device driver emulation of a disk volume.
Solutions:
Use a physical disk emulation ramdisk instead (this is an option in OSFMount)
Notes:
Other similar mounting software also has the same issue in 24H2. So there has definitely been changes in Windows that broke this.
Example:
https://forums.tomshardware.com/thre...ivers.3858332/
Problem:
Error messages, "Incorrect function" & "ShellExecuteEx failed code 1", when running executables from a volume created with OSFMount.
Conditions:
Using OSFMount V3.1.1003 on Windows 11 Pro x64 24H2, attempting to run an executable within a logical disk emulation drive ramdisk can fail to execute. This ONLY happens with 24H2, only with executables requiring UAC Admin elevation permission and only with logical volumes. Other executables not requiring UAC elevation work fine on the ramdisk. Win10 was also OK.
Windows seems to fail to display the UAC Admin prompt window (so the user never becomes Admin) and then because the executable can only run as Admin, there is an error. So maybe a Windows bug or maybe something missing in the device driver emulation of a disk volume.
Solutions:
Use a physical disk emulation ramdisk instead (this is an option in OSFMount)
Notes:
Other similar mounting software also has the same issue in 24H2. So there has definitely been changes in Windows that broke this.
Example:
https://forums.tomshardware.com/thre...ivers.3858332/