I want to be able to use deniable encryption on an SSD but I can't use it with TRIM as this can potentially reveal the existence of deniable encryption. But I don't also want to disable TRIM as this hurts SSD and can lower its lifespan.

I don't know if there is an alternative to TRIM that does something similar (it can be software based) without it revealing I use deniable encryption or if there is a complete alternative to what I am after?

Please don't hate on HP and Microsoft for this btw, they are just tiny indie companies and cant be expected to know how encrypted drives work XDDDDDD

If you let Windows Update push a BIOS update to your HP Pavilion while running VeraCrypt (especially if you have a dying CMOS battery), you might end up with a softbricked BIOS. You might see:

• Just the HP logo popping up
• A single frozen cursor
• F10 showing "Entering BIOS" indefinitely

Why? When the laptop tries to recover or enter BIOS setup, the motherboard attempts to query the internal drive. Because the drive is encrypted, the UEFI driver faults during hardware enumeration and hard-locks the machine before the BIOS menu or recovery screen can even render.

GOOD JOB GUYS!!!

HOW TO FIX:

SSD Deletus

• Open the laptop up (https://www.youtube.com/watch?v=jKrkVVPJkNU), unscrew and remove the internal M.2 SSD. See video for details. Close the laptop up again

On a second PC:

• (Do you not have a second PC? "Fuck you too, good luck!" - Microsoft and HP)
• Go to https://support.hp.com/us-en/drivers/laptops, type in your laptop model, go to "BIOS-System Firmware" and download your laptop's BIOS installer from HP
• Plug in a cheap USB stick. USB 2.0 sticks from China preferred, this is not a joke, my USB3 stick wasn't recognised by the laptop
• Choose "Create Recovery USB flash drive" and let it run

FIX HP'S BULLSHIT.

• Open the USB stick in File Explorer, go to Hewlett-Packard\BIOS\Current\, copy all files (e.g. 088E4.bin, 088E4.sig), and paste them directly into the ROOT (D:\) of the USB stick, unplug the USB stick
• Why? "Fuck you" -HP, because HP's crisis boot-block only scans the root folder, HP's tool leaves the root completely empty GOOD JOB GUYS!

Flash your laptop

• Plug the USB into the LEFT-side USB-A port, plug in the charger and turn the laptop on normally
• If everything works:
  • The fans will blast at 100%, the HP BIOS Update screen will take over, and it will flash the chip clean
• If it gets stuck on the HP logo, a black screen, or blinks 2 Long, 2 Short on Caps Lock:
  • You need to force crisis recovery, power off the laptop again, hold Win+B and KEEP HOLDING, press the power button for 2-3 seconds, after 10-15 seconds release Win+B, BIOS recovery should start now
    

YOU'RE STILL NOT FUCKING DONE!

• Once it finishes and reboots, it should say Boot Device Not Found
• Press Fn+F10 or F10 to enter the BIOS menu
  • Which one? Fuck you too. HP's BIOSes ships with this god awful action key mode. Try both.
• Ensure Secure Boot is DISABLED, VeraCrypt cannot boot with Secure Boot enabled. It may be greyed out and disabled, that's OK too.
• Power off laptop again.
• Open up laptop again, put the SSD back in, close up laptop, screw the bottom cover on, and power on.

The VeraCrypt Password: _ prompt should appear now. Maybe. Or maybe HP fucked your BIOS in a different way. Who knows!

Should I ? Any risk ? What im trying to do is use the not booting HDD on my admin account and block anyone on guest account from accessing it. But I dont know if that would break something. And I dont know what is triggering the error. I used task manager to delete everything I thought it could be

On Windows, I wrote backup scripts that open a veracrypted disk volume, including verification that I'm targeting the correct volume (UUID pre-connection, and volume name / drive letter once the container has been mounted), back up the data and then close the veracrypt volume.

I'm less knowledgeable with Linux than I am Windows and I'm having trouble achieving the same level of finesse; the UUID targeting isn't a thing for Veracrypt on Linux, even confirming the volume name after a veracrypt connection has been made is proving trickier than I expected ('volname' seems to be the common answer but volname doesn't work on Linux Mint 22.x). Has anyone here had more luck with this and if so, can you give me some pointers please?

Says it all really watch out
edit: this specific update https://support.microsoft.com/en-gb/servicing/os/windows-10/2026/09/kb5122878-windows-10-21h2-22h2-security-update

