Fix erroneous 2 TiB limit for hidden file containers in GUI wizard#1672
Merged
idrassi merged 1 commit intoveracrypt:masterfrom Apr 13, 2026
Merged
Conversation
Member
|
Thank you for the fix. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes: #1560
Summary
Fix the GUI wizard incorrectly rejecting hidden file containers larger than 2 TiB.
Currently the outer hidden-volume size check is applied even when the selected target is a normal file. In that case the wizard uses the file-hosted sector size constant, so the FAT sector-count check incorrectly caps the GUI flow at 2 TiB.
This change restricts that check to device-hosted paths only:
if (SelectedVolumePath.IsDevice() && OuterVolume && VolumeSize > TC_MAX_FAT_SECTOR_COUNT * SectorSize)This has been tested on Linux using a 3 TiB file.