BigMonkeyHead
asked on
Refers to a location that is unavailable
Windows 7 - 64 bit
I have a new computer that I'm trying to move the C:/Users folder on an SSD to my data drive (G:). I have 2 computers and the first moved without issue. The second is giving me problems. I followed the instructions at http://lifehacker.com/5467758/move-the-users-directory-in-windows-7
When logging in, I get an error message:
C:\Windows\system32\config \systempro file\Deskt op refers to a location that is unavailable. It could be on a hard drive on this computer, or on a network. .....
The steps to move were as follows:
Take a restore point.
Boot into system restore from disk and open a cmd line
robocopy /copyall /mir /xj [SSD]:\Users to [HD]:\Users
rmdir /S /Q [SSD]:\Users
mklink /J [SSD]:\Users [HD]:\Users
where [SSD] and [HD] refer to the appropriate drive letter
Any idea where I might be able to fix this. I imagine there's a registry hack somewhere.
I have a new computer that I'm trying to move the C:/Users folder on an SSD to my data drive (G:). I have 2 computers and the first moved without issue. The second is giving me problems. I followed the instructions at http://lifehacker.com/5467758/move-the-users-directory-in-windows-7
When logging in, I get an error message:
C:\Windows\system32\config
The steps to move were as follows:
Take a restore point.
Boot into system restore from disk and open a cmd line
robocopy /copyall /mir /xj [SSD]:\Users to [HD]:\Users
rmdir /S /Q [SSD]:\Users
mklink /J [SSD]:\Users [HD]:\Users
where [SSD] and [HD] refer to the appropriate drive letter
Any idea where I might be able to fix this. I imagine there's a registry hack somewhere.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
In the future please delete the question before wasting the time of those answering questions.
ASKER
Accepted my own comment as I had already corrected the issue before SStory's response.