Okay, this is a little strange, but I'm trying to unlock and access (mount) an container which is itself stored in another virtual drive from Cryptomater. This works on Windows, but on Debian systems, I get an error. Does anyone know what I'm doing wrong? The error indicates a permissions issue. Thank you!
I just checked. I'm on Windows 11 25H2. The March 2026 Update (KB5086672) replaced the file \efi\microsoft\boot\bootmgfw.efi .
First, I doubt (hope not!) the account is actually deleted, it's most likely just disabled/turned off. Your accounr is just in the recycle bin... :) I would email people in the crypto community/other devs who would know someone at MS - bruce schneir, chris titus, niels ferguson; or are someone at MS - karen easterbrook, nathan ide. I would also contact media - tom's hardware, ars techica, wired, the intercept, EFF. there are a bunch of reddit subs that would apply - both in the privacy and crypto...
First, I doubt (hope not!) the account is actually deleted, it's most likely just disabled/turned off. Your accounr is just in the recycle bin... :) I would email people in the crypto community/other devs who would know someone at MS - bruce schneir, chris titus, niels ferguson; or are someone at MS - karen easterbrook, nathan ide. I would also contact media - tom's hardware, ars techica, wired, the intercept, EFF. there are a bunch of reddit subs that would apply - both in the privacy and crypto...
Hello Mounir, I have the same problem as described here. I am using version 1.26.24 on a laptop with a screen resolution of 3200 x 1800. In the BIOS I can not set anything, so my hope is the configuration of the Boot Loader. Here is a portion of the PlatformInfo file: <graphdevices count="2"> <graphdevice index="0" modes="7" h="3200" v="1800"> <graphmode index="0" h="3200" v="1800"> <graphmode index="1" h="640" v="480"> <graphmode index="2" h="800" v="600"> <graphmode index="3" h="1024" v="768">...
Some practical questions about the most current Windows release, until this situation can be resolved: The current version 1.26.24 is signed with the 2011 CA, which is soon to expire. This will certainly affect secureboot.... but how will this affect mounting non-system volumes (partitions and/or file containers) as a user? Will one have to disable secureboot just to install VeraCrypt, even if not using system encryption? And how will this affect portable use? The same question applies to unsigned...
Maybe, this issue is related: https://sourceforge.net/p/veracrypt/discussion/general/thread/9620d7a4b3/?limit=25
File not shown after mounted
I have successfully mounted veracrypt volume but i am not able to see my files and folder inside it. however used space is showing as per my files and folder data was there.
delete this topic please
I just noticed that I have recovery disabled. It seemed to me that it was active before encrypting, or maybe I had already disabled it previously, I don't remember. Do you think it should be enabled or disabled with encrypted System partition ? This is the command to check the status of WinRE: reagentc /info . (reagentc /enable , reagentc /disable) .
I just noticed that I have recovery disabled. It seemed to me that it was active before encrypting, or maybe I had already disabled it previously, I don't remember. Do you think it should be enabled or disabled with encrypted System partition ? This is the command to check the status of WinRE: reagentc /info . (reagentc /enable , reagentc /disable) .
How to prevent Windows Update from overwriting UEFI entries and deleting the Veracrypt one ? https://imgur.com/DqIAb2v Windows 11, vc 1.26.27 . This is the second time i have to use the recovery disk to restore the Veracrypt bootloader, because every time there is a Windows Feature Update, the UEFI NVRAM is rewritten and erases the Veracrypt entry. I don't know if this is just me or a common problem (in this case, i think it's a critical issue that needs to be addressed).
I am assuming you used pre-1.26.x software version when you created the VeraCrypt volumes. You will need to use 1.25.9 or older software to mount the volumes due to you are likely using deprecated item(s) that will not work when using 1.26.x version. https://veracrypt.jp/en/Conversion_Guide_VeraCrypt_1.26_and_Later.html
So I created two veracrypt drives on a Windows 10 computer, both on USBs. One of the usbs is entirely encrypted and the other USB contains an encrypted container. I believe I have the correct passwords for both. Both USBs appear when plugged into a computer, and I can see the encrypted container, copy it, etc. On the computer they were created with they mounted perfectly, but even at the time I created them, I could only open them on the original computer that made them. I believe they were encrypted...
@idrassi I would try sending an email to Microsoft CEO, Satya Nadella at: satyan@microsoft.com Use brief details from your first post in this thread along with the error message screenshot. Possible email shown below. Subject Line: Reinstate Partner Center Program Account for my Software Developer Business Dear Satya Nadella, I need someone from your staff's to help me get my Partner Center program account reinstated for my Windows developer business. I attempted to login to my Partner Center account...
I'm really sorry to hear this bad news. Someone probably reported the software, claiming it could be used for illegal activities, which led to the account being deleted. Unfortunately, the general trend is increasingly toward controlling and monitoring what people do, and there is less and less respect for privacy. Is there no way to get around this limitation, even temporarily? Perhaps by restricting the software, for now, to non-system partitions and volumes?
This is a sad turn of events, Mounir! This may seem a bit out in left field (to use an American idiom), but is it possible that some seemingly minor aspect of your recent relocation to Japan is at the root of this inexplicable account revocation? Grasping at straws is a hobby of mine :)
Maybe I should ask here, I tried building the latest Veracrypt from source (git clone) on Linux but still wasn't seeing argon2 options in the GUI. From a cursory glance it looked like argon2 should have been included in the build. Is it just an issue of the options not showing on the gui? I'm on EndeavourOS with KDE and Wayland and kernel 6.19.10, if that matters. Also if argon2 should be there, I'd be more than happy to help test/fix the issue.
Maybe I should ask here, I tried building the latest Veracrypt from source (git clone) on Linux but still wasn't seeing argon2 options in the GUI. From a cursory glance it looked like argon2 should have been included in the build. Is it just an issue of the options not showing on the gui? I'm on EndeavourOS with KDE and Wayland and kernel 6.19.10, if that matters.
In view of this situation, I recommend adding a signature-independent program that provides archive-like creation and extraction functions (without support for real-time modification), so as to cope with highly targeted scenarios.
yes, no problem. I don't have much social presence so this can be helpful. Thanks.
I start with the performance without encryption: (CRUCIAL P310 1TB NVME GPT ) https://imgur.com/a/68rxOZq Then the performance after the drive encryption using Veracrypt 1.26.20 I have a recent Ryzen 9700X . Veracrypt Benchmark: https://imgur.com/a/oO5LQn0 Encrypted Drive Performance using AES SHA512: https://imgur.com/a/y2j2qAo (Hardware accelerated ????? ) These were the previous system drives encrypted with Veracrypt AND a very old Intel i7 6700k (2014) (SSDs, which should be much slower and are...
Sure, thanks for the heads up. I already knew that with modern SSD/NVMe drives, the CPU makes the difference. In fact, i didn't understand why i was having such a dramatic drop in 4K reads, considering i'm using AES. I have a Ryzen 9700X (over 21Gb/s in decryption performance): https://sourceforge.net/p/veracrypt/discussion/general/thread/843f2e41db/?limit=25#f259 . So i think the integrated Veracrypt benchmark should be offered with 4K performance. Is there a 4k comparison with Diskcriptor ?
Sure, thanks for the heads up. I already knew that with modern SSD/NVMe drives, the CPU makes the difference. In fact, i didn't understand why i was having such a dramatic drop in 4K reads, considering i'm using AES. I have a Ryzen 9700X (over 21Gb/s): https://sourceforge.net/p/veracrypt/discussion/general/thread/843f2e41db/?limit=25#f259 . So i think the integrated Veracrypt benchmark should be offered with 4K performance. Is there a 4k comparison with Diskcriptor ?
I start with the performance without encryption: (CRUCIAL P310 1TB NVME GPT ) https://imgur.com/a/68rxOZq Then the performance after the drive encryption using Veracrypt 1.26.20 I have a recent Ryzen 9700X . Veracrypt Benchmark: https://imgur.com/a/oO5LQn0 Encrypted Drive Performance using AES SHA512: https://imgur.com/XsLgLcb (Hardware accelerated ????? ) These were the previous system drives encrypted with Veracrypt AND a very old Intel i7 6700k (2014) (SSDs, which should be much slower and are...
according to veracrypt benchmark, i should be well within my nvme capabilities, since i used AES. Instead, it's a disaster !
Sure, thanks for the heads up. I already knew that with modern SSD/NVMe drives, the CPU makes the difference. In fact, i didn't understand why i was having such a dramatic drop in 4K reads, considering i'm using AES. I have a Ryzen 9700X (over 21Gb/s): https://sourceforge.net/p/veracrypt/discussion/general/thread/843f2e41db/?limit=25#f259 . So i think the integrated Veracrypt benchmark should be offered with 4K performance. Is there a 4k comparison with Diskcriptor ?
Sure, thanks for the heads up. I already knew that with modern SSD/NVMe drives, the CPU makes the difference. In fact, i didn't understand why i was having such a dramatic drop in 4K reads, considering i'm using AES. I have a Ryzen 9700X (over 21Gb/s). https://sourceforge.net/p/veracrypt/discussion/general/thread/843f2e41db/?limit=25#f259 . So I think the integrated Veracrypt benchmark should be offered with 4K performance.
Would you be OK if I posted this to socials, such as Microsoft's reddit or twitter accounts? Might get some traction.
Hi everyone, I want to share an update following my absence over the past few months. I have encountered some challenges but the most serious one is that Microsoft terminated the account I have used for years to sign Windows drivers and the bootloader. You can see below a screenshot of the message shown when I tried to sign in. Microsoft did not send me any emails or prior warnings. I have received no explanation for the termination and their message indicates that no appeal is possible. I have tried...
Performance drop for any SSD and HDDs should not at all because: SSDs is way faster than HDDs in sequential speeds as well as response times. So, in HDDs, the bottleneck is disk performance all the time. But SSDs sequential speeds is too fast for CPU to handle, so CPU is bottleneck here. CPU is not usually involved in performance tests, but when disk is encrypted by software, SPU is always handling it, so you are limited by CPU speed. AES in my case in VeraCrypt's benchmark is above 20GB/s (I have...
I know i am almost 2 months late, but in the case the disk is still in your hands: What i would do a disk what has similar problems, and i do not care about the data, to get a program, like the HardDiskSentinel, or something similar, what overwrites a sector and reads back the result for "readability quality", let it ran through (at least one overwrite, to hide the previous life). + can force HDD-internal deep-scans Sometimes an "OS-less" check on a drive can force it, to self heal, meaning it starts...
I know i am almost 2 months late, but in the case the disk is still in your hands: What i would do a disk what has similar problems, and i do not care about the data, to get a program, like the HardDiskSentinel, or something similar, what overwrites a sector and reads back the result for "readability quality", let it ran through (at least one overwrite, to hide the previous life). + can force HDD-internal deep-scans Sometimes an "OS-less" check on a drive can force it, to self heal, meaning it starts...
Two files with the same password. File A mounts, the File B gives "incorrect password" etc. Mounted file B a few days ago. Didn't change any password. All other files, each with different passwords, mount successfully. Latest version Veracrypt, 1.26.24. Tried "Restore Volume Header" from internal, did not help. What is wrong?
Возникла проблема с форматированием тома при его создании в Veracrypt в формате NTFS или ExFat. ошибка такая: " Api функция FormatEx в windows не смогла отформатировать том как NTFS/Exfat/ReFS Статус отказа = 0х000000004" и предлагает отформатировать в формате Fat32. Veracrypt версия 1.26.24. Пробовал и на win 10 и на 11, ошибка одинаковая. Антивирус штатный, отключал - результата нет. Подскажите кто сталкивался с такой проблемой? Очень нужен совет как победить эту напасть.
Oh, sorry... I hadn't noticed the hidden icon of the app running in the background that asked me to continue by moving the mouse... So it's good for me. Thanks anyway
Hello, I'm using VeraCrypt 1.26.24 in Windows 11 to encrypt C: of ~ 180Go Yesterday at 12:00 , i would to change my password, but after 21 hours, the windows "Please wait... this process may take a long time... and the system may stop responding" is always displayed : is it normal ? Thanks, and sorry for my bad English... Franck
I've never heard of this program (DiskCriptor). I just re-encrypted 2 disks with veracrypt...after many problems (sigh). Do you think it's better in terms of performance? And in terms of privacy, is it secure ? Unfortunately, performance with Veracrypt drops dramatically. This is the performance of my main NVMe drive before and after encryption with VeraCrypt 1.26.27: before: https://imgur.com/a/l0EFlIV after: https://imgur.com/a/y2j2qAo
I've never heard of this program (DiskCriptor). I just re-encrypted 2 disks with veracrypt...after many problems (sigh). Do you think it's better in terms of performance? And in terms of privacy, is it secure ? Unfortunately, performance with Veracrypt drops dramatically. This is the speed of my main NVMe drive before and after encryption with VeraCrypt 1.26.27: before: https://imgur.com/a/l0EFlIV after: https://imgur.com/a/y2j2qAo
I've never heard of this program (DiskCriptor). I just re-encrypted 2 disks with veracrypt...after many problems (sigh). Do you think it's better in terms of performance? And in terms of privacy, is it secure ? Unfortunately, performance with Veracrypt drops dramatically. This is my main NVMe drive before and after the encryption with veracrypt 1.26.27: before: https://imgur.com/a/l0EFlIV after: https://imgur.com/a/y2j2qAo
Bonjour, Je possède un disque dur externe Verbatin dans lequel j'ai installé VeraCrypt. Au sein de VeraCrypt j'ai crypté plusieurs fichiers docs, JPEG, etc.... Ma question est : comment dois-je procvéder pour supprimer VeraCrypt de mon disque dur externe tout en gardant mes fichiers lisibles alors en clair. Je vous remercie de vos réponses exprimées , si possible, en gfrançais.
Not only EXOS are affected. Different brands, different results. But all have common behavior. If bigger, it's slower. Veracrypt bad write speeds and DiskCryptor writes as unencrypted. Test was CrystalDiskMark v8.0.4 x64 and 8GiB, SEQ1M-Q8T1. I tested 7 random disks I have with different capacities and brands and it looks like VC issue starting at 4TB disks. !SEAGATE EXOS X16, 16TB speed DC 225MB/s, VC 50MB/s (80 with newest FW) !SEAGATE EXOS 7E8, 8TB speed DC 200MB/s, VC 50MB/s !WD model WD40EFRX,...
Hello, currently it is only possible to mount devices in Linux by using block device files like /dev/sdb2. But these files tend to change after reboot, so /dev/sdb2 might become /dev/sda2 after a reboot, which makes it impossible to use these paths as favorite volumes in the GUI. Please make it possible to also use links from the /dev/disk/by-id directory, which tend to be stable.
chatgpt is right, you need to have two separate EFI partitions. https://sourceforge.net/p/veracrypt/discussion/general/thread/3ce5b46bb6/
There are 3 main methods to achieve the goal. 1) full disk encryption (not recommended; Disk not recognized, accidental overwriting by Windows, dual boot/Linux issues, etc.) 2) physical disconnection (dismounting everything may be complicated/difficult, especially with NVMe heatsinks with thermal pads) 3)Deleting/Restoring partitions (disk wipe) Another method is to disable NVMe drives directly from the BIOS (only a few manufacturers offer this option, such as Alienware) or disable the PCIe lanes...
There are 3 main methods to achieve the goal. 1) full disk encryption (not recommended; Disk not recognized, accidental overwriting by Windows, dual boot/Linux issues, etc.) 2) physical disconnection (dismounting everything may be complicated/difficult, especially with NVMe heatsinks with thermal pads) 3)Deleting/Restoring partitions (disk wipe) Another method is to disable NVMe drives directly from the BIOS (only a few manufacturers offer this option, such as Alienware) or disable the PCIe lanes...
There are 3 main methods to achieve the goal. 1) full disk encryption (not recommended; Disk not recognized, accidental overwriting by Windows, dual boot/Linux issues, etc.) 2) physical disconnection (dismounting everything may be complicated/difficult, especially with NVMe heatsinks with thermal pads) 3)Deleting/Restoring partitions (disk wipe) Another method is to disable NVMe drives directly from the BIOS (only a few manufacturers offer this option, such as Alienware) or disable the PCIe lanes...
There are 3 main methods to achieve the goal. 1) full disk encryption (not recommended; Disk not recognized, accidental overwriting by Windows, dual boot/Linux issues, etc.) 2) physical disconnection (dismounting everything may be complicated/difficult, especially with NVMe heatsinks with thermal pads) 3)Deleting/Restoring partitions (disk wipe) Another method is to disable NVMe drives directly from the BIOS (only a few manufacturers offer this option, such as Alienware) or disable the PCIe lanes...
There are 3 main methods to achieve the goal. 1) full disk encryption (not recommended; Disk not recognized, accidental overwriting by Windows, dual boot/Linux issues, etc.) 2) physical disconnection (dismounting everything may be complicated/difficult, especially with NVMe heatsinks with thermal pads) 3)Deleting/Restoring partitions (disk wipe) There's also another method, which is to disable NVMe drives directly from the BIOS (only few manufacturers have this option, e.g., Alienware) or the PCIe...
There are 3 main methods to achieve the goal. 1) full disk encryption (not recommended; Disk not recognized, accidental overwriting by Windows, dual boot/Linux issues, etc.) 2) physical disconnection (dismounting everything may be complicated/difficult, especially with NVMe heatsinks with thermal pads) 3)Deleting/Restoring partitions (wipe disk) There's also another method, which is to disable NVMe drives directly from the BIOS (only few manufacturers have this option, e.g., Alienware) or the PCIe...
There are 3 main methods to achieve the goal. 1) full disk encryption (not recommended; Disk not recognized, accidental overwriting by Windows, dual boot/Linux issues, etc.) 2) physical disconnection(dismounting everything may be complicated/difficult, especially with NVMe heatsinks with thermal pads) 3)Delete/Restore Partitions (Full disk erase) There's also another method, which is to disable NVMe drives directly from the BIOS (only few manufacturers have this option, e.g., Alienware) or the PCIe...
There are 3 main methods to achieve the goal. 1) full disk encryption (not recommended; Disk not recognized, accidental overwriting by Windows, dual boot/Linux issues, etc.) 2) physical disconnection (It might be annoying/inaccessible to disassemble everything again, especially with nvme heatsinks with thermal pads.) 3)Delete/Restore Partitions (Full disk erase) There's also another method, which is to disable NVMe drives directly from the BIOS (only few manufacturers have this option, e.g., Alienware)...
There are 3 main methods to achieve the goal. 1) full disk encryption (not recommended; Disk not recognized, accidental overwriting by Windows, Dual boot/Linux problems... ) 2) physical disconnection (It might be annoying/inaccessible to disassemble everything again, especially with nvme heatsinks with thermal pads.) 3)Delete/Restore Partitions (Full disk erase) There's also another method, which is to disable NVMe drives directly from the BIOS (only few manufacturers have this option, e.g., Alienware)...
There are 3 main methods to achieve the goal. 1) full disk encryption (not recommended; Disk not recognized, accidental overwriting by Windows, Dual boot/Linux problems... ) 2) physical disconnection (It might be annoying/inaccessible to disassemble everything again, especially with nvme heatsinks with thermal pads.) 3)Delete/Restore Partitions (Full disk erase) There's also another method, which is to disable NVMe drives directly from the BIOS (only few manufacturers have this option, e.g., Alienware)...
What i'd like to do is completely separate the two disks and disable dual boot. I'll choose which disk to boot via BIOS/UEFI. What should i do ? I know i need to modify the EFI partitions somehow, but how ? I finally solved the problem (there are more solutions). Here's how:
What i'd like to do is completely separate the two disks and disable dual boot. I'll choose which disk to boot via BIOS/UEFI. What should i do ? I know i need to modify the EFI partitions somehow, but how ? I finally solved the problem (there are more solutions).
What i'd like to do is completely separate the two disks and disable dual boot. I'll choose which disk to boot via BIOS/UEFI. What should i do ? I know i need to modify the EFI partitions somehow, but how ? I solved the problem (there are more solutions).
I have now a better understanding of it. This happens because the two systems are booted from the same EFI partition, which also contains the VeraCrypt bootloader, which has priority and cannot be circumvented.
I don't remember if the entire NVMe drive is encrypted or just the system partition (C:). [Edit] Correction, only the system partition C:.
i dont remember if the entire NVMe drive is encrypted or only the system partition (C:) . [edit] I correct myself, only the system C: partition.
I have now a better understanding of it. This happens because the two systems are booted into the same EFI partition, which also contains the VeraCrypt bootloader, which has priority and cannot be circumvented.
Hi again, Please let me know if it is possible to decrypt the files or should I move forwards ? Thank you
Hi, I had a USB key with a standard veracrypt volume on it. I have a copy of the encrypted fjles on my machine. The thing is I am not able to decrypt the container as it is not on the original USB drive anymore as the USB key has been corrupted with the time. Is there a way to decrypt it differently ? I have the decryption password. Thank you for your help
Hi, I had a USB key with a standard veracrypt volume on it. I have a copy of the encrypted fjles on my machine. The thing is I able not able to decrypt the container as it is not on the original USB drive anymore as the USB key has been corrupted with the time. Is there a way to decrypt it differently ? I have the decryption password. Thank you for your help
Now I'd like to understand how you folks use Veracrypt, because it's unthinkable to use a program like this without also using some kind of disk imaging program. So, every time you restore a disk image (and this image isn't encrypted because there are no imaging programs that support Veracrypt), the Veracrypt bootloader is still causing problems? Can you explain to me how the developer thinks this problem should be handled ?
Now I'd like to understand how you folks use Veracrypt, because it's unthinkable to use a program like this without also using some kind of disk imaging program. So, every time you restore a disk image, and this image isn't encrypted because there are no imaging programs that support Veracrypt, the Veracrypt bootloader is still causing problems? Can you explain to me how the developer thinks this problem should be handled ?
Maybe I forgot to mention that once the encrypted partition is deleted/restored without being decrypted first, and the VeraCrypt bootloader remains in the EFI partition, it cannot be removed even via the Rescue Disk's boot menu. https://imgur.com/a/85FpnSX z) Remove Veracrypt loader from boot menu , the selection is ignored and nothing happens.
Maybe I forgot to mention that once the encrypted partition is deleted without being decrypted first, and the VeraCrypt bootloader remains in the EFI partition, it cannot be removed even via the Rescue Disk's boot menu. https://imgur.com/a/85FpnSX z) Remove Veracrypt loader from boot menu , the selection is ignored and nothing happens.
Maybe I forgot to mention that once the encrypted partition is deleted, and the VeraCrypt bootloader remains in the EFI partition, it cannot be removed even via the Rescue Disk's boot menu. https://imgur.com/a/85FpnSX z) Remove Veracrypt loader from boot menu , the selection is ignored and nothing happens.
How to check the EUI-64 provided by the VeraCrypt Rescue Disk: Reboot using the USB flash drive with the Rescue Disk, select "d" - "Decrypt OS", then a list of disks appears. Type N if you just want to exit.
(version 1.26.27) I tried to decrypt the OS disk using the rescue disk, but I was afraid that it would select the wrong hard disk (I have 3 encrypted disks including the OS disk), so I rebooted to check from inside Windows11 (25H2) if the number was correct, and it wasn't !!!!! RescueDisk EUI-64 is something like (not my real number): 32-8A-50-4C-01-85-A0-00 , while Windows11 EUI-64 ( Powershell command: Get-CimInstance -Namespace root\Microsoft\Windows\Storage -ClassName MSFT_PhysicalDisk | Select-Object...
(version 1.26.27) I tried to decrypt the OS disk using the rescue disk, but I was afraid that it would select the wrong hard disk (I have 3 encrypted disks including the OS disk), so I rebooted to check from inside Windows11 (25H2) if the number was correct, and it wasn't !!!!! RescueDisk EUI-64 is something like (not my real number): 32-8A-50-4C-01-85-A0-00 , while Windows11 EUI-64 (Get-CimInstance -Namespace root\Microsoft\Windows\Storage -ClassName MSFT_PhysicalDisk | Select-Object FriendlyName,...
Cause of the problem is found: this stupid W11 had decided to mount a shared folder of my NAS as "Y" in the Windows Explorer. I don't why, but W11 did it alone... (maybe during the crash ?). So I have disconnected "Y" from the Windows Explorer, and therefore Veracrypt immediatly presents "Y" as a letter for the crypted folder. consequently: problem solved. Thanks.
Veracrypt has been always perfect, but since a serious crash of my PC this afternoon, the letter "Y" that I normally use to mount a crypted folder has disappeared from the letters list : see the attached screen capture. Veracrypt still works fine if choose another letter, "T" for example, but letter after "X" can be selected from the list. How to fix it ??? Thank you
Veracrypt 1.26.24 installs an app indicator on ubuntu24's top bar. Can this be made optional? (My bar is too crowded).
Yes, there are backup files in that folder and others, BUT I think I've figured out the main problem. Veracrypt writes files to the EFI partition and the UEFI NVRAM. If you delete the partition or disk WITHOUT decrypting it first (i suppose), the BIOS/UEFI NVRAM simply remains intact. If you then rewrite/delete the partitions as i did, you also have to go into the BIOS/UEFI and save the configuration with F10. In fact, even using BOOTICE from inside Windows11, the UEFI values still showed a Veracrypt...
Yes, there are backup files in that folder and others, BUT I think I've figured out the main problem. Veracrypt writes files to the EFI partition and the UEFI NVRAM. If you delete the partition or disk WITHOUT decrypting it first (i suppose), the BIOS/UEFI NVRAM simply remains intact. If you then delete the partitions as I did, you also have to go into the BIOS/UEFI and save the configuration with F10. In fact, even using BOOTICE from inside Windows11, the UEFI values still showed a Veracrypt entry...
Yes, there are backup files in that folder and others, BUT I think I've figured out the main problem. Veracrypt writes files to the EFI partition and the UEFI NVRAM. If you delete the partition or disk WITHOUT decrypting it first (i suppose), the BIOS/UEFI NVRAM simply remains intact. If you then modify the partitions as I did, you also have to go into the BIOS/UEFI and save the configuration with F10. In fact, even using BOOTICE from inside Windows11, the UEFI values still showed a Veracrypt entry...
Yes, there are backup files in that folder and others, BUT I think I've figured out the main problem. Veracrypt writes files to the EFI partition and the UEFI NVRAM. If you delete the partition or disk WITHOUT decrypting first (i suppose), the BIOS/UEFI NVRAM simply remains intact. If you then modify the partitions as I did, you also have to go into the BIOS/UEFI and save the configuration with F10. In fact, even using BOOTICE from inside Windows11, the UEFI values still showed a Veracrypt entry...
Yes, there are backup files in that folder and others, BUT I think I've figured out the main problem. Veracrypt writes files to the EFI partition and the UEFI NVRAM. If you delete the partition or disk WITHOUT decrypting first (i suppose), the BIOS/UEFI NVRAM simply remains intact. If you then modify the partitions as I did, you also have to go into the BIOS/UEFI and save the configuration with F10. In fact, even using BOOTICE from inside Windows11, the UEFI values still showed a Veracrypt entry...
Hello! I created an encrypted system partition (win10) in a SSD. This partition uses only a third of my SSD space and the rest is left blank and without a file system. I installed windows and proceeded with encryption through VeraCrypt, only the system partition, not the whole drive. I run Mint on another drive ( an HDD) and VeraCrypt in GUI mode inside it. No matter what I do the linux version seems unable to decrypt the windows system encrypted partition, even if all partitions are correctly listed...
Using your browser search feature on the Release Notes to search for the term "bootloader", you will find references to enhancements to fix the VeraCrypt bootloader during MS OS upgrades and fix the missing VeraCrypt bootloader. Maybe the copies of the original MS and VeraCrypt bootloaders are stored in the %ALLUSERSPROFILE%\VeraCrypt\ directory. https://veracrypt.jp/en/VeraCrypt%20System%20Files.html
Using your browser search feature on the Release Notes to search for the term "bootloader", you will find references to enhancements to fix the VeraCrypt bootloader during MS OS upgrades and fix the missing VeraCrypt bootloader. Maybe the copies of the original MS and VeraCrypt bootloaders are stored in the folder %ALLUSERSPROFILE%\VeraCrypt\ directory. https://veracrypt.jp/en/VeraCrypt%20System%20Files.html
Using your browser search feature on the Release Notes to search the term "bootloader", you will find references to enhancements to fix the VeraCrypt bootloader during MS OS upgrades and fix the missing VeraCrypt bootloader. Maybe the copies of the original MS and VeraCrypt bootloaders are stored in the folder %ALLUSERSPROFILE%\VeraCrypt\ directory. https://veracrypt.jp/en/VeraCrypt%20System%20Files.html
Using your browser search feature on the Release Notes to search term "bootloader", you will find references to enhancements to fix the VeraCrypt bootloader during MS OS upgrades or replace the missing VeraCrypt bootloader. Maybe the copies of the original MS and VeraCrypt bootloaders are stored in the folder %ALLUSERSPROFILE%\VeraCrypt\ directory. https://veracrypt.jp/en/VeraCrypt%20System%20Files.html
Using your browser search feature on the Release Notes using the search term "bootloader", you will find references to enhancements to fix the VeraCrypt bootloader during MS OS upgrades or replace the missing VeraCrypt bootloader. Maybe the copies of the original MS and VeraCrypt bootloaders are stored in the folder %ALLUSERSPROFILE%\VeraCrypt\ directory. https://veracrypt.jp/en/VeraCrypt%20System%20Files.html
Using your browser search feature on the Release Notes using the search term "bootloader", you will find references to enhancements to fix the VeraCrypt bootloader or replace the missing VeraCrypt bootloader. Maybe the copies of the original MS and VeraCrypt bootloaders are stored in the folder %ALLUSERSPROFILE%\VeraCrypt\ directory. https://veracrypt.jp/en/VeraCrypt%20System%20Files.html
Using your browser search feature on the Release Notes using the search term "bootloader", you will find references to enhancements to fix the VeraCrypt bootloader or replace the missing VeraCrypt bootloader. Maybe stored in the folder %ALLUSERSPROFILE%\VeraCrypt\ directory. https://veracrypt.jp/en/VeraCrypt%20System%20Files.html
Using your browser search feature on the Release Notes using the search term "bootloader", you will find references to enhancements to fix the VeraCrypt bootloader or replace the missing VeraCrypt bootloader. Maybe stored in n the folder %ALLUSERSPROFILE%\VeraCrypt\ directory. https://veracrypt.jp/en/VeraCrypt%20System%20Files.html
Long story short, due to a failed update, I deleted the Veracrypt encrypted partition, so I restored a previous disk image (1 month ago). I used Paragon Hard Disk Manager. The system works fine. Obviously, I lost file encryption because the image is created from within Windows, and Paragon doesn't support Veracrypt. So every time I restore an image of my system, I also have to re-encrypt everything (but that's another story). Of course, the old disk image also contained the EFI partition with the...
The fundamental problem for me is understanding why a completely clean EFI partition was rewritten by the Veracrypt bootloader, how is this possible ? Veracrypt 1.26.20 had already been uninstalled from the system by that point. Really, guys, how is this possible ? Does Veracrypt create hidden backups somewhere?
The fundamental problem for me is understanding why a completely clean EFI partition was rewritten by the Veracrypt bootloader, how is this possible ? Really, guys, how is this possible ? Does Veracrypt create hidden backups somewhere?
Yes, 1.26.20. Thanks for the reply, I had already tried that, before deleting and recreating the EFI partition from scratch. This doesn't work, simply because Veracrypt sends this message (and it's right).: "the system partition/drive does not appear to be encrypted" https://imgur.com/a/JUf4FR2 I didn't want to make it long in the first post, but right after I also tried to use the rescue disk to decrypt the partition (which obviously wasn't encrypted anymore), just to see if it removed the bootloader,...
Yes, 1.26.20. Thanks for the reply, I had already tried that, before deleting and recreating the EFI partition from scratch. This doesn't work, simply because Veracrypt sends this message (and it's right).: "the system partition/drive does not appear to be encrypted" https://imgur.com/a/JUf4FR2
Yes, 1.26.20. Thanks for the reply, I had already tried that, before deleting and recreating the EFI partition from scratch. This doesn't work, simply because Veracrypt sends this message (and it's right).: "the system partition/drive does not appear to be encrypted" https://imgur.com/a/JUf4FR2
Yes, 1.26.20. Thanks for the reply, I had already tried that, before deleting and recreating the EFI partition from scratch. This doesn't work, simply because Veracrypt sends this message (and it's right).: "the system partition/drive does not appear to be encrypted" https://imgur.com/a/JUf4FR2
Yes, 1.26.20. Thanks for the reply, I had already tried that, before deleting and recreating the EFI partition from scratch. This doesn't work, simply because Veracrypt sends this message (and it's right).: "the system partition/drive does not appear to be encrypted" https://imgur.com/a/JUf4FR2