Every time I run SyncBackSE (licensed copy, 8.5.26.0 64-bit) on Windows 10 (properly updated), the UAC is triggered and pops up the dialog.
What should I do that I am not required to confirm it every time? Beside the point I am quite certain than SyncBack is NOT making changes to OS with my backups.
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.
- If you are entitled to technical support then please submit a support ticket. Please do not post the same question to the forum and also via a support ticket. Once again, 2BrightSparks does not provide technical support via this forum.
SyncBack and Win10 UAC on every run
-
cliffhanger
- Expert
- Posts: 606
- Joined: Tue May 31, 2011 5:59 pm
Re: SyncBack and Win10 UAC on every run
Hi, see this Knowledge Base article
Note that the wording* of the UAC prompt is Microsoft's choice, and more accurately would state that the elevated privileges (see KB) being requested potentially give more scope for changes to the system than a program running non-elevated would have. It doesn't necessarily mean SB is asking to make any changes right now, but the MS prompt wording can give that impression.
PS the KB article refers to different wording* of the UAC prompt, which (IIRC) is how it prompted in Vista. The wording (as you probably know already) is 'Do you want to allow...' in Windows 10
Note that the wording* of the UAC prompt is Microsoft's choice, and more accurately would state that the elevated privileges (see KB) being requested potentially give more scope for changes to the system than a program running non-elevated would have. It doesn't necessarily mean SB is asking to make any changes right now, but the MS prompt wording can give that impression.
PS the KB article refers to different wording* of the UAC prompt, which (IIRC) is how it prompted in Vista. The wording (as you probably know already) is 'Do you want to allow...' in Windows 10