Company Christmas Holidays
North American Headquarters in Miami, USA: Dec 25, 2015, Jan 1st 2016
European Headquarters in Muenster, Germany: Dec 21, 2015 until Jan 03rd 2016
Limited support is available during this period.
We at PROVISIO wish you Merry Christmas and a Happy New Year!


Support Request: Sitediosk was not able to start properly.....


We have multiple deployments with the same configuration, but one of them is getting the following at start up:

SiteKiosk was not able to start properly for 10 times in 1200 seconds or the SiteRemote Client service did not start in time, therefor you see this emergency screen. Please press the Escape key or click the <Logoff> button and use your SiteKiosk general password to end SiteKiosk to fix this situation. The general Password is part of the Registration information you received for SiteKiosk.

SiteKiosk will be closed, the start settings will be reset, and you will be sent to the Windows login Screen.

For further assistance please contact support via our website

>> I have requested to get the logfile from the the deployment. Do you have any suggestions?

Answer: (1)

Re: Sitediosk was not able to start properly..... 8/6/2020 10:30 PM

Thank you for your inquiry. The emergency screen loads whenever SiteKiosk is restarted multiple times. It could mean a Windows security program is trying to close it. Our watchdog program ensures that it's kept running. Your general password (first 11 eleven characters of your license key) will be able to unlock it once in the emergency mode. You can read more here:

Most times, you may need to go to your admin account to run updates if its part of your corporate network. Sometimes there maybe some recent group policy changes affecting the use of SiteKiosk. There is no one reason why it does this but you can check different factors:

-Ensure that hardware failure is not eminent, like hard disk failure.
-Check your security settings like group policy, antivirus , antimalware, encryption services.
-Check SiteKiosk logs for any windows that will not close (saved as yyyy-mm-dd.txt) - C:\Program Files (x86)\SiteKiosk\Logfiles.
-Check Windows Event Viewer logs in sections like System or Application.

If you could not find anything else locally that could have affected SiteKiosk, then you can send your files to support-america(at) referencing this post:
-Configuration - C:\Program Files (x86)\SiteKiosk\Config (*.skcfg files)
-Log files - C:\Program Files (x86)\SiteKiosk\Logfiles (yyyy-mm-dd.txt files)
- SiteKioskNG.log - C:\Users\<your running user>\AppData\Local\Temp (generates when SiteKiosk runs.)
-Windows Event Viewer logs.

Best regards,