![]() The new version of the encryption software adds support for Windows on ARM64, Apple Silicon M1 and OpenBSD, but it also removes support for the following operating systems: VeraCrypt 1.25 is a major new version that changes system requirements significantly. ![]() The system needs to be restarted after a successful installation, as the new driver needs to be loaded during system start. The new version of VeraCrypt updates any existing version that is installed on the system. Note that the GitHub repo has not been updated yet as well. The first thing I did was to create a backup header for all of my True Crypt partitions for additional restoration options in case of an emergency.VeraCrypt 1.25 is not yet listed as a download on the official project website, but downloads are available on the project's SourceForge project page. I guess I was lucky that I was able to restore the header without the backup. You can use cloud hosting services such as Dropbox to host those, or keep those safe on a USB Flash Drive or even your smartphone. Make sure you save the data to another drive or location, as it won't do you anything good to keep it on the True Crypt partition. ![]() This can be done by selecting the True crypt partition under Select Device, then Tools from the main True Crypt window and finally Backup Volume Header. To avoid header problems with True Crypt volumes it is suggested to backup the volume headers so that they can be restored in case of corruption. This fixed the problem that the True Crypt volume was not recognized and the encrypted partition mounted as normal on the system. I selected "use backup header embedded in volume if available" that is an option in the Mount Options in True Crypt's password field and entered the password of the True Crypt partition again. Now this might not work in all cases as these can also become corrupted but it did work in my case. True Crypt offers so called mount options and one of these mount options is to use embedded backup headers if they are still available in the encrypted volume. It was clear that the headers where somehow corrupted. ![]() ![]() It was later that I discovered that these advanced troubleshooting programs were not needed for the problem that I was experiencing. I started with advanced troubleshooting programs like Test Disk trying to figure out what was wrong. The drive itself showed up fine in Windows Explorer and Disk Management. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |