Before posting, and to avoid disappointment, please read the following:

  • This forum is not for 2BrightSparks to provide technical support. It's primarily for users to help other users. Do not expect 2BrightSparks to answer any question posted to this forum.
  • If you find a bug in any of our software, please submit a support ticket. It does not matter if you are using our freeware, a beta version or you haven't yet purchased the software. We want to know about any and all bugs so we can fix them as soon as possible. We usually need more information and details from you to reproduce bugs and that is better done via a support ticket and not this forum.


SyncBackFree is the freeware version of SyncBack. It is *not* an evaluation version of SyncBackPro/SE.
Post Reply
Posts: 1
Joined: Thu Sep 06, 2018 9:32 am


Post by aptisman »

I have just started using SyncBackFree on Win 10.

I have set up a number of profiles to run daily in the small hours, and they do seem to be working.

However, the Last Run and Next Run times are all 24 hours behind what they should be. I have tried to fund a reason but no joy so far.
Posts: 606
Joined: Tue May 31, 2011 5:59 pm

Re: Times

Post by cliffhanger »


Are you leveraging a copy (instance) of SBF that has been open in the background overnight to check the runs were successful? Note that a Windows Scheduled Task (created at your request by SBF when Scheduling a profile) opens/uses/closes another separate instance of the SBF program to run scheduled profile/s, so an already-open idle instance may get out of step in regard to polling recent info (occasioned by the scheduled activity) to display to you. Try pressing F5 in SBF to refresh the SBF GUI (or close & restart your foreground copy of SBF) and see if the values for LastRun & NextRun update?

If not, then all I can think of right now is some issue with your PC whereby the system time (viewed in isolation) is accurate but the system date is 'one day wrong' and you didn't notice. This should be hard to achieve these days, as Windows 10 by default checks the system clock with NTP time servers across the internet, so this shouldn't ever happen, but hey, systems are not foolproof. It may be faintly possible you have accidentally specified a regional setting that is 24 hrs different to your real regional time/date, but that would need careful planning to achieve and I guess only possible in the case of certain regions near the international date-line.
Post Reply