@jpcummins - if you're using a manual operation from the established task (Backup button from that task or one of the Action options), whatever the set DEFAULT is, it should stick.
Anyone else having problems with the restore functionality? When i use the bootmenu created from within HBS, the pc reboots and "read the files" ( the bar that goes from left to right) so as to come to the GUI for executing the started restore, it does it twice. The first initial reading is slow, slower than usual, and the second even slower, when that is finished the GUI shows up. So an automatic restore takes a VERY long time. Besides the fact that the program is getting slower for every update. The actual restore is still fast, but everything else in the restore action takes more time now so overall, it is slower now then a couple of versions back.
On the units i upgraded so far to Hasleo Backup Suite 4.9.3 i also have not experienced any issues at all. We are so fortunate to have this product continuing development and outshining some common legacy competitors.
Hi @ Wilders One problem I am experiencing with Hasleo 4.9.3 is that when I try to shut my Desktop down it hangs with a blue screen and Hasleo showing it needs to be shut down. (It wasn't open). It occurs virtually every time I shut down. Terry
Have you waited patiently... Windows sometimes takes a long time to end certain services, which I believe is your issue.
Issue Hasleo 4.9.3 Failed restore So I had to restore my system to May - April today The restore went well. Got files I need, then did restore back to today. but the restore failed, I was using Hasleo boot usb so used a different image, failed and failed message was cant find c/ drive so went to AOMEI Backupper restore perfect
Obvious ISSUE i would say. Good thing you double Image just as i do, and also with Aomei Backupper. Although i yet to have one bad restore from either. I do anticipate Microsoft 24H2 upgrade (when i do) on Windows 11 to introduce some weird issue with an Imager. Which is why i have stocked plenty of Backups pre-24H2 on my Windows 11 boxes. Sure hope it doesn't come to that but it's better to be prepared with a solid contingency plan in case things do go dreadfully wrong.
Hi @ TheRollbackFrog "Have you waited patiently... Windows sometimes takes a long time to end certain services, which I believe is your issue." Thanks for your response. I have no option, but to wait, as you infer it does take a long time, too long. More importantly it doesn't occur with Aomei Backupper or Todo Backup. I suppose the question is is it a Windows problem or is it Hasleo? Thanks Terry
Hi @ Wilders A Salutary Tale I had used Snappy Driver Installer to update my drivers on my Desktop. Everything seemed to go OK since it was my first use. Circa 10 Drivers updated. Two days later I installed Driver Max since it had a good review although it only permits two drivers to be installed per day. I chose two drivers the first one installed OK with no reboot, the second required a reboot. That's when my problems started, On reboot my PC went into blue screen "repair mode" loop. In other words I had bricked my machine. Two days earlier I had created a system image using Hasleo Backup. I the proceeded to restore this backup. Problem solved. A flawless restore!! Terry
I just completed this exercise for the Hasleo Dev team... Reflect X vs Hasleo v4.9.3 ----------------------------- CPU: i7-10700, 8-core/16-thread, 2.9/4.8ghz RAM: 32gB Source disk: NvME M2.2280, PCiE v3 (7-part <1 FAT@102.6mB, 1 unf@16mB, 1 NTFS@66.1gB, 1 NTFS@481.6mB, ------------------------------------------ 1 ext@22.83gB, 1 NTFS@51.02gB & 1 NTFS@974.6mB) Target disk: NvME M2.2280, PCiE v3 MEDIUM compression, no image checks following imaging operation Hasleo v4.9.3: 4m 57s (Image size=83.5gB) Reflect v10: 3m 9s (Image size=71.4) Remember, Macrium REFLECT X is now using an entirely new streaming compression method, when imaging, obtained from a Facebook developer. As a result, the image format (not the method) is now PUBLIC and available to all if interested. ...and I believe Hasleo does not know how (just a guess here) to determine the USED space of an EXT<n> partition, that's why the image is 12gB larger. Macrium REFLECT does know how to do this.
You can wager a guess that Hasleo Devs will at least devote some research from the result. Frankly that margin doesn't move the needle AT ALL to favor Reflect X per speed (and size). I assume the test was focused solely to a one dimensional activity, as in the Imaging side of it only? The real meat and potatoes would be ETA on a Restore IMO. Either way Hasleo Backup Suite continues to outperform expectations locally on this end. Those who follow this Topic, and more recently, likely are aware that i continuously am still pressing the Merge Feature with Incs. With 100% success rate to date. Now most my Merge Tests are a combination of Retention Schedule setting AND Manual on-the-fly situations.
It's always connected for me, when necessary... maybe a firewall problem or MicroSloth availability issue. If you want, you can download Hasleo's off-line WinPE image and select that during your build. I build all my Hasleo PEs/ISOs with this image, it's nothing more than a local version of the stuff you download from MS. The process can be found HERE... when using the off-line WinPE build package it eliminates any downloading requirements from MS when you do any builds.
The restore process has changed very little with REFLECT X... only the imaging process has been sped up with a bit better compression in the resultant image.
I have just made a recovery from Windows and Hasleo has removed my secondary partition for no reason, I just clicked Next-Next-Next. I had to redownload all games, onedrive, etc. Restoring from PreOS or EmergencyDisk results in no problems. the same procedure, Next-Next-Next. Maybe they should make it more dumb--proof.
Yes, and i most definitely agree that ANY image vendor (free or subscription) where they can utilize such improvement with the Compression ratio reduction, and without undo issue are on to something very beneficial. As i see it, the tighter that they can squeeze or in other words, effectively master compression reduction, that particular section of an Imager's Code can by steps prove out that there remains areas whereby efficiency isn't lost while shaving off ETA to complete a reliable disk or partition Image. Macrium REFLECT X has obviously effected a welcome change (for those users), in the course of it's Imaging compression function under the hood. @TheRollbackFrog - Thanks for stepping up and conducting the comparison locally. And explaining it. Do you feel that it's within Hasleo's Dev Researchers to duplicate it?
I just set Hasleo to backup all my drives at once. No chance of losing any partition on restore as it allows you to choose the partition(s) you want to restore from backup
Everybody's experience with Reflect X will be different depending on the hardware specs of their rig(s)... HDDs vs Sata SSDs vs NvME SSDs (PCiE v3 vs PCiE v4) AND MultiCore Cpus (# of cores, # of threads & base megahertz vs Turbo megahertz). This is because both Macrium and Hasleo have taught their app to use as many available cores/threads as possible (parallel processing) to run their particular compression method and output the results to the storage element. This is a natural application evolution as it relates to multi core/thread cpus. Most apps who try and do this will do it logically... compress the data blocks first then write those blocks to the storage. When doing this in a parallel type of method, coordination must occur so the data blocks are written in the proper order... typical semaphore type of coordination. Both Macrium v8 & Hasleo v4 were doing this pretty efficiently. Macrium, with vX, is using a completely different approach to this process... using a new Facebook developed compression algorithm. They are now doing the compression and writing at the same time during the same output stream to the storage device. This is what's given them the new speed increase compared to their previous process method in v8. Can Hasleo duplicate that method? Of course they can... but will they? From previous discussions with their "Dev Team," they are very small, probably less than 5-6 developers. These same 6 developers are responsible not only for the actual development but also for all the regression testing they can supply with such a small group. That's why they are so appreciative of users like me and others bringing product issues to their attention to be corrected... kinda like a forever BETA testing team . At this point I think they feel they cannot rightfully expect users to pay for this product yet until they develop a suitable support structure to ensure its ongoing success... someday, maybe. Technically they are very capable of replicating Macrium's success. The Macrium method is in the public domain from a Facebook developer, I assume its either FREE or at least licensable. Now can such a small team take this effort on? Hasleo/EasyUEFI has many other products, some are FREE and some are PAID perpetual licenses. Those PAID licenses are what currently sustains their work, that's why they have to abandon FREE product development occasionally to run off and fully support their PAID products... gotta stay alive ya know. I don't know whether this team is a night job team (already have day jobs) or just an ongoing computer science effort among really dedicated developers. I do know they've been around for over 12-years, and although apparently being China-based, they've never been accused of phoning home (except for user requested update checks) or infecting Systems with nefarious intent. In my dealings with them I have found them trustworthy, very responsive, and dedicated to their products... those are attributes I truly admire in a Software Development organization, even if small.
Excellent summary on it @TheRollbackFrog. Seems it will boil down to IF the additional time and effort is worth the speed increase with that compression method now implemented within Reflect X for the Hasleo Devs to maybe consider as well. For some user's every reduction second/minute on Imaging will be to their taste/personal preference. Others, or many may not see the difference as an encouragement enough to switch. Either way, any (especially in this case) advancement (such as was with Delta Restore) which can be singled out as an industry advancement keeps concentrated developments driving forward. And that benefits us all. My lengthy experimenting solely on the MERGE Feature now is running into 2 months. I like everything that i have experienced with it to date. No data loss, no slip ups or other distortions. I like to hammer away at such Features so as to settle into a solid reliable result that meets and exceeds expectation. I do a lot of Incs, now sometimes, on the order of several per day manually or schedule those onto a chain that can be auto merged.
@EASTER - you're headed to where I came from . I was a big user of snapshot software (RollbackRX, EazFix) prior to the 2015 release of Macrium REFLECT with RDR (Rapid Delta Restore). Those softwares were quite dangerous in their day (hid underneath the Windows radar for their shenanigans) and, eventually, wouldn't properly support TRIM on SSDs (necessary for proper life mgmt of flash-based storage)... still don't to this day. I would take snapshots constantly when testing software, updating the OS... and even in a virus honeypot when trapping nefarious baddies from the network. When RDR first showed up, it was a blessing. Finally, a disk imaging software that allowed not only for backup (which snapshot apps never provided), but also very fast restore for recent images... almost as fast as snapshot applications. I never looked back. Macrium REFLECT, and now Hasleo, allow me to continue in that environment without worry of any kind. I also perform many unscheduled Incrementals into the main backup image chain for the same reasons mentioned above... and the scheduling/retention of both REFLECT and Hasleo allow me to set and forget and all works as I'd expect it to. I still use Shadow Defender occasionally for things that are needed in a very speedy way, but most of the time it's a simple unscheduled Incremental that provides the protection that I need, and retention mgmt sweeps away the clutter when it's time.
Sure... don't run it on W11 24H2. OK, I know that's not an answer but that's where I am with my main System (W10 Ent 21H2). I also tried on W11 Ent with your same results. I'm workin' on it...
Same on this end. MS rudely decides an attempt to CRUSH what is longstanding been a very vital foundation piece of security for user's/customer's of it.
