Why ZIP Compression Speed Halves on Drives Encrypted by BitLocker

Quick fix: BitLocker encrypts every disk write, and the AES operations halve compressor throughput. Move ZIP operations to RAM (use 7-Zip with a tempfile path on a RAM disk) or to an unencrypted secondary drive. Modern CPUs with AES-NI minimize the penalty; older CPUs without AES-NI suffer more.

You ZIP a large folder. On your unencrypted secondary drive, the operation completes in 2 minutes. On the BitLocker-encrypted C: drive, the same operation takes 5 minutes. Throughput is roughly halved. BitLocker is adding measurable overhead to disk I/O during compression-heavy operations.

Why BitLocker slows compression

BitLocker uses AES-XTS encryption per disk block. Every read from the encrypted volume decrypts; every write encrypts. Compression reads source files and writes intermediate temp data plus the final ZIP — all those operations go through BitLocker. On a CPU with AES-NI hardware acceleration (most CPUs since 2010), the overhead is 5–15%. On older CPUs or in software AES fallback, it’s 40–60%.

Method 1: Verify AES-NI is enabled

1. Open elevated PowerShell.
2. Run (Get-CimInstance Win32_Processor).Caption — check the CPU model.
3. Look up the CPU on Intel or AMD’s site for AES-NI support (almost all CPUs since 2010 have it).
4. Run manage-bde -status and check the Encryption Method — XTS-AES 128 or 256.
5. If AES-NI is supported but BitLocker is in software mode, ensure no firmware or hypervisor is disabling AES-NI.

Method 2: Move ZIP temp to a RAM disk

1. Install a free RAM disk tool like ImDisk.
2. Create a RAM disk (e.g., 8 GB at drive R:).
3. In 7-Zip: Tools → Options → Work directory set to R:.
4. Compress operations write temp files to RAM — no BitLocker overhead for the temp data.
5. Final ZIP still writes to encrypted disk but at much smaller volume.

Method 3: Use a separate unencrypted scratch drive

1. Add a secondary internal SSD or external high-speed drive without BitLocker.
2. Use it as the compression workspace.
3. Move the final ZIP to encrypted storage only after compression completes.

Verification

• Time a ZIP operation. Compare encrypted vs unencrypted speed; the gap should narrow.
• 7-Zip’s benchmark feature (Tools → Benchmark) shows raw compression speed without I/O bottleneck.

If none of these work

If your CPU lacks AES-NI, the overhead is real and structural — consider upgrading the CPU. For workloads where BitLocker overhead is unacceptable, evaluate whether the encryption is required by policy or just by habit. For specific workflows like build artifacts, exclude that folder from BitLocker scope by moving it to an unencrypted volume.

Bottom line: BitLocker adds AES overhead that older CPUs feel more. RAM disk workspace or unencrypted scratch drive workarounds shift the cost.