Well, for instance... Hasleo uses a WinPEv10 for both Windows 10 & 11. Why, 'cause it works for both without issues (Win11 is really Win10 regardless of what MS tell you ). The only difference might be some xtra included drivers in the WinPEv11 that don't exist in the WinPEv10... but the app allows you to add what you need during the build. As soon as a tried and tested WinPEv11 is available in the wild (the originals are available now but really need some more hang time in the wild before they're really accepted), I'm sure Hasleo will make it available via the Downloader.
Well, when you update the Hasleo application and try to produce any sort of new Recovery Media (LIVE restore, USB/ISO or BOOT menu), it will force a rebuild of the internal ISO it uses for these types of operations. It does this to insure you have at least the application changes in the new recovery media provided by the application update. They have been asked to provide guidance as far as existing Recovery Media are concerned (like Macrium does) whenever the app changes... they are considering this.
Well, the guidance I personally use is as follows... if the release notes don't reference major changes in formats (like a new imaging streaming/compression scheme) or solutions for problems that I, personally, haven't been experiencing, there's probably no need to update your existing Recovery Media. If those same notes reference some new improvement in the functioning of the app that you would like to use with the Recovery Media... sounds like a time to update that Recovery Media. As mentioned earlier, most of the time I only use ISOs/WIMs in my recovery operations so updating those is really no big deal when new releases come out (I recreate the ISO using my resident OPE file, and extract it's WIM if I need a new WIM file), regardless of the magnitude of changes involved. If I really need a "pure" USB-based recovery media, I make one utilizing my current ISO via "Rufus" or just use Hasleo's Emergency Disk USB builder... results are the same.
Appreciate the procedure details you use on your systems. Works well on this end. Obviously on my lower end 8.1 systems at least where implementing metal spindle drives which are slower, yet the HOT RESULT is still more than adequate. Even ever more so (Plus Faster) with newer technology. Absolutely enjoy the setting of adding the one-time OR you can just allow it to stay on the BCD. No biggie really but the 1 time Recovery function is simple and the Emergency Disk UFD provides double the option of entering the imaging program. Definitely will keep an eye out for any HASLEO changes where concerns your mention above.
@TheRollbackFrog Okay im lost on why this Imaging Program like Hasleo wants us to install Dokan. I read the Dokan Github page and none of it is making any sense to me. Not a single other imaging program needs go to that extent. Something about a Dokan driver that supplements Hasleo when it comes to mounting a saved image?
Not a saved image, a saved Hasleo File'n'Folder image only. I haven't used it yet but I assume it allows you to mount their F'n'F image just like a System/Disk/Partition image as a virtual disk. They can already do this with their System/Disk/Partition images but prior to Dokan their method of F'n'F mounting/extraction was very proprietary... Dokan makes it look like that type of virtual disk mounting. Dokan is an OpenSource implementation of virtual disk mounting that can handle Hasleo's F'n'F image format.
That i can understand @TheRollbackFrog - But the same is already accomplished with a disk image isn't it? I mean it's already settled any File & Folder in an image can be Mounted, browsed, copied etc. from a saved imaged. I suppose it is a singular feature for ONLY File/Folder selection totally aside from a disk image. Thanks for clarification.
@TheRollbackFrog - Can you encourage Hasleo to offer a PDF of this program's Guide? All pertinent detail on their site is accurate and simple in detail but a PDF a user can download and read and study would help too.
I kind of dislike to double post like this but Hasleo Backup Suite this time is truly exceeded my highest expectations. Oh sure on a 500GB SSD etc it performs as you would expect. But recently i been dealing in those older outdated (WD-Toshiba Terabyte capacity at least drives) AND not only that, but try this over-performing imager, with that in mind, backing up/restoring metal platter spindle hard drives w/o error or stalling! Not only that but it nudges itself ever so deliberately-seamlessly and to some surprise, completely with an entire library of 1930's, 40's, 50's and other data of films in various formats. I have seen a good share of STOPS occasionally with Imagers, mainly due to my tight security set up you sometimes forget to allow for where that ANY imager would hit a snag. I selected my worse metal hard drive almost full, and while it will accrue gobs of time to make a Full Disk Backup (with any imager), Hasleo just blows me away with not just feature sets in it, but fully capable of handling our antique drives too. Full at that. This is with Windows in full operations and unless i'm seeing things, soon as it completed, it even can back up ongoing work. I tested this soon as the imaging was successful and THAT took me by surprise because i always assume a volume is supposed to be locked at a point-in-time and any work you conduct after that would be ignored. It may have just overtaken my long prized and reliable Aoemei Backupper as a primary imaging solution. Sharp piece of work!
@EASTER, ewww, Aoemei Backupper? Really? That's a horrible imaging app. There are at least 35463 other apps that are better and more reliable. First the avatar change, now this?
Are you serious? I been using Aomei Backupper well over a year now and totally Error-Free. And pretty fast restore times to boot. But anyway being a staunch skeptic that seriously scrutinizes Imagers (you must with a group of highly active 8.1s), Hasleo Backup Suite is really putting the foot to the pedal on QUALITY and FEATURES and that with pretty good efficiency. Now there's your reliable
Oh, it's awesome! The only things it's missing, from my perspective, is a driver that prevents image manipulation/deletion; kind of like Macrium Reflect or Protectit.
Secure Folders 1.0.0.9 even if old and not supported anymore IT IS very stable and good! https://www.softpedia.com/get/Security/Security-Related/Secure-Folders.shtml You can protect folders (even in safe mode) and optionally permit only some specified applications that can access the folder. This is how I protect folder in which partition backup images are stored. Hided, only Total Commander and backup application can access it. Windows can't show it, in command promt can't go there, a.s.o. I know it's not the best solution but HASLEO already offered US a very strong, good and reliable program. And also FREE on both Windows PCs and Servers. I'm not sure if it's free also for companies too ..
Oh this is very cool! Thank you for for this. I'll have to do some more testing with it but on quick glance, it seems to do just what I want.
@n8chavez You can get further info on this and perhaps discuss any questions on it in the thread here. https://www.wilderssecurity.com/thr...ct-folders-and-use-as-anti-executable.369503/
@TheRollbackFrog and others. PROBLEM: (Not Serious) But, here is what for some might or might not be an issue to them. After engaging HASLEO for usual "Live Windows" backup images. REPRODUCIBLE: Most users of this magnificent program won't or don't manually STOP 2 Hasleo ongoing running services after doing an image OR simply use it's monitoring continuously for personal preferences of it's features. But i do to keep my services resources list minimum/ limited. It's function I DO keep AUTOMATIC Since on reboot it auto starts normally. ISSUE: If a user does terminate both Hasleo Backup Suite Service AND Hasleo Backup Suite Image Mount Service at any time (manually), for purposes aforementioned, then decide within the same session to conduct an Incremental, Hasleo's main executable (or shortcut) throws an error (for obvious reasons) until a user manually restarts those 2 accompanying services. In other words, should those 2 services become terminated after closing Hasleo's main GUI, Hasleo will not communicate to reactivate them on it's own. I hardly doubt anyone even bothers, BUT, i wanted to bring this up since with most Imagers, even if their services have been stopped, upon restarting a GUI most if not all others immediately detect it and restart it instead of simply issuing an ERROR. Hopefully someone can relay this to the devs and also hopefully a easy fix/update. I didn't want to overthink it since most users will never terminate Hasleo's services even after doing a Live Windows. But for sake of precision or otherwise, i experienced this and it was as simple as restarting them again. A newbie or less familiar user who watches over their services list i would assume would quickly realize all needs done is to restart them again and your back in business.
If you switch services to manual startup mode instead of automatic, they will not start when Windows boots. If you now start the program as an admin, it will start the services. This worked successfully in previous versions of the program. Restoring from a backup is always more interesting than creating one.
Question: What would be a reasonable amount of ongoing common Incremental's using this Hasleo Backup Suite before rolling up the chain or creating a fresh new Image Backup?
I don't even think I'd mess with any of that. It's just the way I prefer it, but I'd eliminate anything possible that could go wrong. Meaning, why make incremental and then combine those into a full image when creating a full image every X and then differential images every day? Skip the incremental and skip the combining. If there's one kink in that chain, one error in any of those incrementals, you're screwed since they they all rely on each other. That's not the case with differentials.
