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
Today I was successfully able to salvage my 2019 Dell XPS 8930 SE, which was destined to lose Secure Boot status because the 2011 Secure Boot Certificates are expiring at the end of the month. Dell refused to provide a solution to update the Certificates for any of its computers sold more than five years ago.
I therefore had to learn how to manually add the necessary 2023 Secure Boot Certificates to the BIOS. I was greatly assisted by a Guru at another Forum.
That brings up a question: does the Hasleo Offline WinPE.OPE file have to be recreated as a result? My .OPE file dates back to 2026-04-23.
I've recently had to move from Macrium Reflect due to the psmounterex.sys issue. I was pleased to discover Hasleo Backup as it appeared to do all that I needed. However I am having problems getting either Pre or Post-Commands to work. I have created a small test backup with a post command to run a simple test .bat file to pop-up a text message. I can see that the batch file is triggered, but nothing happens and no backup is created. Hasleo Backup then hangs and Cancel does not work. No log file is created.
I also wanted to use a Pre-Command to switch on an external HDD before backing up to it, but have read that this is not possible at the moment?
I downloaded Hasleo Backup Suite Free to try before I buy but I tried three times to do a System Backup and a Drive/Partition Backup and they all failed with failed to write file. All backups were full backups with the default settings.
This feature works successfully to wake-up a desktop PC to run the backup tasks, but does this not work on my ASUS laptop.
The laptop is not powered off, just the lid closed overnight. The Event Viewer is full of entries of events that have run while the lid is closed, e.g., UserModePowerService that seems to have an entry every minute, or Microsoft Windows security auditing that has lots of entries.
It is just a minor inconvenience as these task start as soon as the laptop is opened.
1. Created a File Backup with encryption
2. Forgot password (the known password does not work)
So cannot mount the backup, but most important cannot delete the backup task as it requires the password. Seems the only way to recover is:
- uninstall/reinstall HBS
- delete the now useless backup files
- import all the tasks except that one
- recreate the schedules
- create a new task for the one with the incorrect password
- run a new backup
As a result of a topic to which I have been responding on another Forum, the issue of the Hasleo Backup Suite GUI was mentioned as a negative influence on the user switching to Hasleo. That got me thinking, always a dangerous thing!
I have never liked the very dark appearance of the HBSP program on my two computers. I decided to see what I could do about that.
I went into the Themes options. I am not sure, but I think it was set to "Automatic" on my desktop computer. I apologize, but I wasn't paying really close attention. I switched it to the "Light Theme" and I was immediately a very happy camper. Then, I switched it to "Automatic" and the Light Theme "stuck."
Both of my computers are set in Windows 11 Pro (26200.8457) to use the OS "Light Theme." I think I recall back in the past that I had switched it from the HBS "Dark Theme" on the desktop computer to "Automatic" and nothing happened. Again, I do not trust my memory to be 100% at my age ...
I used HBSP to backup my laptop computer subsequently this afternoon after my desktop computer. HBSP was set to use the "Dark Theme" on that computer. I never selected the "Dark Theme on either computer. Of that fact, I am certain because I dislike Dark Themes.
So this raises two questions in my feeble mind:
1. Why is Dark Theme apparently the HBS program default Theme instead of Automatic?
2. Does the HBS program coding always accurately detect the OS Theme choice of the user's computer?
These are small issues to be sure, but they can have a big impact on a new user of the Hasleo Backup Suite. The user may decide to abandon HBS and look at other backup products with a more "attractive" GUI.
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.
I was experimenting a bit with Windows 11 Canary version 29585.1000 (Insider Experimental Future Platforms) in VMware Workstation.
I made an HBS image backup to a second internal drive, which I now tried to restore from within Windows.
Restore process started successfully, Windows rebooted into WinPE. But it then took a few extra seconds to load up HBS, showing only the screenshot tool in the meantime.
When HBS finally showed up, the restore process didn't start automatically. Instead I was given the normal HBS window in "Home" tab:
Logs from the WinPE HBS are attached, maybe this helps with the diagnosis. Using the current HBS version v5.8.2.1.
BTW: After manually starting the restore from the backup task, it finished without a problem, so this is only a hiccup with the auto select.
I couldn't reproduce this behavior on current Windows 11 or any older versions so I think this might be something new, possibly introduced by MS.
Please note: I haven't tested the outcome with the current latest Canary version 29599.1000 so far, but I'd assume it's still the same.
This post is quite long but that is necessary to explain the experiences.
HBS File Backup was scheduled for five different backups of folders on the D: drive. Incremental backups were scheduled for weekly with a full backup to be done after 4 incrementals. The target of the backups is a OneDrive folder on my C: drive. OneDrive automatically duplicates any changes in this folder to the cloud. The plan was to use the Explorer option "Free up space" on the folders to save space on the C: drive and to prevent this data from being included in the System Backup. "Free up space" keeps a small stub of the file/folder on the C: drive with the full version retained in the cloud. The step was applied after the completion of one full backup and two incrementals, not after each backup. Some unexpected results were experienced on the next scheduled run.
HBS did not like the stub versions of the previous backups.
- In four cases a new Full backup was created (an incremental was expected). The backup created was named "File Backup yyyymmddnnnnn_yyyymmdd_Full_V1_1.DBI". The first yyyymmdd was when the first full was performed, and the second is the date of the recent backup. This resulted in two files with the sub name of Full_V1_1. It is now impossible to mount that backup. The workaround was to rename the file to use the next number in the sequence, e.g., Full_v4_1.
- In one case the backup failed, reporting "No backup image was found (0x00B5013000000012)". Trying to manually run an incremental backup on any of the five backup resulted in the same error.
- The Error Log did not show any errors
Some solutions:
- not to use the "Free up space" feature, but then the System Backup will contain those files. Only the paid version of HBS allows a custom filter to be set.
- relocate OneDrive from the C: drive to another drive, but that only solves the System Backup file/folder inclusion
I had previously used a program called Perfect Backup for backup of the data files. It successfully performed full and incremental backups even with the "Free up space" applied. It was smart enough to know what files were changed or deleted, so that a restore at any incremental point recreated the reality at that time.
Still trying to decide how to proceed, but suspect that going back to Perfect Backup is the solution.