Hidden volume mounting error

Open
#1,854 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
c
Domain
security

Research direction

The report compares hidden volumes created with VeraCrypt 1.25.9 on Windows 7 and mounting behavior in 1.26.24 versus 1.26.29 on Windows 10; it does not name files or tests. Start by comparing changes between those versions and tracing the hidden-volume mount path, then reproduce the failure with the reported version and system combination. Done means hidden volumes mount normally in 1.26.29 while regular-volume behavior remains unaffected.

Written by the indexing model from the issue text.

Description

bug

Because we need to use both Win7 and Win10 systems, hidden volumes created using version 1.25.9 in Win7 can be mounted normally using version 1.26.24 in Win10, but cannot be mounted normally using version 1.26.29. Regular volumes are fine

Dominant language
C
Stars
11.7k
Forks
1.4k
Avg merge
1d 1h
Merged PRs (30d)
28

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from veracrypt/VeraCrypt

All issues in veracrypt/VeraCrypt

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.