Recuva crashes on scanning storage spaces drive with bitlocker enabled

Recuva Recuva Bug Reporting
1

I have created a RAID5 using storage spaces on 4 NVMe drives, and I have enabled bitlocker on it. When I try to run a scan with Recuva on the drive after it is already mounted, Recuva immediately crashes. This is 100% reproducible. Running Recuva in debug mode produces this log:

[2026-03-15 12:53:46] [INFO ] Recuva v1.54.120 (64-bit)
[2026-03-15 12:53:46] [INFO ] System Info: Windows 11 Pro 64-bit, AMD Ryzen 9 9950X3D 16-Core Processor, 64.0GB RAM, NVIDIA GeForce RTX 5090
[2026-03-15 12:53:46] [WARN ] LibRecuva::Drives::Ssd::IsSSD: Identify device incorrect - all zeros
[2026-03-15 12:53:46] [WARN ] LibRecuva::Drives::Ssd::IsSSD: Identify device incorrect - all zeros
[2026-03-15 12:53:46] [WARN ] LibRecuva::Drives::Ssd::IsSSD: Identify device incorrect - all zeros
[2026-03-15 12:53:46] [WARN ] LibRecuva::Drives::Ssd::IsSSD: Identify device incorrect - all zeros
[2026-03-15 12:53:46] [WARN ] LibRecuva::Drives::Ssd::IsSSD: Identify device incorrect - all zeros
[2026-03-15 12:53:46] [WARN ] LibRecuva::Drives::Ssd::IsSSD: Identify device incorrect - all zeros
[2026-03-15 12:53:46] [WARN ] LibRecuva::Drives::Ssd::IsSSD: Identify device incorrect - all zeros
[2026-03-15 12:53:46] [WARN ] LibRecuva::MountedVolumes::GetVolumePhysicalDisksNumbers: IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS failed with GLE(0x1)
[2026-03-15 12:53:46] [INFO ] CMainWnd::CheckForUpdates: Check for updates: is disabled
[2026-03-15 12:53:48] [WARN ] LibRecuva::Drives::Ssd::IsSSD: Identify device incorrect - all zeros
[2026-03-15 12:53:48] [WARN ] LibRecuva::Drives::Ssd::IsSSD: Identify device incorrect - all zeros
[2026-03-15 12:53:48] [WARN ] LibRecuva::Drives::Ssd::IsSSD: Identify device incorrect - all zeros
[2026-03-15 12:53:48] [WARN ] LibRecuva::Drives::Ssd::IsSSD: Identify device incorrect - all zeros
[2026-03-15 12:53:48] [WARN ] LibRecuva::Drives::Ssd::IsSSD: Identify device incorrect - all zeros
[2026-03-15 12:53:48] [WARN ] LibRecuva::Drives::Ssd::IsSSD: Identify device incorrect - all zeros
[2026-03-15 12:53:48] [WARN ] LibRecuva::Drives::Ssd::IsSSD: Identify device incorrect - all zeros
[2026-03-15 12:53:48] [WARN ] LibRecuva::MountedVolumes::GetVolumePhysicalDisksNumbers: IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS failed with GLE(0x1)
[2026-03-15 12:53:52] [INFO ] LibRecuva::FileSystems::`anonymous-namespace’::LogBootSector: Boot sector:

REMOVED HASH FOR SECURITY

[2026-03-15 12:53:52] [INFO ] CNtfsUndeleterImpl::FindFileRecords: Reading MFT

2

I’m not sure how sucessful any attempted recovery from a Raid drive will be, simply because of the way that a Raid distributes data across an array of multiple discs.

I’m not at all sure that Recuva was designed to handle Raids.

You may want to have a read of these before trying to recover from a RAID; and you may need a recovery tool that has been specifically designed to recover from RAIDs:

This one gives 4-steps that you should go through before attempting file recovery from a Raid:

3

Thank you for your response. I am not trying to recover files from a broken RAID or do RAW recovery. The RAID is working fine and the RAID partition is already mounted. I am just trying to recover deleted files from the mounted partition, which, from the point of view of any recovery software, is not any different from a non-RAID partition. RAID matters only when RAW recovery is involved, which is not what I am trying to do. The problem here is that Recuva is simply crashing in this case, preventing any possibility of recovering deleted files from the partition. Other competing software such as EASEUS or Disk Drill do not have such problem, and can find and recover files from the mounted RAID partition without any issues.

4

In that case I’m afraid that I can only suggest that you stick with using Easeus or DiskDrill then.

Recuva was designed for home users to recover files from FAT32 and NTFS partitions rather than spanned RAID arrays.
It can handle some limited recovery from RAIDs, but that is pretty limited.

Recuva has not had an update to its functionality for years, and so I very much doubt that it will be getting one anytime soon.

Recuva appears to have become almost Abandonware now, it is still available, still functional and still useful to a certain extent - but don’t expect any updates (or any bugfixes either).