Argon2id resume fails with ResumeInPlaceEncWaitThreadProc:408 on non-system volume

Abierto
  • ¿Algo no está bien?
#1,810 1 comentario 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
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
c
Área
security

Línea de trabajo

Start at ResumeInPlaceEncWaitThreadProc:408 and compare the Argon2id header-decryption path with the related report in #1614. The interruption cause is still a placeholder, so first obtain that detail and a reproducible case; done means the interrupted non-system-volume encryption resumes successfully with the correct password.

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

Descripción

bug

VeraCrypt version: 1.26.29
OS: Windows 11
Volume type: Non-system volume, internal HDD, in-place encryption
KDF used: Argon2id
PIM: Left empty (default)
Keyfile: None used
Hash/Cipher: default / not noted

Summary:
In-place encryption of an internal non-system hard drive was interrupted
at approximately 5% completion after [précise ici : ex. "a Windows
restart" / "a forced shutdown" / "clicking Defer"]. The volume cannot
be resumed or recovered afterward — VeraCrypt consistently fails to
decrypt the volume header with the correct password.

Error message:
"Operation failed due to one or more of the following:

  • Incorrect password
  • Incorrect Volume PIM number
  • Incorrect PRF (hash)
  • Not a valid volume
  • The volume uses an old algorithm that has been removed.
  • TrueCrypt volumes are no longer supported.
    Source: ResumeInPlaceEncWaitThreadProc:408"

Steps to reproduce:

  1. Start in-place encryption of a non-system internal HDD using
    Argon2id KDF with default (empty) PIM.
  2. Interrupt the process at low completion percentage (~5%) via
    [décris la cause exacte de l'interruption].
  3. Relaunch VeraCrypt — it correctly detects an interrupted process
    and prompts to resume Encrypt/Decrypt.
  4. Select "Encrypt", enter the password, select the correct device.
  5. Operation fails immediately with the error above.

Expected behavior:
Encryption resumes normally from the last processed sector.

Actual behavior:
Header decryption fails every time, even though:

  • The password has been verified correct via copy-paste (ruling out
    keyboard layout/typo issues)
  • No keyfile was used
  • PIM was left at default (empty)
  • The correct device/partition was selected (verified by size/ID)

Troubleshooting already attempted (all failed with same error):

  • Retyping the password directly
  • Copy-pasting the password from a text editor to rule out input errors
  • Closing all applications with potential disk access, including antivirus
  • Restarting the system before retrying
  • Restore Volume Header using the embedded backup header (Tools >
    Restore Volume Header, no external backup file) — same 408 error,
    suggesting both the primary and backup headers fail to decrypt
    identically with this password

Possible related issue:
This may be related to #1614 ("Possible Argon2id incorrect derived
key"), which describes header decryption failing with Argon2id KDF
despite using the correct password, in a controlled test case.

Data risk / urgency:
The volume was only ~5% encrypted when interrupted, meaning the vast
majority of data on the drive is still in its original unencrypted
state. However, without being able to resume or properly decrypt via
VeraCrypt, the drive currently cannot be safely used or accessed
through normal means.

Additional info:
Happy to provide further logs, a memory dump, or test with a
reproducible sample container if that would help diagnose whether
this is the same root cause as #1614.

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.