[SOLVED] Windows 10 keeps signing me out immediately after
https://community.spiceworks.com/topic/1975351-windows-10-keeps-signing-me-out-immediately-after-logging-in
27 Replies 27 Replies This person is a verified professional. to enable IT peers to see that you are a professional. ghost chili I'd perform a reset or reimage it. Spice (2) 0 of 1 found this helpful This person is a verified professional. to enable IT peers to see that you are a professional. Brand Representative for mace Agreed - either there's a malicious software that made its way onto that system and it is being annoying by forcing the logoff, or there is a script from someone who is making a joke... either that or some sort of windows corruption in either the profiles or the system - in any case, it may be just best to reset or wipe/reimage it. 0 of 1 found this helpful This person is a verified professional. to enable IT peers to see that you are a professional. tabasco Is there anything listed in the event viewer that may help? 1 found this helpful This person is a verified professional. to enable IT peers to see that you are a professional. datil I would open event viewer from a different pc on the network and remotely connect to the effected machine and see what the logs were reporting. Was this post helpful? OP anaheim Oh, and I did try to delete their profile which was not good. Through the audit, I have a "An account was successfully logged on" then right after "An account was logged off." I noticed near the bottom it has this message "Logon Type: 7This event is generated when a logon session is destroyed. It may be positively correlated with a logon event using the Logon ID value. Logon IDs are only unique between reboots on the same computer." Was this post helpful? This person is a verified professional. to enable IT peers to see that you are a professional. datil That sounds suspicious to me! If nothing else, disconnect it from your network while you work on it. 0 of 1 found this helpful New contributor poblano I had a similar issue in the past (users were logged off immediately after logging in) that was caused by the user's profile folder being corrupted - even overwriting the profile didn't help, the only solution was spinning up a new account and giving it ownership of the old account's files. Haven't seen it happen in an AD scenario, though. Was this post helpful? sonora I want to add my solution to this...In my situation, we have about a dozen Windows 10 machines, and five or so had this problem where certain DOMAIN users would enter their credentials to login, it would say "welcome" for a few seconds, and then immediately switch to "signing off".What worked for me was copying the "Default" user profile folder from a windows 7 machine to the "Users" folder on the Windows 10 machine and renaming the original "Default" user folder "Default-old" or something. THEN, you have to delete the affected users Windows folder and delete his/her the registry key here -HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList (I read somewhere else that Windows basically duplicates the Default user profile when a new user logs on. The original must have been corrupted.) Then just have that user log on again. Hope this helps someone. Spice (5) 1 found this helpful New contributor pimiento Thank you, that worked! Was this post helpful? New contributor pimiento Pretend I'm an idiot and understand none of what was previously said. Now how do I fix it? Was this post helpful? New contributor pimiento I have tried the above and still am experiencing the problem. Short of re-imaging, any other ideas? Was this post helpful? anaheim Thank you very much, worked like a charm! Was this post helpful? New contributor pimiento What if I have a stand alone machine and am encountering this problem when trying to add another local login? Not sure where i can get a default user profile that is good if the only user profile on the machine is mine and from what i gather in what the solution is... that profile is the one i need to replace Was this post helpful? New contributor pimiento Just tried replacing the Default User profile.I get nothing. Still the same "Signing out" instantly after entering the users nameI also tried with an Admin profile. It ends up logging in, but then no desktop loads, the start button doesnt work, task manager doesn't work.Get several errors when trying to open things like "Personalize" under the right-click menuPlease HELP, this is breaking all domain computers with win10 creators edition on them. Was this post helpful? New contributor pimiento checkBest Answer Hi,I have seen this issue twice now and I have fixed it both times. There is a problem with the NTuser.dat file in the default profile folder after upgrading to windows 10 1703.Make sure to remove the profile folder of the user that is having the login issues. I removed it through system properties in control panel. Go to the advanced tab and click the user profiles button. Remove the affected user.I then copied the NTuser.dat file from a user that was able to login before the upgrade ( I used the admin user folder) to the default profile folder. I renamed the ntuser.dat in the default folder just in case.I was able to login as the new domain user both times after I did this.Beau Spice (4) 6 found this helpful is an IT service provider. sonora Beau3679 -This worked for me perfectly! Thank you. 1 found this helpful This person is a verified professional. to enable IT peers to see that you are a professional. serrano In the process of testing some workstation upgrades to 1703 (as support for 1511 is due to end this month).This mornings test machine was needed by someone who hadn't logged on to it before.Upon logging in they got signed out straight away.Things I tried that didn't work were:Replacing the Default User ntuser.dat from another 1703 machine.Replacing the entire Default User folder from another 1703 machine.What did work:Copying the ntuser.dat from a profile on another 1703 machine that had successfully logged in. Into the Default user profile on the troubled machine.Need to perform further testing though as at this stage it doesn't seem to be creating our locked down start menu when logging in this way. 1 found this helpful This person is a verified professional. to enable IT peers to see that you are a professional. poblano Thank You! Beau3679 and RobClarke. Your fix with copying the ntuser.dat worked like a charm for me. I love spiceworks! Was this post helpful? serrano How do you rename or delete the ntuser.dat file for the default user when it tells me that it can't be changed because the system is using that file no matter what account I log in with? I'm guessing safe mode but I'm trying to fix this remotely.Thanks Was this post helpful? New contributor pimiento I realize this isn't an option for everyone, but I fixed this problem on one of my 1703 machines by installing the 1709 feature upgrade. My symptoms were the same: users with older profiles, created before the 1703 upgrade could log in. Profiles created recently were logged out immediate upon logging in. After installing 1709 without making any other changes, all users could log in.Incidentally, at the time users were having the problem, dozens of the following Critical errors were logged :Log Name: Microsoft-Windows-AppModel-Runtime/AdminSource: Microsoft-Windows-AppModel-RuntimeDate: 10/12/2017 8:34:47 AMEvent ID: 80Task Category: NoneLevel: CriticalKeywords: (35184372088832),ProcessUser: <xxx\xxxxx>Computer: ad-mp15b.pcfd.orgDescription:0x8007139F: Package family Microsoft.WindowsCamera_8wekyb3d8bbwe runtime information is corrupted but we cannot repair it at this time.(also, Event ID 80. Several packages were named in different occurrences of the event.) Was this post helpful? New contributor pimiento I encountered this issue as well, when testing a Win7 to Win10 upgrade through SCCM using an in-place upgrade task sequence. I found the article below and while it indicates that it applies to server OSs only, I did have two paths in my Userinit value, instead of just one. I removed the one that shouldnt be there (leaving the other pointed to C:\windows\system32\userinit.exe instead of X:\....), rebooted, and was able to login with my account. I made these changes while logged in with the local admin account, which was able to login fine. 1 found this helpful This person is a verified professional. to enable IT peers to see that you are a professional. poblano That worked for me. Was this post helpful? New contributor pimiento Yep, that is exactly what the problem was. I thought that the update had finished, but it still needed another restart to install the feature update 1709. Windows 10......ughThanks for your post. Was this post helpful? New contributor pimiento So I experienced the same thing and what worked for me was logging in under my account with admin rights (I was previously signed in before the upgrade) removing the defective account C:\Users\username then removing the User's ProfileList folder in the registry under HKEY_LOCAL_MACHINE>SOFTWARE>Microsoft>Windows NT>Current Version>ProfileList. You will probably get several folders in the Profile List. You will have to inspect each folder to find the correct username, then delete the folder with the non-functioning username. The user should now be able to sign in. Was this post helpful? pimiento This one worked for us. Found it on another forum: Credit goes to whoever posted it.To fix this issue follow these instructions:
Log into the affected machine as either local or domain admin
Go to C:\Users
If you cannot see the Default user folder click “View” and check the box next to “Hidden files”. Be sure to uncheck this box when you are finished with all other steps.
Rename the Default folder to “Default.bak”
Go to C:\Windows.old\Users (If there’s no Windows.old folder use the backup Default folder in this share to complete the following steps ****see below****)
Copy the Default user folder.
Go back to C:\Users and paste the Default folder there.
If a folder has been created for the affected user, delete it.
Deselect the check box next to “hidden files”.
Right click over the Windows icon and select Run.
In the “Open” window type “regedit.exe” to open the registry editor.
Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
Find the registry entry of the affected user (should have a .bak extension) and delete it.
After a restart of the machine the user should be able to log in successfully 0 of 1 found this helpful New contributor pimiento I noticed this problem on my non-networked Lenovo laptop several weeks ago. It runs Windows 10 Home version 1709. The problem has not recurred after creating a new admin account and deleting the old one.1. Create new admin account: Settings > Account > Family & other people > Add someone else to this PC > I don't have this person's sign-in information > Add a user without a Microsoft account2. Delete the old admin account: 0 of 1 found this helpful New contributor pimiento We had this issue after migrating user profiles where we'd installed VMware View agent on the source machines but not the destination.Check HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon and the REG_SZ key "Userinit".It should only have "C:\WINDOWS\system32\userinit.exe," in it unless your environment needs something else (ie remove the VMware entry).Note that the trailing comma after the userinit entry was there by default. We checked against working and non-working machines. 1 found this helpful lock This topic has been locked by an administrator and is no longer open for commenting. To continue this discussion, please . Read these next...Has Anyone Enabled 2FA for A Domain Controller (Using Duo)? Has Anyone Enabled 2FA for A Domain Controller (Using Duo)?We been deploying 2FA for our clients, mainly for their workstations due to insurance and extra security.So far we haven't had a issue with desktops but wondering if anyone done it with their servers, especially a domain controlller. With Duo, I am afraid...Spark! Pro series 9th March 2022 Spark! Pro series 9th March 2022Today in History: 1974 - Last Japanese soldier surrenders, 29 years after World War II endedNearly 30 years after the end of the Second World War Japanese soldier Hiroo Onoda finally surrendered on this day. He had been waging his own war from a jungle an...
DA: 81 PA: 65 MOZ Rank: 45
