crbrac

@idrassi Apologies for the delayed feedback. The problem seems to be fixed for the most part. There's a significant improvement in terms of the frequency of hangs. I have only encountered a handful of hangs (roughly a week or more apart) since updating to the latest release containing the fix, which is a drastic reduction compared to the earlier versions. Thank you

@idrassi Apologies for the delayed feedback. The problem seems to be fixed for the most part. There's a significant improvement in terms of the frequency of hangs. I have only encountered a handful of hangs (roughly a week or more apart) since updating to the latest release containing the fix, which is a drastic reduction compared to the earlier versions. Thank you again.

It will only return 100% valid if you certify the Veracrypt certificate with yours prior to doing the signature check. You may have overlooked this because you said you are not familiar with gpg4win. Highlight the imported Veracrypt certificate > choose Certify from the Toolbar/Menu or right click the imported Veracrypt key: 5069A233D55A0EEB174A5FC3821ACD02680D16DE (in the Kleopatra window) > Certify.

Firstly, it is always a prudent practice to keep a second copy of your container (or any other file that may matter to you) as a fallback. No grounds for second thoughts there even if there is an exception to every rule. You say your USB drive needs erasing to enable password protection. If that's the case why would you be in any doubt whatsoever of the need for a backup of the container? And, yes you will still have access to your backed up container once you move it back to your USB drive after...

Yes, if the Veracrypt folder (Container ?) itself is not damaged, you should be able to decrypt (or did you mean Mount ?). You can also decrypt if you run VC in portable mode: https://www.veracrypt.fr/en/Portable%20Mode.html You have to be consistent with how you address VC Volumes: Containers, Partitions (System & Non-system), Volumes (System & Non-system), Folders, Files. You can't casually throw them around by calling it a folder only to switch to a file in the next sentence. Can throw off those...

I linked you to the issue just to alert you to any potential for mishaps if they (MS) muck up somewhere during the deployment phase via Windows Update. Once the Revocations are in place (manually or via an update), your external installation Boot media/Backup Rescue Disks (across the board) will be rendered un-bootable from, with Secureboot enabled. You'd have to manually disable Secureboot until all your Boot media are updated with the modifications, to get back in. Ideally we'd want the updated...

@kysvggbb You're running Windows 11 (so likely UEFI and Secureboot enabled). You'll very soon have to contend with this issue: KB5025885: How to manage the Windows Boot Manager revocations for Secure Boot changes associated with CVE-2023-24932 https://support.microsoft.com/help/5025885. And, there's no opt-out, it seems. More details here: https://www.elevenforum.com/t/additional-guidance-for-devices-using-secure-boot-to-address-cve-2023-24932.14761/

Thank you Was late to find out they had a change of mind.