Aomei Backupper Error 4110
So I've been using version 2.2 since January of this year with no
problems whatsoever, but when 3.0 came out I decided to give the update a
go (big mistake) despite non-stop issues I've seen from people since
2.2. The minute I did that my daily backups instantly refused to verify
with: Error 4110 failure to decode, whatever that means. I've been
backing up my Corsair Neutron SSD > External WD 2TB drive perfectly
fine before the upgrade and then it suddenly wont verify any backups
after the upgrade.
I tried downgrading to 2.8, 2.5,
back to 2.2. Now all of them are broken in the same manor. Version
doesn't even matter anymore. Tried googling the issue and looking
through the forums, with no real solution to the problem or what the
problem even means. One solution said they had luck with turning off
compression. Did that and it worked for a few daily backups and then
today its spitting out the Error 4110 again and any backup now refuses
to verify. I've tried mounting this failed backups and I just get a
blank unformatted drive when over the past couple of days the image
would load and I could browse through it like you normally would.
WHAT
IS GOING ON!? I don't feel like I can ever trust the product anymore
even if I manage to fix it because the confidence has been destroyed.
I've used about a dozen products through testing over the past 3 years
and this one seemed like the best, except this is the only program I've
used that has ever given me these serious issues. Not verifying is
fine, but when mounting and no data is there when this happens, that's a
problem.
I've tried restarting the machine multiple
times. I've uninstalled and reinstalled various versions countless
times. I've ran chkdisk with no errors reported. Ran a defrag on my
external. Ran HDTune on both drives. Nothing is popping up and since
this only started after upgrading from 2.2 > 3.0 and now for every
version it leads me to believe that something is broken on the software
side of things. I've tried all the tips from the threads I could find,
but it seems like nobody has an answer or even has this problem, let
alone the details on what this error means are vague.
Comments
I am starting to agree with you, trust is evaporating at high speed!