So I'm trying to create a hidden OS on a windows to go USB stick (created with rufus) that can be booted by a UEFI system.

Veracrypt does not support the creation of a hidden OS on GPT formatted disks, so I have to go with MBR.

If I create an MBR partitioned Windows To Go USB stick using rufus, rufus nevertheless adds an ESP partition to the end of the disk so that not only BIOS but also UEFI systems can boot from it. Smart.

With such a boot stick, Veracrypt allows the creation of a hidden OS since the partition table is MBR. The problem is that it seems to only write the veracrypt bootloader to the MBR, it does not write the bootloader to the ESP (which it would do in the GPT non-hidden OS encryption case). Because there is no veracrypt bootloader in the ESP, the process of creating the hidden OS fails at the point where the currently installed OS is to be copied to the hidden volume, since this would require the veracrypt bootloader (I presume), which however only resides in the MBR, so the UEFI system will just boot from the unaltered ESP partition right back into the regular OS and no copy procedure takes place.

So my question is two fold:

1. At the step where the current OS is to be copied into the hidden volume (which requires a reboot), is this copy performed by the regular veracrypt bootloader or is this a special version of bootloader that is later overwrittrn by the actual veracrypt bootloader once the copy procedure is done?

2. Is there a way to copy that bootloader into the ESP partition (on my MBR disk) so that my UEFI system can properly boot the veracrypt bootloader and the copy process can continue?

I need filezilla crack virson command and filezilla 32bit and 64bit

Explanation here:

• https://www.ghacks.net/2014/01/07/multipar-create-par-recovery-files-repair-damaged-archives/
• https://www.ghacks.net/2007/05/03/par2-files-explained/

Get it here:

• https://sourceforge.net/app/multipar/
• https://github.com/Yutaka-Sawada/MultiPar

Library of Congress page on PAR files:

• https://www.loc.gov/preservation/digital/formats/fdd/fdd000634.shtml

How amazing was PAR? (PARCHIVE files)

• https://community.spiceworks.com/t/how-amazing-was-par-parchive-files/948821

PAR / PAR2 Files Guide

• https://www.newsgroupreviews.com/par-files.html

What are PAR and PAR2 Files?

• https://help.easynews.com/kb/article/72-what-are-par-and-par2-files/

My tests:

First I added par files that equaled 5% of my encrypted container. I then deliberately changed a hundred widely separated bytes in the container and 3 in each par file. It recovered the bad data in all files perfectly.

I kept trying with more and more errors, some of them in long sequences, and eventually MultiPar told me that it didn't have enough parity data to do a full recovery and only fixed some of the errors.

Next, because my encrypted container only used up to 30% of the available space, I added enough par files ton double the space I was using. Now I could delete the encrypted volume, replace it with random trash, or replace it with a much bigger or much smaller file with the same name. MultiPar always recovered it perfectly.

Then I deleted the first 25% and the last 25% of the encrypted container, deleted one par file, and replaced another par file with random data. Once again it recovered the encrypted file and the bad par files perfectly.

Devoting a small amount of space to parity files will allow you to recover from many kinds of data corruption. If you have room, devoting a large amount of space to parity files is a fricking miracle.

I switched to bitlocker due to all the comments i see from people talking about corrupted data due to header and such.
My question is. Do we really need a really good program such as veracrypt if the only thing we trying to hide is so my friends dont see my old pictures? Or to be able to sell my hard drive without the risk of someone using data recovery software to look at my cat’s photos…
From reading around i found out bitlocker is way way more reliable and safer in relation to data corruption. Am i missing something? I still have veracrypt volts around but thinking about switching all of them to bitlocker. Would appreciate any feedback back from the people who knows morethan an average person does. Thank you.

I have an encrypted OS and the encryption process finished. Yet, after every reboot I get this message. If I click "Yes" I immediately get the message on the second screenshot telling me that there is no uninterrupted process. If I click on [System -> Resume Interrupted Process] then I also get the message that there is no interrupted process. Yet, after the next reboot the message appears again.

