More
Administrator prompts
QuickInstaller always runs at your normal permission. When a job needs administrator rights, Windows shows its standard permission prompt (UAC). You will not see a prompt for anything that does not need one.
When Windows asks
Expect a prompt when QuickInstaller:
- installs or updates an app for all users, or into a folder Windows protects;
- updates a portable app that lives in a protected folder;
- removes an all-users program entry, or stops an app that is running as administrator;
- saves a schedule that applies installed updates.
You will not see one for apps installed just for you, portable apps in your own folders, checking for updates, or browsing.
One prompt, not one per app
QuickInstaller starts a small, separate, digitally signed helper for the administrator part and keeps the rest of the app at normal permission. The helper has no internet access. Windows is the only place you approve, and QuickInstaller adds no second dialog.
Under Settings, Downloads & installation, Installation behavior, the option Keep administrator access until QuickInstaller closes is off by default. It is on only if you upgraded from QuickInstaller 0.5 with Launch as administrator turned on:
- On: one approval lasts until you close QuickInstaller.
- Off: one approval covers the current batch.
If you decline the prompt, the whole batch is cancelled, exactly like clicking Cancel. If the administrator route is not available for one app, only that app fails and the rest continue.
See fewer prompts
- Turn on Keep administrator access until QuickInstaller closes.
- Select several apps and install or update them in one batch.
- For a long session, start QuickInstaller with Windows' Run as administrator once. QuickInstaller itself still runs at normal permission, and it keeps that approval until you close it.
Scheduled runs never prompt
An automatic update run does not show UAC, does not start the helper and does not pick another account. A scheduled update that needs administrator access is skipped unless QuickInstaller already has that access for the run, and it is tried again next time. See Automatic updates.