Hasleo Backup Suite V6.0.0.0 ALPHA test release

[yastil]

P.S.
For reference, the current WinRE status on my system is as follows:
WinRE -- status, location, BCD identifier
WinRE: Enabled
WinRE location: \\?\GLOBALROOT\device\harddisk1\partition3\Recovery\WindowsRE
WinRE BCD identifier: present
WinRE version (informational only, not compared with OS Build): 10.0.26100.9444

[n8chavez]

Maybe it should limit its inclusion to DISPLAY, HID devices, DISK (NvME specifically) and NETWORKING.  That seems to cover what most users need when using the ED.  Bluetooth is not available within the WinPE environment, I believe (Microsoft doesn't offer a working construct for that networking environment within the PE build).

Are displays driver really needed in an RE/PE?  When's the last time you actually engaged your graphics cards in one?  That has to be where the ballooning is coming from.  I think generic display drivers are fine.

[Froggie]

Maybe it should limit its inclusion to DISPLAY, HID devices, DISK (NvME specifically) and NETWORKING.  That seems to cover what most users need when using the ED.  Bluetooth is not available within the WinPE environment, I believe (Microsoft doesn't offer a working construct for that networking environment within the PE build).

Are displays driver really needed in an RE/PE?  When's the last time you actually engaged your graphics cards in one?  That has to be where the ballooning is coming from.  I think generic display drivers are fine.

You're probably correct (the Intel UHD driver itself is 1.5+gB) although I've seen users with display probs (usually 4K or 8K displays) and I don't know whether "today's" generic display driver handles these types of displays well.  I know my 4K display needs quite a bit of squinting when I'm reading the HBS UI   (lucky for me, since I use it so much I know where everything is  )

[yastil]

Subject: Rescue disk creation fails at 100% - "Failed to start system API (0x011F0015C0AAB132)" - Backup Suite Home 6.0.0.0 Alpha

Hello,

In my earlier post I wrote that everything was OK, but I had not tested it thoroughly at that time. Here is the full description of the problem.

SYSTEM
Windows 11, build 26100, Hasleo Backup Suite Home V6.0.0.0 Alpha (Czech UI).

PROBLEM
Tools > Create Rescue Disk > From WinRE, with automatic driver injection and "Enable support for 'Windows UEFI CA 2023'" enabled. The progress bar for building WinPE reaches 100% and then the wizard shows in red:
"Failed to start system API. (0x011F0015C0AAB132)"
The error is reproducible and the code is the same every time.

WHAT I CHECKED AND TRIED (the error stayed identical every time)
1. WinRE is fine: reagentc /info shows "Windows RE status: Enabled", version 10.0.26100.9444, location \\?\GLOBALROOT\device\harddisk1\partition3\Recovery\WindowsRE.
2. I found a stale mount: dism /get-mountedwiminfo showed Mount Dir C:\Mount, Image File E:\sources\boot.wim, Index 1, Read/Write, Status "Invalid". I cleaned it with dism /cleanup-wim and afterwards got "No mounted images found". The error still occurs.
3. No leftover registry hive: reg query HKLM | findstr /i "WIM" returns nothing.
4. I unchecked "Enable support for 'Windows UEFI CA 2023'".
5. I temporarily disabled real-time protection.
6. I also tried the "Download WinPE components" method.  

DISM LOG (C:\Windows\Logs\DISM\dism.log, 2026-09-23, 20:21:36 to 20:21:43)
DISM fails seven times to unload the offline registry hive:
"Failed to unload hive (type 1) with ERROR_ACCESS_DENIED. Retrying..."
"Could not unload hive key normally ... hr = 0x80070005"
and then:
"Failed to disconnect OSServices - CDISMProviderStore::Internal_DisconnectProvider(hr:0x80070005)"
"Failure occurred during shutdown of the Image Session - CDISMManager::CloseImageSession(hr:0x80070005)"
After the failure no hive and no mount remain loaded.

MY CONCLUSION
The WinPE image seems to be built completely and the failure happens in the final stage. The same error occurs with both methods ("From WinRE" and "Download WinPE components"), so it does not seem to be specific to my WinRE. I do not know the root cause. I have not investigated Secure Boot as a possible cause, so I make no claim about it.

Could you please tell me what error code 0x011F0015C0AAB132 means and what may be holding the hive open? I am happy to send the full dism.log or any Hasleo log if you tell me where it is stored.

A screenshot from the Hasleo program with the error message is attached.

Thank you,
Luboš

[Froggie]

@yastil - I believe the Devs are fully aware of the problem (having received the same input via their SUPPORT portal).  I also experienced the same issue.  I also tested the build with Hasleo's OffLine PE offering (OPE) and it does not error using that PE source, only the download and RE sources.

The other issues brought up earlier as far as ISO size have also been seen by others.  Hopefully they will get enough information from users to address these issue.  I believe they are different from each other but both are serious issues... this is what ALPHA version testing is all about   !

Thanks for getting back to the Devs!

[yastil]

Hello, and thank you for the reply.

I can confirm the same behavior: with "From WinRE" and with "Download WinPE components" the build reaches 100% and then fails with "Failed to start system API (0x011F0015C0AAB132)". Where do I find the Offline PE (OPE) source you mention? My dialog only offers From WinRE, Download WinPE components and From custom WIM.

A correction to my first post: please disregard the dism.log excerpt from 20:21. It comes from separate dism.exe sessions (probably a manual "dism /cleanup-wim" that I ran myself). Hasleo writes its own DISM log to ...\Hasleo Backup Suite\bin\logs\BuildWinPE.log. In that file, in the Hasleo process, the end of the build shows:

Error DISM PE Provider: CPEImg:etach: Detach failed with error 0x800703fa.
Error DISM Manager: PID=22840 Failure occurred during shutdown of the Image Session. - CDISMManager::CloseImageSession(hr:0x800703fa)

0x800703FA is ERROR_KEY_DELETED, which usually means that something still holds the registry of the mounted image when it is unmounted. The unmount then completes ("Unmount complete") and the DISM API shutdown is clean.

I can provide the full BuildWinPE.log to the developers if it helps.

Thank you

[Froggie]

@yastil - what the Devs need is their own LOG system.  This may be obtained by using their UI CONTEXT menu and selecting "Save LOG file."  That file should be sent along with every issue discovered with the application... either release, beta or alpha.

[admin]

Hi everyone,

Thank you all for participating in the V6.0.0.0 internal test and for sharing your detailed feedback. Your reports, especially those regarding the Emergency Disk (ED), are very important to us.

Regarding the WinPE size bloat issue: the problem is indeed that too many drivers are being added to WinPE. We are currently working to narrow the range of drivers injected. The challenge is determining which OEM drivers are truly needed. Some drivers only cause bloat without providing real value to most users. We appreciate everyone's suggestions to limit it to specific device categories, such as HID, DISK, and NETWORKING, this is exactly the direction we are working toward.

We will continue to improve in upcoming builds.

Have a nice day!

Best regards,

[admin]

We’ve narrowed down the scope of driver injection. Please download the updated BuildPE.dll, replace the existing file in the bin folder under the installation directory, and then try creating the WinPE again.
https://www.easyuefi.com/backup-software...uildPE.dll

Thanks.

[n8chavez]

Replacing the BuildPE.dll fixed my issue. I tried creating an RE and a PE, and both were successful. The RE was 946 meg, whereas the PE was 848 meg. The PE is about twice what it was before, and takes about five minutes to build, compared to the previous 1:30. But it does build and boot just fine.