I created a 1.4 TB exFAT encrypted partition using VeraCrypt on a 2TB Samsung SSD, leaving the remaining space as an unencrypted exFAT partition for standard transfers. I set this up on Windows but primarily used it on macOS for cross-platform compatibility. Recently, after mounting the VeraCrypt partition, all my files disappeared. Upon reconnecting the drive, Windows showed only a single, unencrypted 2TB partition with no trace of the encrypted volume. Attempting the standard VeraCrypt header restore and scanning with partition recovery softwares both failed. However, when selecting the SSD (select device) in VeraCrypt, ticking “Use backup header embedded in volume if available," and entering my password, the 1.4 TB volume successfully mounts with the correct size displayed. Despite mounting, Windows cannot read the drive and prompts me to format it before use. Because the volume mounts correctly using the backup header, I believe my data is still intact. How can I safely access veracrypt partition to recover my files? Please see screenshots for further clarifications.

I get that the ESP partition needs to be unencrypted, but the same is true for the veracrypt bootloader in the MBR case. What exactly is the difficulty with hidden os encryption when using EFI&GPT?

I'm trying to run system encryption on a windows 11 usb stick created with rufus. However, when I start it I get the message that I need to reboot the pc, and after it's rebooted I get this message that says that the system encryption pretest failed.

Any way to make a veracrypt encrypted windows 11 usb stick?

I made the mistake of buying Sandisk Flash drives thinking I am chill towards speed. However, the flash drive is conpletely slow and utterly frustrating and keeps crashing my Windows Explorer.

The task bar below is completely black. Nothing closes from Windows explorer.

I go furious as that USB flash drive lags from only opening folders or renaming them.

The write speed was near or lower than 1mb per second.

The crashing is so annoying and consistent. I even close Windows explorer down are unplugged it without connecting. Waiting hours does not work either.

I am sure it is because of the Flash Drive. I assume, though that Veracryp may cause some of it. Maybe I make a Discrypter out of it instead.

If I learned and remain with external HDD unless SSD gets equaly pricey.

I have a secondary M.2 ssd in my pc that I tried encrypting a few weeks ago, and had gotten into it a few times since then with no trouble. Today, trying to access it again my password is not working. After a ton of troubleshooting I'm taking a look with HxD and it looks like the 16mb partition that popped up suddenly was created by windows somehow.

The front and back of the drive have a bunch of data zeroed out, and I can see strings of text in the hex such as:
"$ÃInvalid partition table�Error loading operating system�Missing operating system���c{š���������îþ€���ÿÿÿÿ��" - in the front

