Fab's AutoBackup 6 Pro - a must have tool for techs

- There could be some warnings about file dates differences (one second) between source and copied files when copying to a FAT, FAT32 or exFAT drive.
Thanks Fab. I've had these warnings a lot and have been meaning to report it but couldn't figure out the conditions that made it occur. My backup drives aren't FAT so I don't know what caused it for me, but hopefully it's fixed anyway.
 
Great work Fabs, look forward to version 7. This tool I have used soooo much and been so convenient. With customization to suit your own business is great ie - branding is great. Just wish I could change fonts type lol.
 
Fab's AutoBackup 6 Pro V6.13.4.31543 has just been released.

Change log:

Fixed :
- The read-only, hidden and system files attributes were not copied.


Grab it from your orders history's details on the shop's website or using the bundled updater tool (click the "Fab's AutoBackup 6.X is available" link within the program and get the updated files).
 
Fab's AutoBackup 6 Pro V6.13.4.31543 has just been released.

Change log:

Fixed :
- The read-only, hidden and system files attributes were not copied.


Grab it from your orders history's details on the shop's website or using the bundled updater tool (click the "Fab's AutoBackup 6.X is available" link within the program and get the updated files).
do you copy owner as well?
 
Fab's AutoBackup 6 Pro V6.13.4.31552 has just been released.

Change log:

Fixed :
- The copy process did not even start when performing a data transfer while the source user profile was on the same drive.


Grab it from your orders history's details on the shop's website or using the bundled updater tool (click the "Fab's AutoBackup 6.X is available" link within the program and get the updated files).
 
  • Like
Reactions: GTP
Another (and probably the ultimate) Fab's AutoBackup 6 Pro has been released.

Change log for V6.13.4.31582:


Fixed :
- Very rare error message when setting back files attributes.


Grab it from your orders history's details on the shop's website or using the bundled updater tool (click the "Download Fab's AutoBackup 6.X" link within the program and get the updated files).

Next time, a new forum thread should be created. Stay tuned!
 
Well, if the 7 is bootable but ugly you can likely run the Win10 upgrade then use any of several tools to back up activation state, then clean reinstall (or reset clearing all data) and restore the backed up activation. I'm not sure that'd work if it was backed up on 7 and restored on 10, but it might.
 
I have never used Fabs. I would buy it in a heartbeat if it had support for moving Office 2007/10/13/16 from one OS to a nuke/pave to new one. I do a lot of Vista/7 to Win10 and moving over Office 2007/10 would be groundbreaking amazing.
Moving Office 2007 is no different than supporting Windows XP or Vista. It just shouldn't be done, but 2010 is still valid even if getting long in the tooth.
 
support for moving Office 2007/10/13/16
It does automatically extract Office 2007/2010 product keys and transfers Outlook settings/data. Obviously transferring the application software itself isn't possible and never will be.

The only extra Office feature that would be nice would be to extract the Office Account name to help the re-activation process. I find that many customers forget what email address they used to register Office 2016/365.

This extra feature, and maybe also the default apps settings (e.g. default browser/email), would help a lot in setting up a new or nuked system as the customer previously had it. I understand that the Office account and defaults apps would need to be applied manually after the software is reinstalled, but just having the information in the log or another report file would be very helpful.
 
Another (and probably the ultimate) Fab's AutoBackup 6 Pro has been released ... log for V6.13.4.31582:
On a clean install of Windows 10, Defender has just removed this version during a restore, identified as Trojan:Win32/Critet.BS (this is a new definition in Defender, introduced 16 March 2018). The AV action did not prevent the restore process from completing correctly.

The executable is not detected as a threat when tested individually, so I guess it was the action of writing files all over the place that triggered it.
 
On a clean install of Windows 10, Defender has just removed this version during a restore, identified as Trojan:Win32/Critet.BS (this is a new definition in Defender, introduced 16 March 2018). The AV action did not prevent the restore process from completing correctly.

The executable is not detected as a threat when tested individually, so I guess it was the action of writing files all over the place that triggered it.
I am about to submit the program as a false positive but I see that my Windows Defender with definitions version 1.263.652.0 created on March 17th does not flag it while doing a huge file transfer. Can you update your definitions and try again please? If it is still there, I will send them the program for analysis.
Thanks!
 
On a clean install of Windows 10, Defender has just removed this version during a restore, identified as Trojan:Win32/Critet.BS (this is a new definition in Defender, introduced 16 March 2018). The AV action did not prevent the restore process from completing correctly.

The executable is not detected as a threat when tested individually, so I guess it was the action of writing files all over the place that triggered it.
Sounds like something in the backup itself triggered it. I see it happening all the time. An infected file that was saved and then restored.
 
My bad, I was using V7 for the tests and we are on the V6 topic. Do you confirm you have the issue with V6 ?
 
Sounds like something in the backup itself triggered it. I see it happening all the time. An infected file that was saved and then restored.
Nope, it was autobackup6pro.exe that was quarantined (and removed from my USB stick).

Do you confirm you have the issue with V6 ?
Yes, V6.13.4.31582. Note that a static check (i.e., right-click and check with Defender) doesn't show a problem. The executable was quarantined after the end of a restore job – the restore was finished, Autobackup window still open, then the Defender alert popped up. I can only imagine that Defender detected that autobackup6pro.exe had written many files into personal directories – in other words, the kind of thing that ransomware might do. If that is the cause, it might be difficult to work around it.

I don't have a restore candidate that I can try it on at the moment, but I'll try to put something together later today.
 
Nope, it was autobackup6pro.exe that was quarantined (and removed from my USB stick).


Yes, V6.13.4.31582. Note that a static check (i.e., right-click and check with Defender) doesn't show a problem. The executable was quarantined after the end of a restore job – the restore was finished, Autobackup window still open, then the Defender alert popped up. I can only imagine that Defender detected that autobackup6pro.exe had written many files into personal directories – in other words, the kind of thing that ransomware might do. If that is the cause, it might be difficult to work around it.

I don't have a restore candidate that I can try it on at the moment, but I'll try to put something together later today.
I had the issue too when doing a backup. I have sent it to them. Now, it's in their hands! Beside it, I can try to make another build and test it. If it does not get shot, then I'll release it
 
  • Like
Reactions: NJW
Back
Top