User Profile Service failed the logon

I have just finished setting up 2 brand new workstations, Windows 7 64-bit, and manually joined them to our domain, Small Business Server 2003, and was able to log into both workstations using the domain administrator account, but when I try to log into the workstations with any other domain user account i get the "The User Profile Service service failed the logon" error message. I have been through numerous Microsoft KB articles and nothing thus far has worked.
LVL 12
Who is Participating?
That's probably a good idea.  We never utilize the OEM build of Windows on our domains... they typically have far too many proprietary OS configuration adjustments.

For what it's worth, even though it sounds like you were only copying the domain admin account over the Default User account for troubleshooting purposes, on a Windows 7 machine that typically causes more issues that it solves.  The potential problems are described in this TechNet blog:

Configuring Default User Settings – Full Update for Windows 7 and Windows Server 2008 R2

More specifically, the manual profile copy process can cause issues such as:

• Their list of most frequently run programs is not cleared
• Whether the user has been introduced to the Start menu (will be set to TRUE for the source account, but should be FALSE for new users). Windows Explorer does some special things the first time you log on to introduce you to the Start menu and other new features.
• Whether the user is an administrator (and should therefore see the Administrative Tools, etc).
• The personalized name for “My Documents” will be incorrect. All users documents folders will be called “Administrator's Documents”.  This is documented in the Knowledge Base article “The Desktop.ini File Does Not Work Correctly When You Create a Custom Default Profile” (
• The default download directory for IE will be set to the Administrator's Desktop folder.
• The default Save and Open locations for some application with point to the Administrator's documents folder.
• Windows 7 Libraries are broken.
Just to double-check...

The majority of the time that we see this error, it's because there were profiles that were already present within the Windows build (perhaps even the master image), and then they were manually deleted in Windows Explorer instead of being properly removed by using the Advanced System Settings interface.  As a result, registry remnants cause that exact message to appear:
silverkornAuthor Commented:
yea i have been through that KB about 5 times already. I have even deleted the Default User account and copied over the contents from the domain administrator account, and still have the error. I have also changed the permissions on the Users folder to allow full control for everyone but still same problem.

It also appears that I can not create a new account specific to the workstation as well. I have begun re-installing windows on 1 of the workstations to see if it was possible that Dell's default install of windows 7 had been corrupt for some reason.
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

silverkornAuthor Commented:
after spending too much time trying to get the workstations onto the network I have since re-installed Windows 7 and all seems well. thanks for the help
silverkornAuthor Commented:
the re-installation of windows seems to have fixed the problem(s)
Glad to hear that your machines are up and running normally again!  As I said earlier, over the years I have found that the proprietary OEM builds of Windows tend to be rather quirky.  Our team always utilizes a native Microsoft build of Windows 7, customizes the image to suit our purposes, and then deploys it throughout the domain.
I recently had this same problem. I resolved it by booting into Safe Mode with Networking with the users username. Windows was able to create the profile in safe mode. After rebooting normally the user was now able to log into their Windows profile.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.