You have been logged on with a temporary profile
by SynRaptor on Aug.02, 2012, under IT Support
Personally I like Windows 7. It’s quick and easy to install and doesn’t have half the arse-ache of Windows XP when you reinstall for the first time, mainly because it’s inherent driver retrieval is pretty good. I haven’t had too many issues with the initial start up a 7 machine apart from this niggly and frankly irritating “fuck you” from Windows 7…. “you have been logged on with a temporary profile”….up yours!
You can’t do anything when it’s like this! Your roaming profile is fucked, you don’t have any of your administrative rights if you’re an administrator and you get shit in the DOS command line like this crap:
If that isn’t pissing annoying as it is, then the fix for it is fiddly enough that you may need to go for a run afterwards, because I hate fucking around in the Registry. It’s not as if I don’t know what I’m doing, it’s just that a single slip up and you’ve fucked the PC. Which I have no intention of doing.
The problem this causes is that in the registry it has created a duplicate of your profile ID like a royal twat, and a conflict has caused your profile to go all bollocks. The fix is simple, so go into the registry using Regedit from the Start -> Run, and navigate to this location:
HKEY_LOCAL_MACHINE\
SOFTWARE\
Microsoft\
Windows NT\
CurrentVersion\
ProfileList
In here you will find the fucked up profile, which you can easily identify as it has a .bak suffix to it. All you have to do is delete the duplicate profile ID, rename the .bak one by removing the suffix and re-login. It’s that simple, yet its still bloody annoying. It’s relatively infrequent, but once you’ve done it once, it’s easier if it happens again.
November 1st, 2012 on 6:36 pm
Thanks for the helpful comment. It was the 15th one I slogged through, and the first actually useful tip. I had deleted some userprofile folders from a Win7 machine, thinking that would force the domain to re-create the profile at next user login, as it had done in WinXP. However, Win7 also keeps the breadcrumb for the ProfileImagePath in \ProfileList and \ProfileGuid. Thus, when that unsuspecting user logged in, Win7 looked for the Profile, found nothing, created a temporary profile with .BAK suffix in the ProfileList, and did not create the C:\Users\username folder (because an entry was still sitting in \ProfileList ). Perhaps there is an error message in some EventLog somewhere, but it’s not obvious to me.
Thanks again… you never know who you’re going to help, in the Big Wide Internet.
cheers,
–j.t.
November 1st, 2012 on 9:49 pm
Glad I could help Jeffrey, I too am regularly messed about with Microsoft. I don’t think the event log picks up on it as it only seems to be a remnant in the registry, totally hidden in the background. But I hope your issue is resolved now.