|
Ticket ID: 26984
|
Creation Date: 7/22/2026 12:19 AM
|
Product: SiteKiosk Online Client
|
Attachment: -
|
|
TicketType: Support Request
|
Version: -
|
Language: English
|
|
Views: 43
|
Last Modification Date: -
|
Platform:
|
|
|
Level: Pending
|
Modified By: -
|
|
|
Support Request: service "sitekiosk.remoteclient" failed to start
Please see the error message. The service fails to start. I have tried the following steps suggested by Claude:
A few things to try, in order:
Check the "Log on as a service" right. Open secpol.msc (Local Security Policy) → Security Settings → Local Policies → User Rights Assignment → "Log on as a service." Make sure your admin account (or SYSTEM/Local Service, if that's what SiteKiosk RemoteClient runs as) is listed there. If the machine is domain-joined, a domain Group Policy can silently strip this right back out — worth asking your IT/domain admin to check for a GPO overriding it.
Temporarily disable antivirus/endpoint protection. AV and EDR software are the most common cause of "service failed to start" during SiteKiosk installs — they block the driver/service creation silently. SiteKiosk's own FAQ flags antivirus as a known conflict source. Disable it, retry the install, then re-enable and add an exception.
Try a clean boot. msconfig → Services tab → check "Hide all Microsoft services" → Disable all → Startup tab → disable everything → reboot → run the installer as admin. This rules out a background service or startup app interfering.
Use the built-in Administrator account rather than an admin-privileged standard account. Enable it via net user administrator /active:yes (elevated Command Prompt), log in as Administrator, run the installer, then disable that account again afterward if you don't want it left on.
Retry after each step using the Retry button in that dialog rather than canceling and restarting the whole install — sometimes the service just needs the blocker cleared mid-install.
The kiosk is running Windows 10 22H2 Pro.