1 hour ago
(3 hours ago)azmawee Wrote: Hi,
Following up on the C:\Program bug I reported earlier. After deleting the C:\Program file and the first issue was resolved, a new error appeared when creating the Emergency Disk:
"The system cannot find the path specified. (0x0782008500000003)"
The WinPE build itself completes successfully (100%), but the error occurs during post-processing.
**Root Cause:**
Hasleo scans ALL volumes looking for a \Recovery\ folder, including volumes that have NO drive letter assigned (only a mount point). In my case, I have a 5.5TB NTFS data volume mounted at C:\mnt\WR6T1\ with no drive letter. Hasleo scans this volume using its GUID directly, finds no \Recovery\ folder, and fails with path not found - even though WinRE is perfectly healthy on the correct partition.
Important note: Even after assigning a drive letter to that volume, the error persisted. This confirms the issue is not about the missing drive letter itself, but about Hasleo failing to handle volumes that do not contain a \Recovery\ folder gracefully.
Log entry from BackupService.log showing the issue:
CheckPeCrab.cpp 199 nRet=0x0782008500000003 \\?\Volume{00000015-09e0-3804-9bdc-d8012a000000}\\Recovery\*
System info:
- OS disk: Disk 2 (C
- WinRE confirmed enabled and working (reagentc /info shows correct location)
- Affected volume: separate 5.5TB NTFS data volume, no drive letter, mounted at C:\mnt\WR6T1\
**Workaround:** Uninstall and reinstall Hasleo Backup Suite resolves the issue.
**Suggested fix:** Hasleo should only scan the actual WinRE partition as reported by reagentc instead of brute-force scanning all volumes. If scanning all volumes is necessary, the code should gracefully skip volumes that do not contain a Recovery folder instead of returning a fatal error.
Hope this helps. Thanks.
reagentc is not always reliable. For example, when WinRE is disabled, it does not display the path, even though WinRE still exists on the system. Moreover, across different languages or versions of Windows, its output format may vary, making parsing difficult and hurting compatibility - and no one can guarantee that Microsoft won't change the output format in the future.
Unfortunately, Microsoft does not provide an API to directly obtain the WinRE path. Scanning all volumes to locate WinRE, while admittedly inelegant, is currently the most reliable way to find it.
Regarding the error "The system cannot find the path specified," we would greatly appreciate it if you could provide the log file.
Thanks.