jdff
asked on
Temporary Profile on Windows 10 Pro
I have been getting a temporary profile upon login on windows 10, the computer is joined to the domain and even when I've created a new user on active directory I've got the same message "we can't sign into your account windows 10". I have tried the regedit solution but had no luck, anyone to shine a light here?
McKnife
Logon other existent users for a test. Also try local users.
Where I have seen this happen, the regular user Windows Profile needed to be saved, deleted and re-created.
ASKER
Old profiles work fine, but not new ones. I have deleted the temp folders.... no luck here
Please quote from the event logs (system and or security log).
ASKER
a bunch of search errors on system and a bunch of errors of special privileges under security, is there any procedure that I can attempt here?
What errors, please quote at least some that accompany the logons that fail.
ASKER
Log Name: Security
Source: Microsoft-Windows-Security
Date: 1/25/2017 1:30:22 PM
Event ID: 4672
Task Category: Special Logon
Level: Information
Keywords: Audit Success
User: N/A
Computer: ENG-01.domain.local
Description:
Special privileges assigned to new logon.
------
Log Name: Security
Source: Microsoft-Windows-Security
Date: 1/25/2017 1:30:22 PM
Event ID: 4624
Task Category: Logon
Level: Information
Keywords: Audit Success
User: N/A
Computer: ENG-01.domain.local
Description:
An account was successfully logged on.
Source: Microsoft-Windows-Security
Date: 1/25/2017 1:30:22 PM
Event ID: 4672
Task Category: Special Logon
Level: Information
Keywords: Audit Success
User: N/A
Computer: ENG-01.domain.local
Description:
Special privileges assigned to new logon.
------
Log Name: Security
Source: Microsoft-Windows-Security
Date: 1/25/2017 1:30:22 PM
Event ID: 4624
Task Category: Logon
Level: Information
Keywords: Audit Success
User: N/A
Computer: ENG-01.domain.local
Description:
An account was successfully logged on.
Did you make an account called Security? Why? and why would Source = Microsoft-Windows-Security
This is a workstation. I have no such account.
This is a workstation. I have no such account.
ASKER
This is an workstation, I did not make any accounts.
I checked my machines here and one in a client office. No such account exists
I am wondering if you have a virus. Certainly I suggest you do a full scan followed by a scan with Malwarebytes.
I am wondering if you have a virus. Certainly I suggest you do a full scan followed by a scan with Malwarebytes.
That's the logname, not the user name.
Jeff, those are successes and no errors. Please quote some errors.
Jeff, those are successes and no errors. Please quote some errors.
True. I should have looked a bit more.
So jdff, please post the source this refers to.: "An account was successfully logged on"
You said "I did not make any accounts" But earlier you had said "Old profiles work fine, but not new ones."
Delete the User names AND Profiles of the accounts that do not work (back up documents first). Then shut down (power off), start up, and test all remaining User names. Do they work? Do you get a temporary profile error?
So jdff, please post the source this refers to.: "An account was successfully logged on"
You said "I did not make any accounts" But earlier you had said "Old profiles work fine, but not new ones."
Delete the User names AND Profiles of the accounts that do not work (back up documents first). Then shut down (power off), start up, and test all remaining User names. Do they work? Do you get a temporary profile error?
Can you please respond to the last question here?
ASKER
This I have not been able to get it to work still, I've created a new user and still give me trouble,
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Jeff, you need to respond to requests in order to solve it. I asked you to quote some errors. Please do that. So far, you quoted success messages, but no errors.
The situation was not even analysed properly since the author did not share the errors he wrote about, so to say "all that was left was a fresh install" is not quite it. I don't care how this question is finished, but I would rather delete it.
ASKER
That's what I had to do. Could not find a way around it.
Thanks for the update and I was happy to assist. I know it is a pain, but that was the only resolution.