I started using it on a single PC and after a disastrous Windows 10 update / upgrade it got hosed. Luckily I use Macrium reflect, which when restored put the OS into an unencrypted state. Since major Windows 10 updates are a full scale OS replacement it makes it tough to update it.

I've since relegated it only my DATA drives / partitions only. I use SED (Self Encrypting Disk) on my main laptop, for the other machines I either encrypt the OS with Bitlocker (required by my work) or leave the OS unencrypted and just encrypt the data. For these machines I make sure to never use them for anything sensitive.

• Some SSDs experience severe performance degradation. Google around and you can see many examples of this. Some, many newer models, perform adequately.

• It will not just encrypt the used space only, whatever you assign to be encrypted is encrypted, or will be as soon as something is written to it.

• The only way to do "used space only" is to encrypt a container file that is the ultimate size you want it to be. When setting it up VC offers to overwrite the space to make sure recovery is not possible.

• To ensure adequate space for cell wear leveling is to provide for it using over provisioning if your SSD software provides that function.

• Comparison to Bitlocker. Two different animals. The main worry is that MS has provided or will provide back doors to the encryption. One concern with VC is vulnerabilities that are not covered.

VC support is waning, i suspect partly due to the pandemic reducing resources and people moving on to other projects or dropping project altogether. MANY projects are experiencing this. Hopefully it will pick back up once it has passed, but people that are starving, giving up essentials like bandwidth or working multiple jobs to make ends meet are not very eager to put a lot of effort into FOSS at this time.