V
V
Vladimir Frank2017-04-19 11:39:54
Active Directory
Vladimir Frank, 2017-04-19 11:39:54

Ending a Windows 10 pro 1703 session immediately after signing in?

There is a machine under control of the domain. Windows 10 pro 1607 was installed on it the other day, an update to 1703 arrived in WSUS. All the rules seemed to be updated. Now, if a domain user has not previously sat at this computer when trying to log in, when a local user profile is created on the computer, after a couple of seconds it immediately writes "Logout" and throws it back to enter a password, and you can do this ad infinitum. If the user has previously logged in to this computer, then he logs in without problems. The same problem was after updating from 1511 to 1607 and was solved by replacing the Default folder in the users folder, it doesn’t work right now.
In the registry branch [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] the parameters
"Userinit"="C:\WINDOWS\system32\userinit.exe," UIHost="logonui.exe" Shell="Explorer.exe"
Shell="Explorer.exe"
are present.

Answer the question

In order to leave comments, you need to log in

2 answer(s)
Y
yesworld, 2017-04-21
@frankw

Try after replacing the Default folder with a known good one, clean up the information about the new user (who cannot log in) in the users folder and in the registry branch HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList - it drop-down there delete the SID of the user account, understand whose SID can be viewed by viewing the parameters of each.

A
Anatoly, 2017-04-21
@rbobot

In the folder of the default user there is some file, the rights to which do not allow him to be copied to a new profile.
Watch the eventlog after such an unsuccessful logon.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question