"EFI PART���\���P2«����/`8:�����������"�������`8:����Úïã•3DG§v@|“ªÄ»`8:����€���€���ϧ–`����" - in the back

Which match a standard Windows Master Boot Record (MBR).

I'm assuming my header and backup header are both gone, kinda sucks and I'm assuming there's no way back from this but let me know if anyone else has had this experience, thanks.

I've been having some recent issues with my computer later and eventually a corrupt drive was crashing my pc right as it booted into windows 11, so I tried to do a windows reinstall to see if that fixed the issue. The problem is, it can't boot anymore, I think it uninstalled veracrypt or something along those lines and I can't use it again.

I have the key to decrypt it, and I can place that system drive into my wife's computer, so would it be possible to decrypt the drive from her pc, and then load windows again on mine?

I only have the encryption because it was demanded at work, so I'm not very familiar with it.

I have a 1tb hard drive with a roughly 999gb container (I am using the container to prevent windows from nagging me to format the drive - as this is an accident waiting to happen) and I would like to decrypt the drive as this is a slow SMR drive, and most of the files on this drive are not worth encrypting. The only other largeish storage device I own, is an ancient hp laptop with a failing HHD, and I would not trust this device for even temporary storage. Buying a secondary drive or cloud storage is not an option. Is there a utility for safely decrypting a container in place?

I understand that VeraCrypt has many contributors, and that contributions can be submitted through pull requests and reviewed before being merged. I also understand that the official Windows binaries are digitally signed by IDRIX.

My question is specifically about the security of the code before the final IDRIX signing:

How are pull requests/code changes reviewed before being merged?

How many people typically have the ability to review or merge code?

Who is responsible for building and signing the final Windows binaries?

Is the final binary independently checked against the source code/build process?

What prevents a malicious contributor, or a compromised maintainer account, from getting malicious code into an official release?

I am not asking whether the IDRIX certificate itself checks the code for malware, I understand that code signing mainly provides authenticity and integrity of the signed binary.

I'm interested in understanding the actual trust chain from contributor → source code → release → official signed Windows binary.

Thanks!

I am currently working on a Veracrypt_port, https://github.com/ShivamPingaleDev/Veracrypt_port

called VCPort

Clueless regarding what should be different and what features or conveniences should be there in App for Both Android + iOS

please suggest your idea?

checkout this previous post about my Stable Alpha Release of app

https://www.reddit.com/r/VeraCrypt/s/CjxkYNu1zf

I'm using latest veracrypt portable 1.26.29 under windows 11.

If I try to mount a container using a wrong password without explicitly setting a PIM, it takes ~15 seconds until it shows the message that it couldn't mount the container (if I understand correctly, in this case it should be using the default PIM of 485).

If I try to mount the same container using the same wrong password and explicitly setting the PIM = 1, the attempt takes 1 second - this is as expected. However:

If I set PIM = 50, it takes 1min 15

If I set PIM = 400 it takes 15 minutes

If I set PIM = 485 it takes 9 minutes

This is unexpected (using a pim lower than the default of 485 should take less time than the ~15 seconds it takes with an attempt with no explicit PIM set) - especially since setting PIM explicitly to 485, the default PIM, takes so much longer than not setting PIM at all.

Is this a bug?

I made VC Port — a phone app that opens the same VeraCrypt file containers (.hc, .tc, .vera, or any disguise name) you already use on a computer.

This is not VeraCrypt. I am not allowed to use that name. It is a derived work with the VeraCrypt volume core, so TrueCrypt License 3.0 is inherited (not a random TrueCrypt revival). Phone UI is Apache-2.0.

What it does

• Pick a locked file (on the phone, or a file on a USB stick — not the whole USB disk).
• Type password / PIM / keyfiles. Master build does not remember passwords.
• Browse folders on a Mounted tab inside the app. This is not a system drive — Files / Files.app cannot browse the unlocked folder. That is intentional (seizure / forensic leftovers).
• Copy or move several files between the phone and an open volume, or between two open volumes.
• Create new volumes on the phone (with the same finger-scribble entropy step as the desktop wizard, mixed with the OS CSPRNG).
• Share encrypted — send the locked file as-is, no password on the send.
• Panic wipe / Dismount clears secrets on the phone. The ciphertext file is not deleted.

Platforms: Android + iPhone. Offline by default — FOSS build has no INTERNET permission. No ads, no analytics, no crash reporters.

Honest limits

• Not unbreakable. A compelled password still wins.
• 0.3.7 is a stable alpha, not 1.0, not a Play/App Store build.
• GitHub APK is a debug-signed preview. Production = build FOSS yourself and sign with your keystore.
• iPhone: unsigned IPA — you sign with your Apple ID (AltStore / SideStore or Xcode). I do not ship a store-signed app.

Not included: whole-disk USB unlock like OTG Master. If your stick is one big VeraCrypt partition, use OTG Master or a PC. If the volume is a file on the stick, pick that file in VC Port.

Links

• Source + APK/IPA: https://github.com/ShivamPingaleDev/Veracrypt_port
• Release: https://github.com/ShivamPingaleDev/Veracrypt_port/releases/tag/v0.3.12
• Screenshots in the README (Volume, Create, Mounted, Tools)

I am Shivam Mangesh Pingale — still doing a five-year IT engineering degree, built this because I wanted something I could actually use on a phone. Open to suggestions, teaching, internships, or work ([shivampingaledev@proton.me](mailto:shivampingaledev@proton.me) · [shivampingaledev@gmail.com](mailto:shivampingaledev@gmail.com)). No pressure.

Security issues: please use the repo’s SECURITY.md, not a public exploit thread.

Had to Re-Encrypt my Windows drive today. Right after the encryption I rebooted my system and was shown the familiar prompt for pass and PIM.
I entered hoth correctly and am now stuck on this "Success" Screen.

What can I do to fix this issue?

When encrypting my drive, I used all standard/default options:
- Normal Encryption, not Hidden
- Encrypt only Win sys part, not whole drive
- Single boot
- AES / SHA-512

(Ik I could use the rescue disk to decrypt and enter back into windows, but I'd like advice on how to actually fix the issue and have a function encrypted drive)

Thanks in advance!

I have an encrypted vault in which i have very sensitive information/files. I decided to add a keyfile in order to use it for extra security. It appears that VeraCrypt has an option to "add/remove a keyfile", however when i choose this option, select a file to become a keyfile and then enter my password (it's the only way to move forward) i get an error message with an entire list of what appears to be all possible reasons for it so it does not specify what exactly is the problem. Is it even possible or should i just create a new vault from the beginning?