Link to home
Start Free TrialLog in
Avatar of dovidf
dovidfFlag for United States of America

asked on

How do I correct "can't load profile, file not found" error?

Every time that I log into my system now I get the can't load profile error message. How do I correct this?
Avatar of agriesser
agriesser
Flag of Austria image

Are you using roaming profiles or local profiles?
Does the folder c:\documents and settings\USERNAME exist?
Avatar of dovidf

ASKER

All my profiles are local. The USERNAME profile exists. However, it is bigger than my available room on my C drive. Perhaps this is my problem.
That's bad, yes. Try to delete all temporary files in this profile.
Relative to your profile, they should be located in "Local Settings\Temp" and try to also clear the temporary internet files.
Oh, sorry, I somehow misread your comment. Having less drive space available shouldn't be a problem. Having no space available will cause troubles of course.

Can you check the permissions of this profile?
After you've logged in, you probably get another profile (a temporary profile) assigned - check that by clicking on "Start" -> "Run" -> "cmd"

Type "set" to see all environment variables and at the bottom of this output you should see the USERPROFILE variable. What is is currently set to?

Can you manually open your not working profile directory in Windows Explorer?
Avatar of dovidf

ASKER

The userprofile variable is set to the right profile (the one it says it can't load)
I can open the directory in the explorer.
ASKER CERTIFIED SOLUTION
Avatar of agriesser
agriesser
Flag of Austria 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
Avatar of dovidf

ASKER

I uninstalled Bitdefender which was too big for my 256 meg memory system and the problem cleared up. I think the problem was related to the registry space limit.
Oh, alright. Good to hear that you worked it out.
Avatar of dovidf

ASKER

Your suggestion for looking into the event viewer pointed me to the details of the error which indicated the symptoms in another Experts Exchange response.