Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to create encrypted partition on Windows 11 with Storage Spaces #1316

Open
leubgi opened this issue Mar 4, 2024 · 3 comments
Open
Labels

Comments

@leubgi
Copy link

leubgi commented Mar 4, 2024

Expected behavior

Encryption of a NTFS partition from a Storage Spaces drive (RAID)

I was using veracrypt with Storage Spaces on Windows 10 x64 on my previous computer without any issue. I can't remember the exact version of veracrypt maybe around 2-3 years old

Observed behavior

It failed, whether it's a new encrypted volume or encrypt partition in place

Steps to reproduce

  1. Create a new virtual drive with Windows 11 Storage Spaces
  2. Veracrypt : Volume : create new volume
  3. New encrypted partition / Encrypt the partition
  4. Filesystem : NTFS

Screenshots

Your Environment

Please tell us more about your environment

VeraCrypt version:

1.26.10 x64
Operating system and version:
Windows 11 22H2
System type:
64 bits

@leubgi leubgi added the bug label Mar 4, 2024
@Roydee34
Copy link

Hello I ran into this same error message today, I have 2 x 2tb ssds and Storage spaces set them to make one large 4tb drive.

Veracrypt latest build (as off May 2024) on Windows 11 64bit 23H2 (as off May 2024)

When I attempt to encrypt my 4tb storage space single drive, VC promps with an error message:
"Windows formatEX API failed to format the volume as NTFS/Exfat/REFS Failure status = format_finished"

Anyhow I noticed VC auto ask if you wish to try FAT instead which then works fine, but naturally one can't use bigger files so I investigated this error and found its due to Storage spaces using GPT system. So I switched the new Storage Space drive to Dynamic disk and re-tested it and VC now completes with ntfs file system without the error.

You will have to do the above with aomei partition assistant or Windows Disk management built in tool, just convert the Storage Space new drive to Dynamic disk. If you are stuck google : how to convert to Dynamic disk then run the VC program and it will work.

@Roydee34
Copy link

Expected behavior

Encryption of a NTFS partition from a Storage Spaces drive (RAID)

I was using veracrypt with Storage Spaces on Windows 10 x64 on my previous computer without any issue. I can't remember the exact version of veracrypt maybe around 2-3 years old

Observed behavior

It failed, whether it's a new encrypted volume or encrypt partition in place

Steps to reproduce

  1. Create a new virtual drive with Windows 11 Storage Spaces
  2. Veracrypt : Volume : create new volume
  3. New encrypted partition / Encrypt the partition
  4. Filesystem : NTFS

Screenshots

Your Environment

Please tell us more about your environment

VeraCrypt version:

1.26.10 x64 Operating system and version: Windows 11 22H2 System type: 64 bits

Please check my message above since I found a solution to it, it should hopefully fix things for yourself or anyone in the future.

@leubgi
Copy link
Author

leubgi commented May 25, 2024

Thanks for the update, yes I noticed it works with FAT but it's too limited for practical use.

Anyway, it seems your workaround isn't that great : Dynamic disk is deprecated and can be hard to restore on another computer contrary to Storage Space. What's even more concerning is that you are basically running 3 volumes on top of each other : VC volume -> Dynamic Disk (at least a simple volume) -> Storage Space.

Such a shame the dev doesn't seem interested in fixing this issue...

I will probably end up with just a dynamic disk (I suppose it should work even without Storage Space) but it's far from ideal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants