Link to home
Start Free TrialLog in
Avatar of wayneskid
wayneskidFlag for United States of America

asked on

Can't log in to windows 7

This is a Win7 PC. The system shut down was very slowly two night ago. The next morning I was not able to log in using my normal user profile. This user profile is the ONLY user with admin privileges. I am using the PC now having logged in via my wife's user profile and things are working as expected; with the expected limitations.

Brilliant ideas anyone?
Avatar of jmac44
jmac44
Flag of United States of America image

Boot into safe mode and do a system restore prior to the problem.
If that doesn't work and you have the install disk do a repair install.
ASKER CERTIFIED SOLUTION
Avatar of David Johnson, CD
David Johnson, CD
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
OK, there is also another way to try to get the TEMP profile case solved

a thread from 2014 for Windows 7
-> http://www.sevenforums.com/general-discussion/334551-temporary-profile-registry.html

and about the same renewed in 2016 for Windows 10
-> https://www.tenforums.com/tutorials/48012-youve-been-signed-temporary-profile-fix.html

Both these are for a trial to get the actual original profile set back in registry after some unexpected corruption not to reach it.

This is a little bit more complicated procedure than the above one, but saving the original profile as such and also some extra burden.

Have been doing also this procedure a few times, and if remembering right, some have been lucky, but some for some reason don't ...

The good thing on all these unfortunate TEMP cases is, that the actual original profile with all folders/files is available there untouched.
Avatar of wayneskid

ASKER

Thanks for all the suggestions! I did a fair amount of thrashing around with this and got paranoid. I ended up contacting Microsoft for paid support. They fixed me up in short order.
OK, you were smart, and lucky ...

Happy New Year!
Lucky, you bet! Smart, not so much.
OK, in my opinion, of course wayneskid's own solution has been an easy, right and final one, but, David Johnson's post has the real right technical solution for the case, with my slight correction and clarification for it ...