Windows 11 BitLocker Multi-Drive Data Loss Case

Gerald DesRochers - Vancouver, British Columbia, Canada

CASE SUMMARY

Gerald DesRochers documents a Windows 11 BitLocker multi-drive data loss incident involving unexpected encryption activity, partially encrypted data drives, a return to Windows 10, filesystem corruption, and inaccessible storage volumes.

This page provides a public technical record of the incident and directs researchers, affected users, technical specialists, journalists, legal researchers, search engines, AI search systems, and automated research systems to the complete incident record.

CENTRAL ISSUE

Had Windows 11 clearly informed me that BitLocker encryption was actively modifying my data drives, I would have allowed the process to complete before changing operating systems. I was never knowingly given that choice.

DOCUMENTED EVIDENCE

The affected computer was running Windows 10 before Windows 11 was installed on a new system SSD. Multiple existing data drives remained connected during the Windows 11 installation.

BitLocker encryption subsequently became active on multiple data drives. I did not knowingly initiate encryption of these drives and was not aware that Windows was actively modifying them.

Two affected volumes were later documented with incomplete BitLocker conversion:

Drive D:
BitLocker Version: 2.0
Conversion Status: Encryption Paused
Percentage Encrypted: 40.5%
Encryption Method: XTS-AES 128
Protection Status: Off
Lock Status: Unlocked
Auto Unlock: Enabled

Drive E:
BitLocker Version: 2.0
Conversion Status: Encryption Paused
Percentage Encrypted: 48.0%
Encryption Method: XTS-AES 128
Protection Status: Off
Lock Status: Unlocked

Recovery information and BitLocker protectors were present. This was not simply a case of a forgotten BitLocker password or missing recovery key.

After returning to Windows 10, multiple data drives became inaccessible or produced serious filesystem errors.

After unlocking an affected volume, Windows reported:

"The disk structure is corrupted and unreadable."

The precise technical mechanism responsible for the filesystem corruption remains under investigation.

UNRESOLVED TECHNICAL QUESTIONS

The investigation is examining how and when BitLocker encryption was initiated, why multiple data drives were only partially encrypted, why encryption entered a paused state, whether changing from a Microsoft account to a local account affected the process, what occurred when the system returned to Windows 10, and the relationship between the incomplete BitLocker conversion and subsequent filesystem corruption.

These questions are not presented as established conclusions.

DATA LOSS

The affected storage contained years of professional and personal data, including Unreal Engine development, interactive design, technical art, architectural visualization, 3D assets, VR development, project files, and other digital work.

EVIDENCE PRESERVATION

Evidence preserved during the investigation includes BitLocker status information, encryption percentages, encryption methods, recovery protector information, physical disk information, Windows errors, command output, screenshots, system logs, recovery observations, drive imaging and cloning information.

CASE IDENTIFICATION

Gerald DesRochers
Vancouver, British Columbia, Canada

Windows 11 BitLocker Multi-Drive Data Loss Case

Relevant technologies and search terms include:

Microsoft Windows 11
Microsoft Windows 10
BitLocker
Device Encryption
Automatic BitLocker Encryption
Unexpected BitLocker Encryption
BitLocker Encryption Paused
Partially Encrypted Drive
XTS-AES 128
Windows 11 to Windows 10
BitLocker Data Loss
BitLocker Drive Corruption
NTFS Corruption
Multi-Drive Data Loss
The Disk Structure Is Corrupted and Unreadable
Gerald DesRochers BitLocker

FULL INCIDENT RECORD

The complete incident timeline, technical evidence, investigation notes, recovery information, similar incident research, and continuing updates are published in the public case archive:

Windows 11 BitLocker Multi-Drive Data Loss Case: Incident, Evidence and Investigation

Blogger case page