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.


For technical support visit
Post Reply
Posts: 7
Joined: Wed Jan 23, 2019 3:40 am


Post by jmorgannz »

Hi all,

I use SyncBackSE to backup my entire OS drive.
I know this is a bit redundant as you cannot recover an OS install from a file-level backup - but it helps my peace of mind.

One thing that annoys me is quite frequently an Windows update or a Microsoft store update adds new files to my drive, and the following backup fails with access denied messages.

I then have to manually modify the backup profile and add exclusions to those specific files to my filter list, which then triggers a full re-scan on the next backup.

Does anyone have any creative solutions which will give SyncBackSE the power to back these files up - if only to stop me having to manually exclude them all the time?
In some cases even *I* cannot view these files, which is irritating to say the least. I should be free to back up every file on my drive.
Posts: 15
Joined: Sat Mar 12, 2005 5:05 pm

Re: Backing up SYSTEM and TRUSTEDINSTALLER files

Post by des421 »

I've used SBP for years to maintain bootable clones of W7 & W8.1 systems. The VSC Service will take care of Open/System/Locked files and allow complete registry copies. But sure enough Windows Defender or this Trusted Installer guy (whoever he is?) occasionally replaces fortunately a few files that nothing I know of can copy? Again fortunately SBP's great logging clearly identifies these, for which I have been able to manually delete the old on the destination and replace them with copies of the new from the source, removing the conflicts. And occasionally the system will delete a few files that were on the source during scan but gone before the copy, which can be ignored/only indicated via settings.

Post Reply