Mount crash GetType:48 with macFUSE 5.3.3, not FUSE-T

Abierto
  • ¿Algo no está bien?
#1,841 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
40/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
c, macos
Área
desktop, operating-systems

Línea de trabajo

Start by reviewing the macOS mount and FUSE helper paths, especially where VeraCrypt reads the auxiliary mount control file; the report identifies FilesystemPath::GetType at line 48 but names no source file or test. Compare the failing macFUSE 5.3.3 setup with the working 5.1.3 setup and inspect the attached logs and crash report. Done means mounting succeeds with macFUSE 5.3.3 without the crash.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug

[macOS] VeraCrypt crashes on mount with macFUSE 5.3.3 — "control" file missing, FilesystemPath::GetType:48

Expected behavior

After upgrading macFUSE from 5.1.3 to 5.3.3 and rebooting to approve the system extension, mounting an existing VeraCrypt volume should succeed as it did previously on 5.1.3.

Observed behavior

VeraCrypt quits unexpectedly (crash dialog with "Report…" option) during mount. The underlying error reported is:

Device not configured:
/var/folders/rs/5_xs70_17ws709gdytqhy8900000gn/T//.veracrypt_aux_mnt2/control
VeraCrypt::FilesystemPath::GetType:48

This indicates the auxiliary FUSE mount helper never created the expected control file/socket before VeraCrypt tried to read it. sudo kmutil showloaded | grep -i fuse shows nothing during a mount attempt, and a filtered log stream/log show capture across io.macfuse, com.apple.FSKit, and free-text "fuse"/"mount"/"veracrypt" predicates shows no relevant macFUSE mount activity at the time of the crash — only unrelated FSKit background events (Launch Services database changes). This suggests the kext is not engaging at all, rather than a version-mismatch handshake issue.

I'm running the macFUSE-compatible build, not the FUSE-T build. All existing issues I could find matching this exact error string (#1438 , #1667 ) are filed against the FUSE-T build, so I wanted to flag that this is happening with macFUSE proper as well, in case it's a distinct cause.

Why macFUSE rather than FUSE-T

For reference/context: I deliberately use the macFUSE build rather than FUSE-T. My reasoning is that macFUSE's maintainer (Benjamin Fleischer) has been publicly transparent about why the kernel extension component is closed-source, has stated openness to independent security review, and the project has a long, active maintenance history. FUSE-T remains closed-source with less public detail from its author, so on balance I've preferred macFUSE despite the kext's drawbacks. Given that macFUSE 5.1.0+ now offers an FSKit backend that avoids the kext entirely, I'd also be interested in using -obackend=fskit with VeraCrypt once/if that's viable — is FSKit backend support (which requires linking libfuse3 rather than the current libfuse2) something on the roadmap? Happy to help test if so.

Steps to reproduce

  1. Starting state: macOS 26.6 (Tahoe, build 25G72), Apple Silicon M2, VeraCrypt working normally with macFUSE 5.1.3.
  2. Run brew reinstall --cask macfuse to upgrade to macFUSE 5.3.3.
  3. Reboot and approve the system extension prompt in System Settings → Privacy & Security.
  4. Open VeraCrypt from Launchpad, select an existing volume, enter password, click Mount.
  5. VeraCrypt crashes with the error above instead of mounting.
  6. Reboot a second time for good measure
  7. Retried as 4-5, same results

Workaround: when I reinstall macFUSE 5.1.3 it works fine once again

Screenshots

Image

Your Environment

VeraCrypt version: 1.26.24
macFUSE version: 5.3.3 (upgraded via Homebrew from 5.1.3, which worked correctly)
Operating system and version: macOS 26.6 Tahoe (build 25G72)
System type: Apple Silicon (M2), 64-bit

Attachments

veracrypt_mount_filtered.txt

VeraCrypt-2026-07-28-214140.ips.json

Lenguaje dominante
C
Estrellas
11.7k
Forks
1.4k
Merge medio
1 d 1 h
PR fusionados (30 d)
28

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de veracrypt/VeraCrypt

Todos los issues de veracrypt/VeraCrypt

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.