Activity for standard user
-
standard user posted a comment on discussion General Discussion
I just checked. I'm on Windows 11 25H2. The March 2026 Update (KB5086672) replaced the file \efi\microsoft\boot\bootmgfw.efi .
-
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 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.
-
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
-
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.
-
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,...
-
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...
-
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
-
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...
-
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...
-
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...
-
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...
-
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...
-
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...
-
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...
-
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...
-
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...
-
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. Of course, the old disk image also contained the EFI partition with the Veracrypt bootloader, which now starts and asks me for my password and PIM, but it's useless, so I press ESC and continue to unencrypted Windows 11. So, I want to remove the annoying Veracrypt boot,...
-
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. Of course, the old disk image also contained the EFI partition with the Veracrypt bootloader, which now starts and asks me for my password and PIM, but it's useless, so I press ESC and continue to unencrypted Windows 11. So, I want to remove the annoying Veracrypt boot,...
-
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. Of course, the old disk image also contained the EFI partition with the Veracrypt bootloader, which now starts and asks me for my password and PIM, but it's useless, so I press ESC and continue to unencrypted Windows 11. So, I want to remove the annoying Veracrypt boot,...
-
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. Of course, the old disk image also contained the EFI partition with the Veracrypt bootloader, which now starts and asks me for my password and PIM, but it's useless, so I press ESC and continue to unencrypted Windows 11. So, I want to remove the annoying Veracrypt boot,...
-
Maybe i should post my questions on Reddit ? Because this seems like a dead forum to me.
-
Maybe I should move this thread to Reddit ? Because this seems like a dead forum to me.
-
Maybe I should move this thread to Reddit ? Because it seems like a dead forum to me.
-
There is an interesting discussion here, though, in hindsight, not conclusive: https://forums.tomshardware.com/threads/can-i-disable-nvme-slot.3752830/#post-22629795 In my opinion the best answer is dwd999's. The method I use for this relies on having sufficient external storage to store an image of the nvme drive: I use the free Macrium software to image the nvme drive onto a usb drive; I then use Gparted to delete all of the partitions on the nvme drive so that it is totally unallocated; then I...
-
There is an interesting discussion here, though, in hindsight, not conclusive: https://forums.tomshardware.com/threads/can-i-disable-nvme-slot.3752830/#post-22629795 In my opinion the best answer is dwd999's. The method I use for this relies on having sufficient external storage to store an image of the nvme drive: I use the free Macrium software to image the nvme drive onto a usb drive; I then use Gparted to delete all of the partitions on the nvme drive so that it is totally unallocated; then I...
-
This is an interesting discussion, although not conclusive in hindsight. https://forums.tomshardware.com/threads/can-i-disable-nvme-slot.3752830/#post-22629795 In my opinion the best answer is dwd999's. The method I use for this relies on having sufficient external storage to store an image of the nvme drive: I use the free Macrium software to image the nvme drive onto a usb drive; I then use Gparted to delete all of the partitions on the nvme drive so that it is totally unallocated; then I install...
-
i dont remember if the entire NVMe drive is encrypted or only the system partition (C:) . How do i check it ?
-
what to do now ? I have a veracrypt (1.26.20) system partition on NVME disk (Win11 Pro 24H2). The entire drive is encrypted and i boot with a password and PIM. It was all ok until i decided to install a new fresh Windows 11 on another SSD (Win11 Home 24H2) . Now let me explain what's happening: since i know Windows is a lame system, i USUALLY disconnect all other hard drives when i install Windows on a new drive, because i don't want Windows to modify existing partitions. I then boot the drives separately...
-
what to do now ? I have a veracrypt (1.26.20) system partition on NVME disk (Win11 Pro 24H2). The entire drive is encrypted and i boot with a password and PIM. It was all ok until i decided to install a new fresh Windows 11 on another SSD (Win11 Home 24H2) . Now let me explain what's happening: since i know Windows is a lame system, i USUALLY disconnect all other hard drives when i install Windows on a new drive, because i don't want Windows to modify existing partitions. I then boot the drives separately...
-
what to do now ? I have a veracrypt (1.26.20) system partition on NVME disk (Win11 Pro 24H2). The entire drive is encrypted and i boot with a password and PIM. It was all ok until i decided to install a new fresh Windows 11 on another SSD (Win11 Home 24H2) . Now let me explain what's happening: since i know Windows is a lame system, i USUALLY disconnect all other hard drives when i install Windows on a new drive, because i don't want Windows to modify existing partitions. I then boot the drives separately...
-
what to do now ? I have a veracrypt (1.26.20) system partition on NVME disk (Win11 Pro 24H2). The entire drive is encrypted and i boot with a password and PIM. It was all ok until i decided to install a new fresh Windows 11 on another SSD (Win11 Home 24H2) . Now let me explain what's happening: since i know Windows is a lame system, i USUALLY disconnect all other hard drives when i install Windows on a new drive, because i don't want Windows to modify existing partitions. I then boot the drives separately...
-
what to do now ? I have a veracrypt (1.26.20) system partition on NVME disk (Win11 Pro 24H2). The entire drive is encrypted and i boot with a password and PIM. It was all ok until i decided to install a new fresh Windows 11 on another SSD (Win11 Home 24H2) . Now let me explain what's happening: since i know Windows is a lame system, i USUALLY disconnect all other hard drives when i install Windows on a new drive, because i don't want Windows to modify existing partitions. I then boot the drives separately...
-
what to do now ? I have a veracrypt (1.26.20) system partition on NVME disk (Win11 Pro 24H2). The entire drive is encrypted and i boot with a password and PIM. It was all ok until i decided to install a new fresh Windows 11 on another SSD (Win11 Home 24H2) . Now let me explain what's happening: since i know Windows is a lame system, i USUALLY disconnect all other hard drives when i install Windows on a new drive, because i don't want Windows to modify existing partitions. I then boot the drives separately...
-
how do you gain access to the EFi partitions to adjust UEFI boot entries ? https://sourceforge.net/p/veracrypt/discussion/general/thread/3ce5b46bb6/
-
what to do now ? I have a veracrypt (1.26.20) system partition on NVME disk (Win11 Pro 24H2). The entire drive is encrypted and i boot with a password and PIM. It was all ok until i decided to install a new fresh Windows 11 on another SSD (Win11 Home 24H2) . Now let me explain what's happening: since i know Windows is a lame system, i USUALLY disconnect all other hard drives when i install Windows on a new drive, because i don't want Windows to modify existing partitions. I then boot the drives separately...
-
how do you gain access to the EFi partitions to adjust UEFI boot entries ?
-
same problem for me, and it's been happening very recently. It's not the indexing service which i have already disabled. I have also Process Explorer installed, but how you determine which files are currently used or what is accessing the mounted volume ?
-
same problem for me, and it's been happening very recently. It's not the indexing service which i have already disabled. I have also Process Explorer installed, but how do you determine what files are opened or what is accessing the mounted volume ?
-
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...
-
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/L5TBsJr (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...
-
I have been using veracrypt since its first releases after truecrypt development was abruptly discontinued. BUT Veracrypt makes a modern system slow and problematic. It is not a program designed to work with modern hardware. If I have to renounce to all the performance gains of a modern system, then there is no point in using this program anymore. I'm very sad.
-
I have been using veracrypt since its first releases after truecrypt development was abruptly discontinued. BUT Veracrypt makes a modern system slow and problematic. It is not a program designed to work with a modern hardware. If I have to renounce to all the performance gains of a modern system, then there is no point in using this program anymore. I'm very sad.
-
I have been using veracrypt since its first releases after truecrypt development was abruptly discontinued. BUT Veracypt makes a modern system slow and problematic. It is not a program designed to work with a modern hardware. If I have to renounce to all the performance gains of a modern system, then there is no point in using this program anymore. I'm very sad.
-
same problem for me, and it's been happening very recently. It's not the indexing service which i have already disabled. I have also Process Explorer installed, but how do you determine what files are open or what is accessing the mounted volume ?
-
according to veracrypt benchmark, i should be well within my nvme capabilities, since i used AES. Instead, it's a disaster ! p.s. Inserting images is a total mess. "Insert Image" doesn't work, and clicking on links takes you away from the current page instead of opening a new one.
-
according to veracrypt benchmark, i should be well within my nvme capabilities, since i used AES. Instead, it's a disaster ! p.s. Inserting images is a total disaster. "Insert Image" doesn't work, and clicking on links takes you away from the current page instead of opening a new one.
-
according to veracrypt benchmark, i should be well within my nvme capabilities, since i used AES. And instead it's a disaster! p.s. Inserting images is a total disaster. "Insert Image" doesn't work, and clicking on links takes you away from the current page instead of opening a new one.
-
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/ZE9hJW9 (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...
-
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/ZE9hJW9 (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...
-
p.s. Inserting images is a total disaster. "Insert Image" doesn't work, and clicking on links takes you away from the current page instead of opening a new one.
-
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/ZE9hJW9 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 very close to nvme instead...
1 >
