-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.2.6 RC7 broke running of files as admin #404
Comments
Huh that is surprising. I'll check into it |
Yeah definitely doesn't work. Not much in FileSpy output either - peculiar. |
You can change the error by setting mimic on, so that is interesting. Launching as admin cares about filesystem type? |
At least on 2.2.3-RC6 this still worked. I updated from that release, so something might have changed |
I tried 2.2.6-rc6, rc5, rc4 and had the same issue. But didn't go as far back as 2.2.3. But it'll just be a quirk somewhere. |
da1fdfb plus setting mimic=ntfs will fix it. |
I will test once a new RC gets pushed. mimic is a parameter for zpool import ? |
It's for any dataset, like |
System information
zfswin-2.2.6rc7
zfs-kmod-zfswin-2.2.6rc7
Windows 11 23H2
Describe the problem you're observing
Upon updating to the new RC, applications cannot be started as Admin on a ZFS volume anymore
Describe how to reproduce the problem
Create a simple dummy .bat file on a ZFS volume.
In my testing, I used a ZVOL directly, not a dataset.
Then, try to launch the .bat file with rightclick -> run as admin.
The command will fail with "Auf [test.bat] konnte nicht zugegriffen werden" , translating to "Could not access [test.bat]".
The .bat file can be launched without admin without problems.
The text was updated successfully, but these errors were encountered: