Failed to create Emergency Disk - 0x01CF001E000000C1

[azmawee]

OS: Windows 11 25H2
Hasleo Backup Suite: V5.8.2.1
ADK: 10.1.26100.2454 (December 2024) installed
WinPE Add-on: installed

Error: Failed to create (start) process. (0x01CF001E000000C1)

copype.cmd works manually only when WinPERoot, OSCDImgRoot
and DISMRoot environment variables are set manually in CMD.
Hasleo seems to not set these variables when spawning its process.

[azmawee]

Hi,

I was getting this error every time I tried to create an Emergency Disk:

"Failed to create (start) process. (0x01CF001E000000C1)"

Environment:
OS: Windows 11 Pro 25H2
Hasleo Backup Suite Free V5.8.2.1
ADK: 10.1.26100.2454 (December 2024) with WinPE Add-on installed

Root Cause:
After extensive debugging using Sysinternals Process Monitor, I found that there was a stray file named "Program" (419 bytes) sitting in the root of C:\ drive (C:\Program). When Hasleo's BackupService.exe tries to spawn a process using an unquoted path containing spaces (e.g. C:\Program Files...), Windows incorrectly parsed it and tried to execute C:\Program instead of the intended executable, causing the process creation to fail.

Fix:
Simply delete the file C:\Program from the root of C:\ drive.

del C:\Program

After deleting the file, Emergency Disk creation worked immediately without any other changes needed.
Hope this helps someone else facing the same issue. Also suggest that Hasleo developers review executable paths to ensure they are properly quoted to prevent this issue from occurring.

[admin]

I'm glad to hear that you have figured out the problem.

Root Cause:
After extensive debugging using Sysinternals Process Monitor, I found that there was a stray file named "Program" (419 bytes) sitting in the root of C:\ drive (C:\Program). When Hasleo's BackupService.exe tries to spawn a process using an unquoted path containing spaces (e.g. C:\Program Files...), Windows incorrectly parsed it and tried to execute C:\Program instead of the intended executable, causing the process creation to fail.

We will fix this problem as soon as possible.

Have a nice day!

[azmawee]

I'm glad to hear that you have figured out the problem.

Root Cause:
After extensive debugging using Sysinternals Process Monitor, I found that there was a stray file named "Program" (419 bytes) sitting in the root of C:\ drive (C:\Program). When Hasleo's BackupService.exe tries to spawn a process using an unquoted path containing spaces (e.g. C:\Program Files...), Windows incorrectly parsed it and tried to execute C:\Program instead of the intended executable, causing the process creation to fail.

We will fix this problem as soon as possible.

Have a nice day!

Thank you for the quick response!
Just to help you recreate the bug: simply create an empty file named "Program" in the root of C:\ drive, then try to create an Emergency Disk. The error 0x01CF001E000000C1 will appear immediately.

Deleting C:\Program resolves the issue instantly.

Hope this helps with the fix!

[admin]

I'm glad to hear that you have figured out the problem.

We will fix this problem as soon as possible.

Have a nice day!

Thank you for the quick response!
Just to help you recreate the bug: simply create an empty file named "Program" in the root of C:\ drive, then try to create an Emergency Disk. The error 0x01CF001E000000C1 will appear immediately.

Deleting C:\Program resolves the issue instantly.

Hope this helps with the fix!

Thank you, this is very helpful for fixing the problem.

[admin]

@azmawee,

Strangely, this issue does not occur on our side, even if I create the C:\Program folder. Could you provide the log file to us, as shown below:


Thanks.

Best regards,

[azmawee]

@azmawee,

Strangely, this issue does not occur on our side, even if I create the C:\Program folder. Could you provide the log file to us, as shown below:


Thanks.

Best regards,

Hi, sorry just notice the attachment area, here is the logs.

[azmawee]

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.

[al3x]

Strangely, this issue does not occur on our side, even if I create the C:\Program folder.

Just a quick note: I was able to replicate this, too. Make sure you add a "Program" file, not a folder.
For example, if you copy "calc.exe" to "c:\Program", it will even execute the calculator on recovery disk creation.

[admin]

@azmawee and @al3x, thank you very much, the issue of 'Failed to create (start) process' has been identified.