You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would love to see a different error-message when disk label length exceeds 32 characters with command line on Windows.
The current error message is not self-explaining. Current error message "Error while parsing command line."
Current behavior
When entering a label via command line that exceeds 32 characters the error message "Error while parsing command line." is displayed.
Desired behavior
When entering a label via command line that exceeds 32 characters a more self explanatory message is desired, like "Label exceeded 32 characters."
Screenshots/Mockup/Designs
N/A
Additional information
Mention the limit of 32 characters in the command line syntax and in the manual.
Your Environment
Please tell us more about your environment
**VeraCrypt version: 1.26.7 (64-bit) **
Operating system and version: Windows 10 Pro 22H2 Build 19045.4046
System type: 64-bit
The text was updated successfully, but these errors were encountered:
Would love to see a different error-message when disk label length exceeds 32 characters with command line on Windows.
The current error message is not self-explaining. Current error message "Error while parsing command line."
Current behavior
When entering a label via command line that exceeds 32 characters the error message "Error while parsing command line." is displayed.
Desired behavior
When entering a label via command line that exceeds 32 characters a more self explanatory message is desired, like "Label exceeded 32 characters."
Screenshots/Mockup/Designs
N/A
Additional information
Mention the limit of 32 characters in the command line syntax and in the manual.
Your Environment
Please tell us more about your environment
**VeraCrypt version: 1.26.7 (64-bit) **
Operating system and version: Windows 10 Pro 22H2 Build 19045.4046
System type: 64-bit
The text was updated successfully, but these errors were encountered: