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

[fabs]

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!

 

[GTP]

Oooh! The excitement builds!

 

[Mr. Ingram's Computer Repair & Shoppe]

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.

 

[fencepost]

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.

 

[Slaters Kustum Machines]

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.

 

[fincoder]

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.

 

[GTP]

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.

Shame on you! Get a copy today and start enjoying the benefits.

 

[NJW]

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.

 

[fabs]

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!

 

[Porthos]

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.

 

[fabs]

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 ?

 

[NJW]

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.

 

[fabs]

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

 

[fabs]

There has not been any trouble with this recompiled version (nothing changed inside the code!). 6.13.4.31583 is online!

 

[NJW]

Hello,

Somewhere between 6.12.0.31411 and 6.13.4.31552 (sorry, I don't have a smaller timeline – maybe the change from 6.12 to 6.13?), the template for HTML reports has changed, putting the operating system detail above the logo banner. Could this be changed back to the previous design, please?

 

[fabs]

Hello,

Somewhere between 6.12.0.31411 and 6.13.4.31552 (sorry, I don't have a smaller timeline – maybe the change from 6.12 to 6.13?), the template for HTML reports has changed, putting the operating system detail above the logo banner. Could this be changed back to the previous design, please?

I made a coding mistake and put this information at the wrong place in the installed software HTML report, due to some missing HTML tags. That's not really a big deal since the program still works. Anyway, I have fixed something much bigger in V7 that affects V6 too, so, there will be a V6 maintenance release:
The program could not deal with machines with customized default user profile: the detected paths from the registry were from the profile that has been used to customize the default profile.

This little design issue will be fixed in it as well.

 

[fabs]

A Fab's AutoBackup 6 Pro maintenance update has been released.

Change log for V6.13.4.31602:

Fixed :
- The program could not deal with machines with customized default user profile: the detected paths from the registry were from the profile that has been used to customize the default profile.
- The operating system information was misplaced on the installed software HTML report.


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).

 

[Larry Sabo]

Thanks @fabs Nice work re the free Emsisoft license!

Anyone else having a problem activating the free license that came with Fabs 7 Pro? My NFR license to Emsisoft expired today and I apparently successfully installed the free EAM license two days ago. It said after the license update, 356 days remaining on the license. Today, I got a prompt to renew the license and the renewal using the free license failed. The License details window showed the NFR license key greyed out and the GUI froze and refused to be end-tasked. Had to reboot the system, after which Windows defender was providing protection.

I'm not sure where to turn for support -- the Emsisoft forum is very active but I'm reluctant to post the problem there, given the free nature of the license.

Suggestions?

 

[fabs]

Anyone else having a problem activating the free license that came with Fabs 7 Pro? My NFR license to Emsisoft expired today and I apparently successfully installed the free EAM license two days ago. It said after the license update, 356 days remaining on the license. Today, I got a prompt to renew the license and the renewal using the free license failed. The License details window showed the NFR license key greyed out and the GUI froze and refused to be end-tasked. Had to reboot the system, after which Windows defender was providing protection.

I'm not sure where to turn for support -- the Emsisoft forum is very active but I'm reluctant to post the problem there, given the free nature of the license.

Suggestions?

I have just sent an email to Davlat from Emsisoft quoting your message. I hope you do not mind I gave your email address to him so he could contact you directly if he needs to.

 

[Larry Sabo]

Thanks, @fabs.