Add Boot Menu: Failure to use a system API

[rogerrabbit]

Hi, 
I just installed the latest version of Hasleo Backup Suite (abandonning the last free version of Macrium Reflect, a step envisaged since some time and finally triggered by the psmounterex.sys driver issue).
After the first successful backup, I then tried to add a boot menu, but got the following error: "Failure to use a system API (0x00A0001500000005)"
Not sure whether the issue stems from the Hasleo software or from Windows 11 (latest version 26200.8655). I run Dism /Online /Cleanup-Image /RestoreHealth, unistalled Hasleo Backup Suite and reinstalled it, but the error came back.
Any help would be appreciated.
Thanks in advance
Roger

[Froggie]

@rogerrabbit - since most of us have done that thousands of times without issue, there's a hitch between your particular OS and HBS.  Best to take your description above along with your LOG file obtained via the HBS CONTEXT menu and send to Support AT EasyUEFI DOT com.

[admin]

We have analyzed error code 0x00A0001500000005, Windows returns error code 0x5 (Access Denied) when Hasleo Backup Suite attempts to add the boot menu. This is typically caused by antivirus software. Therefore, please temporarily disable your antivirus software, or add the following Hasleo Backup Suite executables to your antivirus's allowed application list (often referred to as the trusted applications or whitelist):

• BackupMainUI.exe
  
• BackupService.exe
  
• BackupWorker.exe
  
• BackupSystemTray.exe
  

Then try again.

If the issue persists, as @Froggie suggested, please provide your log files so that we can investigate further.

[rogerrabbit]

We have analyzed error code 0x00A0001500000005, Windows returns error code 0x5 (Access Denied) when Hasleo Backup Suite attempts to add the boot menu. This is typically caused by antivirus software. Therefore, please temporarily disable your antivirus software, or add the following Hasleo Backup Suite executables to your antivirus's allowed application list (often referred to as the trusted applications or whitelist):

• BackupMainUI.exe
  
• BackupService.exe
  
• BackupWorker.exe
  
• BackupSystemTray.exe
  

Then try again.

If the issue persists, as @Froggie suggested, please provide your log files so that we can investigate further.

Thanks to both of you (also to @froggie). I'll try @admin's suggestion and then come back to @froggie's proposal, if necessary.
(I am exclusively running Microsoft Defender as an antivirus).

[rogerrabbit]

Hi, here is my final report on the issue !

(1) I excluded the files indicated by @admin from Defender and tried to create the boot menu again. Same error.
(2) I did an upgrade install of Windows (I have routine with that, I can do it very quickly).
(3) I tried again to create the boot menu. Strangely enough, immediately after having clicked the icon named "Create a boot menu" in "Tools", the icon switched to "Delete a boot menu". There was no process (or time) for the creation of the menu. I restartet the computer and the menu was there !

So it looks like as if the menu was always there, but for some bizarre reasons, it didn't show up at boot!

Everything seems ok now ! Thanks !

[admin]

@rogerrabbit,

Glad to hear the problem is gone. 0x5 (Access Denied) definitely means some program blocked HBS's operation. Maybe you could send us the log file, and we can take a closer look.
https://images2.imgbox.com/2b/1c/JQCplK55_o.png

Thanks.

[rogerrabbit]

Hi @admin,
thanks for your help.
I don't understand anytyhing about log files, but found the following entries:

"2026-06-17 13:25:27, Info                  
DISM  DISM Imaging Provider: PID=4740 TID=3464 The provider FfuManager does not support CreateDismImage on C:\WinPETem\572b1026-a599-4d97-907e-05de11a2ff47\mount - CGenericImagingManager::CreateDismImage
2026-06-17 13:25:27, Info                  
DISM  DISM VHD Provider: PID=4740 TID=3464 [C:\WinPETem\572b1026-a599-4d97-907e-05de11a2ff47\mount] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2026-06-17 13:25:27, Info                  
DISM  DISM Imaging Provider: PID=4740 TID=3464 The provider VHDManager does not support CreateDismImage on C:\WinPETem\572b1026-a599-4d97-907e-05de11a2ff47\mount - CGenericImagingManager::CreateDismImage"

I will now upload the full log file, but please bear in mind that they are only from yesterday 2026-06-17 and not from the day before (I uninstalled and reinstalled your software twice, and also made a repair install of Windows).

Kind regards

[admin]

Hi @admin,
thanks for your help.
I don't understand anytyhing about log files, but found the following entries:

"2026-06-17 13:25:27, Info                  
DISM  DISM Imaging Provider: PID=4740 TID=3464 The provider FfuManager does not support CreateDismImage on C:\WinPETem\572b1026-a599-4d97-907e-05de11a2ff47\mount - CGenericImagingManager::CreateDismImage
2026-06-17 13:25:27, Info                  
DISM  DISM VHD Provider: PID=4740 TID=3464 [C:\WinPETem\572b1026-a599-4d97-907e-05de11a2ff47\mount] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2026-06-17 13:25:27, Info                  
DISM  DISM Imaging Provider: PID=4740 TID=3464 The provider VHDManager does not support CreateDismImage on C:\WinPETem\572b1026-a599-4d97-907e-05de11a2ff47\mount - CGenericImagingManager::CreateDismImage"

I will now upload the full log file, but please bear in mind that they are only from yesterday 2026-06-17 and not from the day before (I uninstalled and reinstalled your software twice, and also made a repair install of Windows).

Kind regards

What we need is the log file generated by Hasleo Backup Suite. Thanks.

[rogerrabbit]

Hi again,
I sent the log file to the adress provided by @froggie. Didn't manage to upload the file to the adress provided by you (@admin), because it does not seem to accept .txt files.
Have a nice day / night (wherever you are  ).

[admin]

@rogerrabbit，

Thank you very much for the log file.

After reviewing the log file you provided, we found that when Hasleo Backup Suite attempts to delete its own installed .wim file, it encounters error 0x5 (Access Denied). This suggests that some other process is intercepting or blocking the operation.

Please try adding and removing boot entry a few more times to see if the issue happens again.

Best regards,