Why Does Chrome Sign Me Out
So I hit this huge wall on trying to resolve this issue. Seems like a random amount of users are experiencing this issue which I cannot find a solution. When a domain user logs into their computer, they instantly get logged off. If the same user logs on to a different computer they have no problem. If any other user domain user signs in to the troubled PC they also get signed off instantly. Local and domain admin accounts seem to work fine with the troubled computer.
Why Does Chrome Log Me Out
- Feb 23, 2012 Google Chrome keeps signing me out of everything? Every time I close out of the browser it signs me out of everything. I do click 'Save my password' for most things like Yahoo and Facebook and I click the 'keep me logged in' button, but i keep getting logged out.
- If there are any mandatory extensions in your Google chrome, you should update them. To remove unwanted extensions or to update them. To do so; Left click on settings button on top right corner and navigate via Tools and click extensions. Also you can simple type chrome://extensions in URL field and press enter.
I already tried to unjoin and rejoining the domain and verified the userinit.exe Regedit which didn't have anything extra. Any suggestions?
Why I’m dumping Google Chrome. Originally, you could disable Chrome’s Auto-Update via registry values. Google felt this was insecure, however, and mandated that you have to be able to edit group policies in Windows in order to make these changes. By default, that restricts auto-update control only to Windows 7 or Windows 8 Professional.
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. 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 -HKEYLOCALMACHINESOFTWAREMicrosoftWindows NTCurrentVersionProfileList(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. 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.
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. 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: 8:34:47 AMEvent ID: 80Task Category: NoneLevel: CriticalKeywords: (8832),ProcessUser: Computer: ad-mp15b.pcfd.orgDescription:0x8007139F: Package family Microsoft.WindowsCamera8wekyb3d8bbwe 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.). 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:windowssystem32userinit.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. 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 HKEYLOCALMACHINESOFTWAREMicrosoftWindows NTCurrent VersionProfileList. 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.