How-to
Running Touch Calibration Without Administrator Rights on a Panel PC
Short answer
An administrator creates one Scheduled Task with Run with highest privileges that starts the calibration executable, and the operator triggers it with schtasks /run — no credentials, no admin group membership. Before rollout, pass one test: the calibration window must land in the operator's own session, because tasks stored to run whether the user is logged on or not start programs where no window is visible. If the tool needs a visible crosshair, grant the operator write access to the exact key it saves instead.
On this page
Yes, within one limit Windows itself sets. A standard operator account cannot elevate anything: its token carries no administrator membership, so every path that asks to run as administrator ends at a credential prompt. Task Scheduler is the built-in mechanism that separates the two roles. An administrator creates a task with Run with highest privileges whose only action is starting the calibration program; the operator receives nothing except the right to trigger that task from a desktop shortcut with schtasks.exe /run. One property decides success before anything else is built: the task's logon setting controls which session the program lands in, and only one configuration ever puts its window on the operator's screen. Work in this order — symptom, program, task, trigger, session test, lockdown, persistence.
Read the symptom before choosing a route #
Calibration failing under a standard account has four distinct causes, and elevation only solves one of them. Match what you see first. If the tool runs to completion from an administrator sign-in, elevation is the whole problem and the rest of this article applies.
| What you see | Likely cause | First check |
|---|---|---|
| A UAC prompt asks for administrator credentials the moment calibration starts | The program's manifest requires elevation; a standard token cannot satisfy it | Sign in as administrator once and complete a calibration |
| The tool opens but fails to save, or the touch offset never changes | It writes to a registry key or folder a standard account cannot modify | Run Process Monitor as the operator and capture the denied writes |
| The shortcut fires, Last Run Result is 0, no window appears | The task started in a session other than the operator's desktop | Task Manager, Details tab, Session column: compare with explorer.exe |
| Calibration holds, then reverts after a reboot | The write is discarded at boot, typically by a write filter | Check for UWF or equivalent, then re-test after a second reboot |
What the scheduled task grants #
User Account Control hands a standard account a token without administrator membership, and nothing that account starts can acquire it; the credential prompt is the only bridge. Task Scheduler works from the other side. The service launches the task under the principal stored in the task definition, and Run with highest privileges gives that process the highest token the principal holds. Two properties follow, and both matter on a panel.
- The elevation belongs to the executable, not the user. Whoever can replace that executable or edit the task can run anything as administrator, which is why the lockdown section below is part of this procedure, not optional hardening.
- Highest privileges of a standard account is still standard. Setting the task to run as the operator changes nothing; the principal must be an administrator account. The operator's trigger is a permission on the task object, not group membership and not a password.
Find the exact program to elevate #
The task must launch the same file the operator launches today, so take the path from the running process rather than from a menu entry.
- Sign in with an administrator account and launch calibration exactly the way the operator does.
- Open Task Manager, Details tab, right-click the process and choose Open file location; note the full path.
- Right-click a column header, add the Command line column, and record any arguments the launch passes.
- Record the program's working folder as well; some utilities load files relative to it.
- If calibration is a control-panel entry or a panel-specific utility rather than a standalone program, take the real executable from the live process. If no executable can be isolated, the task has nothing to target — use the permission decision in the session-test section instead.
Create the task with highest privileges #
- Sign in as administrator, press Win + R, enter
taskschd.msc. - In the Actions pane choose Create Task..., not Create Basic Task; the basic wizard has no highest-privileges option.
- General tab: a short name with no spaces — TouchCal is used here as an example name. Under When running the task, use the following user account, confirm an administrator account, preferably a dedicated local one. Tick Run with highest privileges. Set Configure for to Windows 10 or Windows 11, whichever the list offers.
- Actions tab: New..., action Start a program, browse to the calibration executable, paste its folder into Start in (optional), and add arguments only if the normal launch uses them — fixed in the task, never typed by the operator.
- Conditions tab: clear Start the task only if the computer is on AC power; on a battery-backed panel it is a silent failure source.
- In the task's security settings, add the operator's account with the right to read and run the task. Without that entry, the trigger answers Access is denied no matter how the rest is configured.
- On the General tab select Run whether user is logged on or not, enter the principal's password when prompted, and sign out.
Give the operator the trigger #
On the operator's desktop, create a shortcut with this target:
schtasks.exe /run /tn "TouchCal"
The quoted name must match the task name exactly; if you created the task inside a subfolder of the Task Scheduler Library, include the folder path in /tn. In the shortcut's properties set Run to Minimized so the console window does not flash, and use Change Icon... to take the icon from the calibration executable so the button looks the way the operator expects. The operator now holds a trigger and no credentials.
The session test that decides it #
Task Scheduler places the program according to the logon setting, and this is where GUI tools live or die.
- A task stored to run whether the user is logged on or not starts in a non-interactive session. Whatever window the program opens exists where no desktop will ever show it, and the task still reports success.
- A task set to run only when user is logged on starts on that principal's own desktop — useless here, because the account signed in at the panel is the operator, not the administrator.
Run the acceptance test before any hardening or rollout. Sign the operator in, open Task Manager, Details tab, and add the Session column. Read the number on explorer.exe. Worked example: explorer.exe shows Session 2 on this panel; trigger the shortcut and find the calibration process. If it also shows Session 2, then 2 = 2 passes and the window is on the operator's touchscreen. If it shows Session 3, then 3 ≠ 2 fails: the program ran, invisibly, and no retry changes that. One run and one comparison settle it.
The decision by tool type:
- A headless utility that applies stored calibration data and exits is the ideal case for the stored-credential task; the non-interactive session costs nothing. Accept it on a Last Run Result of 0 plus a touch check at the four corners and the center.
- A tool that opens without any prompt but fails to save needs no elevation at all. Run Process Monitor as the operator, attempt one calibration, and note the denied writes. Grant the operator's account change rights on exactly that registry key or folder — one key, never a branch above it — and the GUI then saves from the operator's own session, unelevated.
- A tool that demands elevation at launch and shows a crosshair the operator must touch cannot be served by this task: the stored-credential run hides the window, and the logged-on-administrator run cannot start while the operator is signed in. Keep recalibration as an administrator action at commissioning and service visits, or use the touch vendor's service-based utility if one is supplied.
Lock the standing privilege down #
The task is a standing administrator grant that fires on demand, so close the obvious paths before you leave the panel.
- Check the executable, its folder and anything the action launches with icacls: standard users and the Users group hold read and execute at most. One user-writable file in the chain turns the task into a general escalation route.
- One task, one fixed program. Never build a launcher that accepts a program name or arguments from whoever clicks it.
- Prefer a dedicated local administrator as the principal over a personal engineering account, so a personnel change neither breaks nor exposes the delegation.
- Record the task name, the target path, the principal account and the shortcut location in the site's privilege documentation.
- Leave UAC enabled and keep the auto-logon administrator out of it. Disabling UAC removes the elevation boundary for every process on the panel, and runas with a saved credential hands the stored administrator credential to anything the operator launches. The task exists precisely to avoid both.
If the panel's own administrator account has been lost, recover it before starting any of this — recovering lost administrator rights on an industrial panel PC shows the typical path.
Make the calibration survive reboots #
Finish with the test that fails in the field. Complete a calibration through the new path as the operator, check the four corners and the center, then reboot and check again; a second reboot proves persistence rather than luck. If the offset survives the session and dies at boot, a write filter is discarding it: managing UWF on Windows 10 IoT HMI panels covers committing the change or excluding the calibration data from the filter. Two clean reboots with the touch still accurate is the rollout criterion; anything less is an open work order.
Questions asked
Why does the operator's shortcut answer Access is denied when the task exists?
The operator's account has no rights on the task object itself, which is the default for tasks an administrator creates. Open the task's security settings as administrator, add the operator's account, and give it the right to read and run the task. The elevation still comes only from the stored administrator principal; this entry grants a trigger, not a credential.
Last Run Result is 0 but no window ever appeared. Did the calibration run?
If the utility is headless, yes: it applied its settings and exited in the background session, and the touch response is the proof. If the tool is supposed to show a crosshair, the task stored credentials to run whether the user is logged on or not, so the window opened in a non-interactive session nobody can see. That configuration fails the session test; use the permission route or administrator-side calibration instead.
The new calibration holds until the panel reboots, then the old offset returns. What is discarding it?
A write filter such as UWF resets the volume at boot, so the calibration write never persisted. Commit the change explicitly or exclude the calibration's registry key and files from the filter, then verify after two consecutive reboots. On a panel with no filter, suspect a save into a profile that only loads under the account that ran the calibration.
Would it be simpler to disable UAC or use runas with a saved credential for this one tool?
No. A saved administrator credential elevates whatever the operator, or anything running on the panel, launches — not one program. Disabling UAC removes the elevation boundary for every process on the panel. The scheduled task keeps both boundaries intact and confines administrator rights to one executable at a fixed path that only administrators can change.
The task ran for months and now fails with a logon error. What changed?
The password of the principal account expired or was changed, so the stored credential no longer matches. Re-enter the credentials in the task's properties as administrator and confirm a Last Run Result of 0. Using a dedicated local account with a documented password policy prevents a routine expiry from stopping calibration on the floor.