VeraCrypt FUSE-T 1.26.29 doesn't accept admin password

[NicoCaldo]

Expected behavior

VeraCrypt mounts my encrypted device after having filled the password

Observed behavior

When asked to input the user-admin password, even if correct, a new window asks for the password. Basically, it won't accept the user-admin password even if it's correct

Steps to reproduce

1. Install Fuse-T
2. Install VeraCrypt
3. Try to mount all devices
4. Input the password of the device
5. Input user-admin password

Screenshots

Your Environment

Please tell us more about your environment

VeraCrypt version: FUSE-T 1.26.29
Operating system and version: Mac Sequoia 15.7.7 on Mac Air M3 24Gb RAM

[NicoCaldo]

Related #1628 #1602

[idrassi]

Thanks for the report. This password dialog is displayed before the FUSE-T mount stage: for device-hosted volumes, VeraCrypt first has to start an elevated helper through sudo in order to enumerate and open raw /dev/... devices.

Could you please test the following?

1. Launch VeraCrypt normally.
2. Before trying to mount anything, click Select Device.
3. Tell me whether the same administrator-password dialog loop happens there, or whether the device list opens normally.

This test is important because Select Device also uses VeraCrypt sudo elevation path, but it doesn't use FUSE-T at all.
If the same loop happens there, the problem is almost certainly in the elevation path rather than in FUSE-T.

Please also run this in Terminal and share the result:

/usr/bin/sudo -k
/usr/bin/sudo -S -p '[sudo test] password: ' /usr/bin/true
echo "sudo status=$?"

Use the same macOS user password you enter in VeraCrypt. The expected result is sudo status=0.

As another diagnostic test, please close VeraCrypt completely and launch it from Terminal as root:

/usr/bin/sudo -k
/usr/bin/sudo /Applications/VeraCrypt.app/Contents/MacOS/VeraCrypt

Please don't use sudo open -a VeraCrypt, run the executable directly as shown above.
Then try Select Device and the same mount operation again. If VeraCrypt is already running with root privileges, it shouldn't need to show the administrator password dialog. If another device access or mount error is currently hidden by the retry logic, this test should make the real error appear. Please share the exact message shown, if any.

It seems if the user is not in sudoers, this software cause an authentication error like OP said.

Even if you can use su - to elevate yourself, this software expects you in sudoers group.

[NicoCaldo]

Thanks @idrassi. I'll retry by the end of this week to try what you have proposed.