I've just tried to move my users folder to another drive on 64-Bit Windows 7 Ultimate. However, I can no longer log in as I get the error message: "The User Profile Service failed the logon. User profile cannot be loaded".

In windows, my drives are mapped as:
C:\ -> windows system drive SSD
d:\ -> programs
e:\ -> users

Using the recovery command prompt my drives were mapped as:
X:\ -> recovery media
e:\ -> windows system drive SSD
f:\ -> users

I tried to create a hardlink from c:\users to e:\users in the recovery command prompt as follows:

robocopy /copyall /mir /xj e:\users f:\users
rmdir /S /Q e:\users
mklink /J e:\users f:\users

this seemed to work in the command prompt as doing a 'dir' showed the junction point as expected. However I was unable to log in after rebooting.

As I was slightly confused about which drive letters to use (the recovery ones or the original windows ones), I tried this again using the "\?\Volume{GUID}\" notation instead but this still has the same problem.

Anyone know what I did wrong or how to both this?

PS the original instructions I used were: http://lifehacker.com/5467758/move-the-users-directory-in-windows-7 PPS this is a clean install of windows, so I am not worried about losing data, etc.

link|improve this question
sounds like the profile path is still set to c: I think this can be changed in managment console, not sure how to do it on commandline, probably via some regedit? – stijn Oct 16 '10 at 13:46
@stijn - the profile path is still set to c, but this is correct isn't it? I thought that was the point of the junction point? – Simon Oct 17 '10 at 10:02
oops didn't see you created the juntcion; in that case, yes, it sounds allright.. either something went wrong with the copy (you could check that by moving everything from e: to c: again, if you still get the error, something's currupt), or windows has problem seeing everytiing through the junction (which I doubt, I've been using junctions for a long time and never had problems) – stijn Oct 17 '10 at 10:23
@stijn thanks, that's a good suggestion. I've done that and you are right, it still can't logon. Any idea's on what I could have missed on my robocopy arguments? It didn't report any failures when I did the copy? – Simon Oct 17 '10 at 10:31
as harrymc points out, robocopy might not copy files that are in use; did you copy after booting to recovery console? if not, that might be the problem; if so, I don't know, afaik when booting via cd no files are in use so it should be fine. – stijn Oct 18 '10 at 18:05
show 3 more comments
feedback

1 Answer

See in this thread the comment made by ohdannyboy on December 4th, 2009 2:33 pm, and the following comment by imadman.

They detail how to relocate the Users folder in a way that supposedly works.

From wikipedia Robocopy :

The Windows Volume Shadow Copy service is the only Windows subsystem that can copy open files, which it does by snapshotting them for point-in-time consistency. Robocopy does not implement accessing the Volume Shadow Copy service in any way, inhibiting its usefulness as a backup utility for volumes that may be in use. However, one can use separate utilities such as VSHADOW or DISKSHADOW (included with Windows Server 2008) to create a shadow copy of a given volume with which to back up using Robocopy.

If uncopied in-use files are the cause of the problem, it is still unclear how you could have deleted e:\users, but many miracles are possible in Windows.

However, the article Backup/Copy Files that are "In Use" or "Locked" in Windows advocates using HoboCopy instead of robocopy.

As another remark, I cannot understand how you claim to have mapped the system drive to another letter than C:. As far as I know, this is absolutely impossible.

link|improve this answer
thanks harrymc, the instructions I used were actually "ohdannyboy"'s anyway. Still cannot get it to work though. – Simon Oct 17 '10 at 10:17
I have added some more thoughts about the subject. – harrymc Oct 17 '10 at 18:24
Thanks for the update harrymc. The problem wasn't files not copying because they were in use. I've now fixed the problem and will add an answer here to provide my solution, but briefly the problem was that robocopy doesn't copy junction points. As to how the system drive wasn't c:, that can happen when you boot from a win7 dvd and select command prompt from the repair menu. – Simon Oct 18 '10 at 10:32
According to your description, the junction was created AFTER the copy. – harrymc Oct 18 '10 at 12:54
Yeah, sorry, the junctions i'm talking about there are the one's that windows creates INSIDE the c:\users folder - for example, it creates a junction called "My Documents" that just points to "Documents". These are for legacy compatibility but in my experience it appears that they are required for the user account to work correctly. – Simon Oct 18 '10 at 13:24
show 1 more comment
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.