We found the five products/applications the best free backup software for both personal and home users, without too much learning they can easily operate the software and make a dependable backup of files, folders, OS, or even hard drives to any desired location. In case of any unexpected data loss or system corruption issue happens, an existing backup image can save the day!
In fact, Microsoft Windows 10 has File History to backup your device and files for free. But Is Windows 10 backup any good? As is known, File History is an automated file backup system on Windows 8/8.1 and Windows 10. With this built-in tool, you can do more than just restore previous versions of files; It's a competent backup tool for your needs.
I've just come across Ease US Todo Backup (free) and it seems like a godsend ... I've recently had one or two near-disasters with W10 files and in Linux have come the value the peace of mind you get from a well-configured Backintime setup.
I've been experimenting with Ease US for about a day and I've also looked at what documentation I can find ... but I'm still rather puzzled by two options and would really like to find quite a detailed account of the difference between ticking them and not ticking them.
Firstly, for a given backup, into schedule options, "Appoint daily first backup as Full" (or it can be "Differential"). I don't understand what this is about or what it means to tick it or not tick it. This option appears active (not greyed-out), whether you are doing one daily backup per day or multiple incrementals (for example, every 10 minutes). What does it mean if you untick it? What does it mean if you tick it?
Secondly, under Image Reserve Strategy, the option "Don't delete the first image". Again, say you're doing a daily incremental plan, but actually doing an incremental every 10 minutes, and you've set it to only preserve 5 backups maximum, does this mean that, with this ticked, the very first image/snapshot that you create just after midnight will be preserved for the whole of the next 24 hours? Whereas unticked means that in fact your oldest snapshot will be one of how the files were 50 minutes previously?
Generally, with an incremental backup plan of the kind described in the last para, I just don't really get how the full backup/incremental backup business works. At the moment there seem always to be two full backups in that folder, but that may be to do with the fact that I keep editing the plan... it appears that a full backup is then done after you have edited a plan. Possibly the last full backup is being "mutated" by merging with later incrementals ... but from the time stamp ("last modified"), actually this doesn't appear so.
For example, if you don't click "Don't delete the first image" it is in fact possible that all files involved in your entire backup plan become completely invalid! I could scarcely believe that the Ease US designers would allow such an outcome, so had to double-check with the engineer about this, but it is certainly the case: i.e. your first (full) image gets deleted, leaving only differentials/incrementals, which are rendered useless after the deletion of the first image, as per the Reserve Strategy you have defined (automatic deletion of old images).
"It is not 100% guaranteed that disaster will happen, because users can create many full backup images.If they have many full backup images, then there is no need to keep the first backup image.For example, they may create a full backup image every week.A few weeks later, there are multiple full backup images, then there is no need to keep the first one."
Regarding the other option, "Appoint daily first backup as Full/Differential". The explanation for this is that is essentially a way to "override" your "incremental" setting... but only for the first backup action of the day. So you've set things to "incremental"... every 10 minutes. A new day then starts (midnight or whenever), and instead of an incremental image being created referencing the previous day's backups, a new full backup image is created (or differential if you set it that way... which would be quite obscure).
This, it seems to me, is useful for something like a monthly plan: I would feel quite nervous/dubious about relying on incrementals/differentials referencing an image from months and months ago. For most purposes it should hopefully be possible to find time (middle of the night or whenever) to do a full backup once a month. This option enables this sort of plan to be automated.
Having used Easeus ToDo Home for a few years I can tell you that is NOT how "don't delete first image" works. Let's say you tell it to preserve 2 backups and you checked to not delete the first image. When it is time for Easeus to delete older backups, it will do so but will NOT delete the first Full backup. It deletes the incremental or differential backups associated with that first full backup but does not delete the original full backup itself. I have seen this in action and then decided I don't need that original backup and had Easeus go ahead and delete it. I guess there are times you'd want to keep that first full backup, like if it was taken when your system is brand new with freshly installed apps, etc. That would give you a way to start over without having to reinstall your apps.
Unable to attach the original file because after the restore from the MBAM Quarantine because when I tried to launch the Easeus Todo Backup Home (ETBH) program, it would issue a UAC, then try to start loading and just quit with no error message. Rebooting, quitting MBAM, etc., made no difference. I had to uninstall ETBH via Windows and reinstall it. I am attaching the zipped version of the requested file from my new desktop computer ETBH installation. I am sure that they are the same as the old one. I have been using ETBH for years now with no issues. No ETBH updates in the last month or so.
My desktop computer is a Dell XPS 8930 SE, running Windows 11 Pro, fully updated. Bitdefender Total Security (BDTS) is my anti-virus solution. Both MBAM and BDTS have the recommended exemptions so that they have played nicely in the same sandbox for many years.
This one is not triggering any detections on my machine. It also has a different MD5/SHA256 than the one reported in your log.
Try to just copy out the exe somewhere so not have these warnings while trying to start the program.
Both files were the same. That is OK though, I was able to get enough from other sources to grab a decent amount of files to create a "prevent fp definition". Always nice when one can get the original file causing the complaint though when possible.
Thanks for your reply. It is curious that the files were the same . . . ? I only run ETBH every second Friday. In the alternate weeks, I run Macrium Reflect Home, so I have no idea when the FP started occurring. The 3rd of February was the last time I ran ETBH on both of my computers.
Looking at the log it seems to be a RTP (real-time protection) event.. so it would have to be "running". It wasn't a result of a scan.
If it was tagged previously, you should see it in quarantine unless you dump that out regularly. I think also that is pretty common software so I would kind of expect to have more reports. Whatever version that particular file was, it was not a very common one because I can't find that MD5 anywhere. Curious for sure.
On the machine that had the detection...
You might be able to find a copy that was there before MBAM tagged it by looking at your shadow copies if you have that enabled. (If you don't, no worries)
I can't be 100% sure it will work for Windows 11.
10 or earlier it does.
Right click "Program Files (x86)" > properties> previous versions> pick closest date to today before MBAM quarantined the file. > "open".
drill down to: EaseUS\Todo Backup\bin
Might be able to copy out the TBConsoleUI.exe to your desktop or something to upload it.
Exit out of previous versions window.
Like I said, it is a common program so I am curious to see what is so different about that file.
Might want to delete it from sendspace in case there is any sensitive info in the file.
This looks like a kernel dump file of some sort mashed up with TBConsoleUI (when I compare it to other common ones)
I always create a Restore Point just before launching my backup program on any given Friday. ETBH had not been used since 2023-02-03, so there should have been no updates or other modifications to its files.
Yeah .. I'm not sure what happened here. The file you just uploaded (from 10 min before ETBH launch) is the same as previous one you uploaded to sendspace.
I can see why MBAM heuristics would have tagged it though .. parts of it are corrupt (icon is borked, can't view much for version info, etc) and does not look like a normal executable at all. There is a bunch of what looks to KErnel junk all through it. (I don't know how else to describe it)
MBAM would indeed see anomaly when you tried to launch it. Even if MBAM didn't tag it, it would likely shut down with an error anyway.
Might want to look at say restore points from say last week or last time you did a backup to see if that one is normal.
Then check your system event logs, application event logs and see of there is something listed there that crashed. (just trying to narrow the timeline a bit)
Something else with the corrupt one .. it seems to have been packed with "private exe protector". I'll have a look over the weekend. I have to rebuild my VM to play with unpackers lol.
I will let you know what I find.
I'm hoping someone can offer some assistance - I'm trying to restore a PBD backup file (containing a full OS and system backup - made using EaseUS Todo Backup) to a blank/new VirtualBox VM, and can't seem to get anywhere. The PBD file was originally on an external USB drive, and while I could get the blank/new VM to see the external USB drive via enabling USB in the VM settings, it then wouldn't see the WinPE ISO file I'd attached to the VM in order to be able to do something with the PBD file.
c80f0f1006