Sieban

VeraCrypt currently says that VSS support is not supported for non-system mounted volumes due to missing API documentation. I'd like to ask whether this limitation could be revisited. Microsoft now documents the VSS provider model, including software snapshot providers and interfaces such as 'IVssSoftwareSnapshotProvider'. It seems technically possible for VeraCrypt to add support by implementing its own VSS software provider or equivalent storage-stack integration. This would be very useful for...

Thank you!!!

Thank you, Mounir. To clarify, I wasn't in any way criticising - like many others, I'm just a touch anxious due to the possible ramifications and I was hoping to be able to install the update with some margin in case of unexpected problems. I appreciate the update and all the hard work you are putting in!

We're now only a few weeks away from the deadline. When will the corrected version be released?

You're not making any sense. When you encrypt in-place a system drive, you can use it fully - meaning the operating system is fully functional creating, renaming, copying, deleting files all the time. You can also manually create, rename, copy, move, and delete files as much as you want - and VeraCrypt will have no problems whatsoever. Therefore, I'm trying to find out why VeraCrypt can't do the same thing for non-system drives. And although I appreciate your trying to suggest a different approach,...

This isn't about best practices. My question is - if VeraCrypt is technically capable of encrypting a system drive in place while keeping it fully useable, why can't it do the same for a non-system drive?

Yes, but when you do that, it warns you that the drive will be unmounted and unavailable until encryption is complete. That's the issue in question.

Why is it that VeraCrypt is capable of encrypting a system drive in place while the operating system is still fully functional, but to do it to a non-system drive requires unmounting? Why can VeraCrypt not encrypt a non-system drive in place while it remains fully functional as well?