Runtime Software offers separate utilities for broken arrays, NAS boxes, plus damaged file systems. The pieces work, but the full recovery path feels fragmented, narrow, plus unnecessarily difficult.
Runtime Software is hard to recommend for a fresh RAID or NAS recovery. RAID Reconstructor supports only RAID 0 plus RAID 5 directly, while a complete job may require another Runtime utility. Disk Drill is the cleaner option for most home users, photographers, plus small offices.
The biggest concern is starting with the wrong Runtime utility, then discovering that your array type, file system, or recovery stage requires another paid program.
Runtime Software sells several Windows utilities for reconstructing RAID arrays, recovering supported NAS volumes, mounting images, plus scanning damaged file systems. A complete job may require more than one application.
Best forWindows technicians working with a known RAID 0 or RAID 5 layout
RAID Reconstructor recognized our basic RAID 0 stripe plus a degraded RAID 5 set, then offered sensible guesses for drive order, block size, plus start offset. The entropy graph plus XOR checks are useful if you already understand RAID geometry.
The trouble starts outside that narrow lane. Direct recovery focuses on RAID 0 plus RAID 5. RAID 6, RAID 10, nested layouts, vendor-specific metadata, plus unusual parity schemes need extra manual work or outside assistance. The program also expects every member disk to be visible separately through a non-RAID controller.
NAS Data Recovery can automate work on single-disk NAS units plus RAID 0, RAID 1, or RAID 5 appliances using EXT or XFS. That covers a number of older Buffalo, Iomega, D-Link, Western Digital, plus Seagate boxes.
It is much less convincing for a current mixed NAS fleet. The drives must be removed from the enclosure, connected locally, then exposed individually to a Windows PC. There is no direct recovery over the network. Modern Btrfs pools, ZFS, SHR-style layouts, RAID 6, encrypted volumes, plus proprietary snapshots fall outside the comfortable path.
A typical RAID job does not end inside RAID Reconstructor. The utility determines the array geometry, then creates a virtual image or raw image. You may still need Captain Nemo to mount it or GetDataBack Pro to scan damaged file-system structures.
That handoff makes sense to a recovery technician, but it is awkward during a stressful home recovery. Labels such as destriper, VIM, XOR test, start sector, plus parity rotation arrive before the program has explained what decision is safe. Disk Drill puts disk imaging, array assembly, scanning, preview, plus export into a more coherent interface.
Once a correct virtual array reached GetDataBack Pro, ordinary NTFS plus EXT folder recovery was respectable. It restored useful directory structures from our simulated partition damage, with better results than a simple file-signature carve.
Results dropped when array parameters were slightly wrong or the test image contained fragmented media files. The preview tool helped catch bad output, though reviewing several possible file-system trees became tedious. Our synthetic SSD image produced a 61% validated recovery rate, while the SD-card image reached 68%.
Each Runtime license is a one-time purchase with lifetime updates. That sounds reasonable until the recovery crosses product boundaries. RAID Reconstructor costs $99, NAS Data Recovery costs $99, while GetDataBack Pro is another $79.
The $319 Ultimate Bundle includes Runtime's recovery plus forensic products, but many home users will need only one recovery. The free downloads can analyze or preview data. They do not provide a meaningful free export allowance.
We used a Windows 11 workstation with 32 GB of RAM, direct SATA connections, plus verified raw disk images. The set included a two-disk RAID 0, a degraded four-disk RAID 5, a mirrored EXT NAS volume, a 500 GB SSD image, plus a formatted SD card. Test files included JPEG, RAW, MP4, PDF, DOCX, ZIP, plus small database files.
Recovery rates count only files that opened correctly plus matched their original checksums where a full match was possible. Scan timing excludes drive imaging. Support response time came from one ordinary technical question sent to each vendor, so it should be read as a snapshot rather than a guaranteed service level.
Skip do-it-yourself Runtime recovery if a disk clicks, repeatedly disconnects, reports the wrong capacity, or slows to a few kilobytes per second. Repeated scans can worsen a physical failure. You should also pause if two disks are missing from RAID 5, any member of RAID 0 has failed physically, or the NAS uses encryption, ZFS, Btrfs, RAID 6, SHR, plus an unfamiliar vendor layout.
A safer DIY case is a controller failure where every disk remains healthy, the bay order is known, plus complete images can be made. Even then, work from images rather than the original drives.
| Category | Performance | Score |
|---|---|---|
| 01 RAID Reconstruction | 5.2/10 | |
| 02 NAS Compatibility | 4.3/10 | |
| 03 Recovery Workflow | 3.8/10 | |
| 04 File Recovery Results | 6.1/10 | |
| 05 Cost and Licensing | 4.7/10 |
Identical hardware, identical test scenarios. Here is how they compared.
| Metric | Runtime Software | Disk Drill |
|---|---|---|
| SSD recovery rate | 61% | 82% |
| SD card recovery | 68% | 91% |
| Quick scan time (500 GB) | 8 min | 5 min |
| Deep scan time (500 GB) | 94 min | 71 min |
| Free recovery limit | Preview only | 100 MB on Windows |
| License model | One-time $319 bundle | One-time $149 |
| Email support response | ~31 hours | ~9 hours |
| Overall score | 4.8 / 10 | 8.7 / 10 |
Choose Disk Drill if you want to image the source, assemble a supported array, inspect recoverable files, then export them without bouncing among separate programs.
Disk Drill is the better starting point for most recoveries. It combines byte-to-byte imaging, virtual RAID assembly, file-system scanning, lost-partition searches, previews, plus file export in one application. That reduces the chance of buying one utility only to learn that another is required.
The Windows edition allows 100 MB of free recovery. Disk Drill PRO costs $89 per year or $149 for a lifetime license, covering one user with activation on up to three devices. RAID recovery still requires healthy disk access plus correct member images, so physically failing drives belong with a lab.
One user testing several professional recovery tools said GetDataBack showed damaged image files plus filenames filled with placeholder characters, while the other tools produced more usable results.
A NAS owner reported that GetDataBack initially found only two small EXT partitions after a long scan, leaving uncertainty over whether another 14-hour pass would recover the original folder tree.
Another user said GetDataBack recognized the drive but froze at the start of the scan during four separate attempts.
Older community discussions still recommend GetDataBack for some logical recoveries, particularly where retaining file names plus directory structure matters more than a simple raw-file carve.
Runtime Software is not our recommendation for most RAID or NAS emergencies. It has capable low-level tools, but limited direct array support, Windows-only operation, plus frequent handoffs between separate products make the process harder than it needs to be. Experienced technicians handling a known RAID 0 or RAID 5 may still find RAID Reconstructor useful. Everyone else should image the disks first, then start with Disk Drill or contact a recovery lab if any drive is unstable.
Power down the NAS, label every disk by bay number, then create byte-for-byte images before scanning or attempting any reconstruction.