Ticket ID: 24388 Creation Date: 8/3/2018 4:50 PM Product: SiteKiosk Classic Windows Attachment: -
TicketType: Support Request Version: 9.6.4409 Language: English
Views: 24844 Last Modification Date: 9/3/2018 9:21 PM Platform:
Level: Closed

Support Request: Email field at Windows Login Screen causing Auto login failure Windows 10 64bit

Description

I am using a Windows Surface Tablet that will serve as a Kiosk for the public to confirm their reservation for speaking at public hearings. The Surface Tablet is running Windows 10 64 bit Version 1703 build 15063.483. It is joined to a domain and the Site Kiosk is intended to run on a local computer account. After I have configured Site Kiosk in the manner that I want it to run and set the auto login to use the local account I want it to be, Site Kiosk consistently creates the profile to have the Windows login screen set to use a email address Sign in with Microsoft account) which causes the auto login to fail. If I manually select the password option( log in on local account) then I can log in and Site Kiosk will launch on it's own. I have tried several methods of repair including re-entering the configuration information in Site Kiosk, re-installing the software, Exporting a configuration file from another identical tablet, and re-imaging the tablet, yet consistently the email field is found at the login screen and the auto login fails because of it. Stranger still the local profile isn't configured to log in using a Microsoft account but as a regular local account when I check the Account settings. I've deleted the registry key that holds this cached setting found at HKEY_USERS > .DEFAULT > Software > Microsoft > IdentityCRL> StoredIdentities, and still no joy. Nothing sticks out as odd in the Winlogon portion of the registry. The AutoLogonSID, autoadminlogin, DefaultDomainName, DefaultUserName, defaultpassword are all correct and yet the issue persists. I could use a clue because I'm fresh out. Please assist.

Answer: (2)
Re: Email field at Windows Login Screen causing Auto login failure Windows 10 64bit 8/6/2018 4:37 PM
Did you do a standard installation of SiteKiosk by just double-clicking the exe file and choosing the default options. How are you putting SiteKiosk in to Autostart mode? Were you asked for a password when you put SiteKiosk in to Autostart mode? Can you verify the SiteKiosk version number you are running? I have not seen this issue occur on other Windows 10 systems.
Re: Email field at Windows Login Screen causing Auto login failure Windows 10 64bit 8/6/2018 8:39 PM
QUESTION: Did you do a standard installation of SiteKiosk by just double-clicking the exe file and choosing the default options?

ANSWER:
No.
* I right clicked it and ran as an administrator even though I have admin rights.

* I selected to use the Custom Installation method where:

* I selected to install .Net 3.5 and all sub features on the hard drive.

* I deselected the Apply System Security Manager default settings check box because when I leave it selected an error that refers to the password complexity occurs that doesn't allow the installation to complete.

* I do not have VNC software installed as it is not an approved Remote Desktop Control software for my enterprise environment that I support.

QUESTION: How are you putting SiteKiosk into Autostart mode?

ANSWER:
I have tried both methods. Each time on freshly imaged computer, with a fresh installation of SiteKiosk. When I launch SiteKiosk it will provide the three options of (1) Run once. (2) Auto login (3) Custom. When I select option 2, I select the local user account that has been created and provide the password. When I select option 3, I make sure the default settings for the sitekiosk local user account are deselected and then provide the local user account and password. Either method 2 or 3 causes the issue.

QUESTION: Were you asked for a password when you put SiteKiosk in to Autostart mode?

ANSWER:
Yes, and I provided the correct password for the corresponding local Windows account

QUESTION: Can you verify the SiteKiosk version number you are running?

ANSWER:
Version 9.6 build 4409.

COMMENT : I have not seen this issue occur on other Windows 10 systems.

REPLY:
Me either! I didn't see it in your support database, which is why I posted this thread. :0) It very odd to be sure. I thought clean installations of Windows and the software would resolve the oddity but it hasn't.
In your comment you state that you haven't seen this issue in other Windows 10 systems. Does that imply that you have seen it in other Window's OS versions like 7 or 8? If so what was the solution? Perhaps the solution conveys to Windows 10.
Post comment
My Account
Login
Language (Tickets):