Windows xp profile not loading

For the time being, Testing is identical to Profile 1 Current. You can also rename the default profile, if you like. You can shuffle the profiles in the list up and down, changing the boot priorities. You can define the timeout before the first listed profile is selected. This can be useful if you do not wish your users to be able to select anything else than the default one - assuming that the intended users are not skilled enough to make changes once they reach the desktop.

Now, we need to change the way services are loaded for each profile during the boot up. Above, you can see the default configuration. There are three levels of Startup type for services:. Automatic - meaning they will be loaded, regardless whether they'll be used or not. Manual - meaning they will be loaded only when used.

Disabled- the service will not be loaded. In the default configuration, most services are set to either automatic or manual. To be able to configure profiles successfully, you need to understand what each service does. There is a brief description, but there's also more information under the Extended tab.

Once you are sure what you may want or need in a particular profile, you will have to change the way services are used. In our case, the first services that we will change is the Automatic Updates. Disable or enable the service for each of the profiles you created. In our case, Testing will be a slightly slimmed down version of the default profile, with several services like Automatic Updates disabled.

But before we do that, let's review our current resource usage - and the security. Our system is running with 20 processes at 71Mb memory.

Not that much - and insignificant for computers with plenty of RAM - but it might be meaningful when the default profile is running at processes with Mb memory used.

In short, you'll access the User Accounts tool to create a new account. Then, log on to the new account to create a default new user profile. Finally, log off and then log back on to the working account. Then, locate and open your original account folder. At this point, you should see all the files and folders in your original user profile, as shown earlier in Figure A. Copy the contents of the folders containing the data that you want to move to your new user profile.

In addition, you'll want to copy the contents of the Favorites, Outlook Express, and Address Book folders if you're using that e-mail program, or the Outlook folder.

You may also want to copy the contents of Cookies, Templates, and any other folders that contain critical data files. Be careful not to copy any files that are specifically related to the operating system, as any one of those files could be the culprit in the case of the corrupted user profile. For example, you definitely won't want to copy Ntuser. When you're finished copying files, log out of the working profile, and then log on to your new user profile. When you do, you should be able to access all your data files and most of your applications, just as you did with your old profile.

However, keep in mind that you may have to reinstall or at least reconfigure some of your applications. And, of course, you'll need to recreate all your personalized settings. Once you've totally moved into your new user profile, you'll want to permanently delete your old, corrupted user profile. While you may be tempted to do so from within Windows Explorer, you shouldn't because it won't completely remove all the settings associated with your old user profile.

To do it the right way, access the User Profiles tool from the Advanced tab of the System Properties dialog box.

Once you do, select the old user profile from the list and click the Delete button. So you won't ever have to go through all these troubleshooting steps should the user profile ever get corrupted again, you can trick Windows XP into administering the local user profile as if it were a roaming user profile.

When you do so, Windows XP will back up your user profile each time you log off. To use this trick, you have to log off your new account and log on to the working account. Then, access the User Profiles tool from the Advanced tab of the System Properties dialog box, select your user profile, click the Copy To button, and type the name of a folder on another drive in the Copy Profile To text box. Automatically sign up today! Greg Shultz is a freelance Technical Writer. Previously, he has worked as Documentation Specialist in the software industry, a Technical Support Specialist in educational industry, and a Technical Journalist in the computer publishing industry.

If the user profile becomes damaged, Windows XP will display one of two error messages when you log on to the system: Windows cannot load your profile because it may be corrupted. You may be logged in using a temporary User Profile. OR: The system has recovered from a serious error.

Must be an administrator Keep in mind that in order to perform the recovery operations discussed in this article, you must be working from an account with Computer Administrator privileges. Backing up your data The first thing that you'll want to do is make sure that the data in your original account is safe and then back it up. At this point, you should see all the files and folders in your original user profile, as shown in Figure A.

Figure A You can open your original account folder and back up all the files and folders containing crucial data. Editor's Picks. The best programming languages to learn in Check for Log4j vulnerabilities with this simple-to-use script.

On the SBS server, can you open an administrative command prompt and type: Replace John Smith with the problem users login name dsquery user -name "John Smith" dsget user -profile. Most of the time, the problem with profiles not loading are because a program didn't release all of the handles when the program closed.

So a temporary profile is used. Install UPHClean on the computer as it will allow the handles to be released. You can make a system restore point before you install just in case you want to go back to before you installed it. Meanwhile, you can also try copying a working user profile to the default user profile under control panel, delete the profiles that have problems and see what happens.

Sorry for the delay. I did typed in what you asked dsquery user -name "John Smith" dsget user -profile and here is what I got. Go to above location, you can find folders under this profile list, expand each folder Each folders will be for each users of the computer , you can see the profile having issue, you have to delete that folder. Restart the machine then, remove from domain and join back to the domain, the issue will be fixed. I wanted to revisit theis issue as it is happened again and I thought maybe someone will have more info.

I had a machine that was part of the network and the profile got corrupted and I want to delete it and creat a new one with the same name. I am not able to do this because of this the same issue I had that is listed in this thread. If you cannot see the whole thread please let me know. I don't want to have to wipe this machine and start from scratch but I have done all the things suggested in this thread as well as anything I can think of on my own.

I have deleted the profile, the local user account, the network account, disjoined the domain and rejoined. No matter what I do when I try to login with this user account it will only allow me to create a temporary profile. As the thread indiactes I have had this issue with other machines and other accounts so it is not this user account or this machine.

The olny way around it has been to give a person that needs to login to more than one machine is to give them a new account name. That has worked in the past to get around this issue but it is a pain in the butt. Now I have this issue which creating a new account is not going to be the solution. I need to use this account name.

Can anyone offer some solution. Thanks for the help. Worked for me too The issue was on a XP machine. Got resolved after removing the duplicate GUID and removing. One would assume from this that a statically set roaming profile path would be removed when you re-created the user.

It might be quite interesting to do so for the user in question. Alternatively, if you have users that function okay, do these users happen to reside in a different Active Directory OU to those which do not function okay? Perhaps you could just move the users with the problems into the same OU as the users who do not have problems? The user was having an issue with access to a shared resource on our FS, when the users laptop was docked they could access the resource but when undocked the mapped drive would throw a "can't find this path" error.

After reboot off the dock the share was there and could be accessed, dock and undock and the error would come back. Ran the same steps above on a different laptop and the issue was not there. Copied the users local data to a share and deleted the user's local profile. Rebooted and added the user back as admin on the laptop, logged in as user and was getting temp profile.