"Incorrect function" exception when running an exe not in C:\ #13605
Comments
|
|
@blancmangit is |
|
Local |
|
What is a file system on the H: drive? And What is |
|
The failure here is occurring when PowerShell checks to see if The underlying Win32 error is ERROR_INVALID_FUNCTION which has the message matching the error PowerShell reports back
The docs for FSCTL_GET_REPARSE_POINT indicate the types of filesystems that support this FSCTL code but I would also guess that It sounds like we need to have a further check on |
|
The drive may certainly be exFAT. I won’t be able to check that for suretill Monday at the earliest. The file is a plain exe, not any kind of hard or symbolic link and it is not related to WSL. In fact the same exception is raised for any exe I’ve tried on that drive. |
|
I'm 95% certain that exfat has no support for reparse points which explains why DeviceIoControl is returning |
|
No need does P/Invoke to check if reparse points are supported. We should return null if ERROR_INVALID_FUNCTION - the error code in the context implicitly says that reparse points are not supported.. |
|
i have same problem on preview7,i allready return to preview6,problem gone. |
|
You can download artifact from #13634 and check. |
I confirm this fixes the problem for me in a Virtualbox shared directory in a Windows 10 guest! It was a bit of a struggle to discover the artifacts, so writing notes for others:
|
|
Handy links: |
|
Handy links: |
Steps to reproduce
Expected behavior
Actual behavior
Environment data
The text was updated successfully, but these errors were encountered: