Their method of solving the SYSTEM backup issue is not solid when it comes to DISK/PARTITION backup. I believe they need to sit down and come up with a different method that can be applied to ANY of their backup options as far as geometry changes are concerned.
I couldn't agree more. It's a same old story though. Micro Windows Group create an unbalance for software developers to either have to work around or completely start from scratch again. HASLEO has been running too smooth for awhile so MS Windows bunch throws another wrench in the machine AGAIN. I'm confident the HBS DEVS will work it out eventually, but as you point out @TheRollbackFrog, it might not be sufficient for the DISK/PARTITION feature. But that CHANGE OF GEOMETRY issue really needs be studied hard and a code for the program to SAFELY adapt for when it occurs.
They are seriously considering a fix as I type, but based on their statements, they don't quite have the whole picture yet (or they don't use the right words in their offered fix)... they will . I'll keep ya posted...
Well i definitely found myself caught flatfooted on 1, and only the one VITAL system where things bluescreened with the missed mismatch. I have since torched those bad incs/diff's as though they never happened. Lesson learned. I haven't performed much in depth partition shifting's and other maneuvers outside the main C:\ partition which holds the bulk of our usage but after this more attention and experimenting locally is in order. Because the way windows group update devs can seriously affect our backups like this demand it anymore. I just happened to have an August full AND series of incrementals which recovered my system quite nicely. The silver lining on my end is that i finally have made use of HASLEO BACKUP SUITE'S file/folder feature in which i've now begun to utilize across platforms and drives to safekeep desktop elements in event of whenever necessary.
Hasleo Backup Suite V5.4.2.4 Released! What's new in this version: 1. Added support for backing up BitLocker drives with hardware-based encryption 2. Fixed an issue where file filtering did not work as expected 3. Fixed an issue that caused changing the task folder to fail 4. Fixed other minor bugs Here are the download links: https://www.easyuefi.com/forums/thread-846-page-31.html
@TheRollbackFrog Sir, do you, or anybody else know if this update fixes the problem cited above? Not knowing should be a deal breaker for anybody who solely relies on it. I use MR 8.1 and FreeFileSync for redundancy but won't be using Hasleo again until I get confirmation of a fix from a reliable source.
@AlphaOne - v5.4.2.4 does not fix the most recent anomaly concerning geometry changes during DISK/PARTITION backups. The previous release, v5.4.2.3 did offer a fix for the same anomaly during SYSTEM backups only.
Was that removed from this version or still working? I assume System fix is still a GO. But that aside here comes the real problem. On recreating yet another new ER UFD anyone know yet, is if the newly created HBS Emergency Disk will even work? Since we now have the MS UEFI Secure boot DBX/KEK/DB Firmware ordeal which won't boot if HBS boot UFD isn't been EQUALLY UPDATED and modified to MATCH the updated Secure Boot MS Firmware certificate being widely discussed right now. Microsoft strictly mentions bootable recovery media will be adversely affected if recovery vendors still use 2011 CA instead of 2023 CA A useful good tool to check. I confirmed my own systems with it. The .CMD command line scripts worked best for me not powershell. https://github.com/cjee21/Check-UEFISecureBootVariables EVENT ID:1037 https://support.microsoft.com/en-gb...e-events-37e47cf8-608b-4a87-8175-bdead630eb69
It's amazing how quickly an application can be dethroned. Hasleo Backup Suite is slowly replacing Macrium Reflect as the image backup king. I see evidence of it across forums everywhere.
@EASTER - I will try and find out planning on Hasleo's part (this is not a cost issue to Hasleo). Pls remember, this issue only affects SECURE BOOT users... no certificate of any kind is required for non-SECURE BOOT users. PS- the SYSTEM Image geometry issue remains fixed in the v5.4.2.4 release.
@EASTER - this POST in their Forum kinda describes where they're thinking/working at the moment on the changed geometry issue. I expect an announcement on their progress in the somewhat near future.
@EASTER - A check of the currently produced (v5.4.2.4) Hasleo Emergency Disk media shows that it is using the CA 2023 updated certificate of authority which will be very happy BOOTing after MicroSloth revokes the CA 2011 certificate. I don't know when they started using it (a while back I assume) so I encourage all to update their Emergency Disk media using the current HBS release of v5.4.2.4 just to be sure you will have continued SECURE BOOT functionality.
HBS v5.4.2.1 was using the CA 2023 certificate (20Jun2025)... I don't have older ISOs available without creating them (Deal with it ).
Hi @ Wilders Security Reference the RollbackFrog post 1689 When I installed Hasleo B/U v5.4.2.4 on 30 September 2025 I updated the emergency disk in my USB drive. At that time I was offered, as usual a choice of downloading Win PE from Microsoft.com or an internal WIM. Chose the former. After creating the new USB Recovery and on boot up the following showed on the Black screen "UEFI Disk 3.0 PMAP Partition 1 (15.5gb)." This is what I clicked on to boot. It worked fine. On the 2nd October using a well outdated (May 2025) Hasleo USB Recovery Drive I decided to update it to version 5.4.2.4. The process was different if not unusual. I was NOT offered the option to download Win PE from MS.com or the WIM version it went straight into producing the Recovery Drive. The drive boots and shows the correct version i.e. v5.4.24. It also boots into Win PE, nothing appears amiss although I haven't done a restore with this USB. On boot up on the black screen the following shows "UEFI 0.00 Partition 1 (4gb)" The two USB's are from different manufacturers, one circa 15gb capacity and the other circa 4gb My questions are 1) Why on the 2nd October 2025 was I not offered the opportunity to download WinPE? 2) Why is the boot information so different? i.e. "UEFI Disk 3.0 PMAP Partition 1 (15.5gb)." "UEFI 0.00 Partition 1 (4gb)" 3) Does this imply a problem? Thanks Terry
Hi @TerryWood - I have to run at the moment but will explain question #1 later. Essentially, question #2 implies no problem, just a difference in UFDs.
Hi @ TheRollBackFrog Thanks, I await your comments with real interest. Also I was not offered the opportunity to inject Drivers nor was it mentioned about formatting the USB Drive. To be clear I am creating the USB Flash Drive as a unified operation, not by first creating the ISO and then exporting it then creating the Flash Drive. Something has definitely changed and I have tried several different Flash Drives and the Hasleo Emergency Disk now goes straight into "Proceed" creating the Flash Drive without any of the precursors of recent versions that I am used to. That's why I am concerned that something is amiss. Thanks Terry
There's nothing amiss (well maybe a slightly different process would help) When Hasleo first builds a "fresh" Emergency Disk" (ED... ISO or a UFD), it needs to do 3-things. 1) It needs to get the needed WinPE basic structure. For that, it asks you to download the needed files. When you say YES to that, it asks whether to get it from MicroSloth or use Hasleo's off-line PE file (.OPE). Once you choose, it creates a the needed "base" WIM (Windows only) in the following folder... ---Program Files\Hasleo\Hasleo Backup Suire\bin\WADK\Windows Preinstallation Environment\amd64\winpe.wim 2) Once that's done, it integrates the current HBS version into its image (the "building" function) then saves a file called "WinPE.iso" in its BIN folder. 3) It then offers to build your ED either by creating your requested ISO or your selected UFD. That's the jist of what it does. Now, if you ask for another ED, it looks to see if it has a created "WinPE.iso" in the BIN folder, if it does, it uses that to make your newly requested ED... it won't ask any questions other than whether you want a UFD or ISO. Since it always uses "leftovers" when it builds Emergency Media (it's BIN-based "WinPE.iso" if there or the previously downloaded "base" winpe.wim), if you want a complete fresh rebuild of your ED, you must DELETE the following file and folder prior to starting your ED creation... ---Program Files\Hasleo\Hasleo Backup Suite\bin\WinPE.iso ---Program Files\Hasleo\Hasleo Backup Suite\bin\WADK\Windows Preinstallation Environment\amd64\ This will eliminate all the "leftovers" from any BUILD process. Hasleo using "leftovers" is just trying to eliminate download & building times to speed the user request up. In the process, it creates your described anomaly. This is really only required when you're working with an existing installation and creating new EDs... a program update usually clears all the above stuff out so it starts nice and neat when you do its first ED build. Hope this gives you a better understanding of how Hasleo builds its EMERGENCY DISK
...and remember, if you're using a really old HBS build, you may not have the ISO with the proper CoA (2023 Certificate of Authority) from MicroSloth to allow SECURE BOOT to work after the 2011 CoA revocation occurs.
Hi @ TheRollBackFrog Thanks for that. A really clear explanation. What I cannot understand is why it is so embedded in me that I have seen the "full" build process every time I have renewed my Emergency Disk. Todays "shortened" run is the first time I have never seen the various offers of updating from MSoft.com, formatting, injecting drivers etc. It is as though the two folders you mention above have never been there or have been deleted every time. What matters is that I now know. I thank you for that. Since I have updated my emergency Disks regularly the problem of "proper CoA (2023 Certificate of Authority) from MicroSloth to allow SECURE BOOT to work" will not occur (hopefully). Thanks again for all your effort. It is appreciated Terry
@TerryWood - if your ED rebuilds mostly occurred after an app update (that's when most users do it), you will always see a "building" process (the 1st time under the updated app) due to the fact that the update removes all those "leftovers."
@TheRollbackFrog All very considerate vital info and always good points shared. We thank You for that. On the home front this way, i have been ruthlessly burning up MERGE with incrementals for weeks. Manually on a daily basis with all sorts of combinations of SIZES. A real quality space saver if a user prefers that particular feature MANUALLY too! A very useful and reasonably Fast feature. Good to learn Hasleo is also way ahead with the (Secure Boot) MS Certificate change/update for boot media. New Rufus too for that already. https://github.com/pbatard/rufus/releases/tag/v4.11
WOW! There's every indication that HASLEO BKUP SUITE has evolved where it is an ALL PURPOSE solution to maintaining reliable backups and restore with peak efficiency. It used to be a headache backing up my UFD Tools and Programs on flash drives only to have one or more malfunction with all data lost. I recently experienced a blunder of my own making by mistakenly inserting one of those Pen Drives believing it was the right one using Rufus and had to abort fast. It took Hetman Partition Recovery to safely/effectively peel off the contents since only the header was damaged. NOW i use HBS Files Backup Feature to image ALL my vital plug in USBs.
