User Profiles - Relocate to another Partition or Disk

How to Relocate User Profiles to another Partition or Disk in Windows 8​

   Information

The method described in this tutorial allows relocating user profiles and folders already while installing Windows 8, before any user accounts are created, as well as after installation on an already installed system.

The advantage of this method is that it changes some internal Windows 8 environment variables, being a “Do it once and forget” procedure. Changing the variables takes care of all existing and future user profiles, locating them when created to selected drive or partition. The method is fail proof and reversible.

When Windows 8 is installed, 5 or 6 system folders are created depending on chosen bit-version:

• PerfLogs (Performance Logs), where Windows stores performance and reliability logs
• Program Files, where applications and software are installed. Windows x86 (32-bit) stores all applications here, Windows x64 (64-bit) only native 64-bit applications
• Program Files (x86), exists only in Windows x64. All non-x64 applications are stored here
• Windows, which contains core operating system files and drivers
• ProgramData, where some applications store application and user specific settings and configuration files.
• Users. This is the “home” of all user profiles. When a new user account is created and this new user logs in first time, Windows creates a set of user specific folders (Users\Username)

Microsoft does not recommend relocating, moving ProgramData, Program Files, Program Files (x86) and Windows folders. Too much is depending on information and data stored on these folders. However, there's simply nothing preventing us to move the Users folder. In this tutorial we show how to move (relocate) the Users folder by changing an internal Windows Environment Variable.

Moving Users folder can save a lot of space on system disk. Pictures, mp3’s videos, documents and so on, a user folder with its subfolders can be tens, sometimes hundreds of gigabytes.

Personally, when installing Windows 8 I always use Audit Mode to relocate Users folder, leaving system drive only for Windows and applications.

   Note

Screenshots from pre-release version Windows 8 Consumer Preview. Actual Windows 8 has different colors but the functions are the same, tutorial can be used as it is.

   Warning

An upgraded Windows cannot be sysprepped. As this method is based in sysprepping, this tutorial is valid only for Windows setups which have not been upgraded.

This means that if you have for instance in-place upgraded Vista or Seven to Eight you cannot sysprep and this tutorial cannot be used in your case. The same applies if you have upgraded Windows 8 to Windows 8 Pro or Windows 8 to 8.1.

Notice that a repair install is also an upgrade install, so if you have ever done a repair install (= in-place upgrade to same edition), you cannot sysprep.

When sysprepping an existing Windows setup, it only works if the Windows 8 was installed clean and has never been upgraded or repaired using repair install, or if it is the original pre-installed Windows 8

Although I have repeatedly told that relocating ProgramData will cause Windows Store and Apps as well as PC Settings not to function, people keep doing it using the method described in this tutorial.

DO NOT RELOCATE PROGRAMDATA! YOUR WINDOWS STORE AND APPS WILL NOT WORK IF PROGRAMDATA IS MOVED FROM ITS DEFAULT LOCATION.

1.Audit Mode

1.1. Boot to Audit Mode when installing Windows 8


(If you have already installed Windows 8, continue from step 1.2.)

Start Windows 8 installation normally.

When installation after a reboot or two is completed and Windows 8 comes to Personalize page (see screenshot below) press CTRL + SHIFT + F3 (press and hold down CTRL and SHIFT, press F3 still holding CTRL and SHIFT down, release all three keys).




DO NOT ENTER PC NAME HERE OR CLICK NEXT! Just press CTRL + SHIFT + F3.

Your computer reboots now. Don’t panic, it’s just doing what it really should do. Windows 8 starts now in so called Audit Mode, using built-in administrator account to let you to modify Windows before any user profiles and user specific folders are created.

Continue from step 2.


1.2. Boot to Audit Mode from existing Windows 8 installation

First you need to open Command Prompt using built-in administrative account: hover pointer over bottom left corner of the desktop, right click to open Start Menu , select Command Prompt (Admin):



Command Prompt window opens. Type this to command prompt:

[B]C:\Windows\System32\Sysprep\Sysprep.exe /audit /reboot[/B]

Hit Enter.Windows reboots now to Audit Mode, "thinking" it's been started first time. Text Preparing can be seen on screen.

If you are interested to know more about Audit Mode, here are some links for you to read:

• TechNet: Understanding Audit Mode
• TechNet: Customize Windows in Audit Mode

2. Audit Mode

Windows has now booted in Audit Mode using built-in administrator account, and you should see Metro interface. Click Desktop to enter classic Windows desktop:



To start, click Cancel to close System Preparation Tool:



If you don’t have a second internal hard disk or you have not created and formatted an extra partition on your system disk, you need first to create one. Notice that the drive or partition don't have to be empty, but especially if relocating on an existing installation it must be big enough to allow Users folder to be moved there. When we sysprep with answer file on next step these two folders are physically moved to new location.

If you already have a formatted second HD or partition, you are ready to go.


2.1. Creating an answer file (script) for System Preparation Tool

Audit Mode lets us to start Windows without creating any user accounts. At the moment we are using the built-in administrator account. Your own accounts are created later.

We are going to use System Preparation Tool (sysprep) to run an XML-script (so called Answer file) which modifies the Windows registry and settings as we want to, relocating Users folder to another partition, E: in this example, by changing a so called Windows Environment Variable. You can of course use any internal drive you want to.

Extensible Markup Language (XML) is a set of rules for encoding documents in machine readable form.
To make changes to Windows registry, we will now create a script in XML and run it with sysprep.

Open Windows Notepad text editor (press Win + R, type Notepad, hit Enter). Type the following script, or copy it from here and paste to Notepad (please do not forget to read the notes below code lines 4, 6 and 11 regarding said lines):

1. <?xml version="1.0" encoding="utf-8"?>
   
2. <unattend xmlns="urn:schemas-microsoft-com:unattend">
   
3. <settings pass="oobeSystem">
   
4. <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm=[noparse]"http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"[/noparse]>
   
      Note

   (If you are installing Windows x64 (64-bit), value prosessorArchitecture should be amd64​, also on Intel processors. For x86 (32-bit) it should be x86.)
   

5. <FolderLocations>
   
6. <ProfilesDirectory>e:\Users</ProfilesDirectory>
   
      Note

   In this example the new location of Users would be E:\Users. Change the drive letter according your needs.

7. </FolderLocations>
   
8. </component>
   
9. </settings>
   
10. [noparse]<cpifflineImage[/noparse] cpi:source="wim:F:/sources/install.wim#Windows 8" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    
       Note

    (Change the drive letter in wim:F: to that of your CD/DVD drive, USB stick or virtual drive containing your Windows 8 installation media (DVD/ISO). Notice that installation media has to be available to system when running sysprep. Change Windows version accordingly, Windows 8, Windows 8 Pro, Windows 8.1 or Windows 8.1 Pro.
    

11. </unattend>
    

(Please leave the row numbers out when typing or copying the above code. Answer file generated with Windows System Image Manager).

If you are installing Windows 8 PRO x64 from CD/DVD/USB F: and relocating Users to E: you don’t have to change anything, you can use the script as it is.

Select Save As from Notepad’s File menu. Select Save as type: All Files. Name the file as you want, add .xml extension to the filename. Save the script to the root of any drive:



Alternatively you can download the answer file here: View attachment relocate.rar

2.2. Using System Preparation Tool

Open the Start Menu (Win + X), select Command Prompt (Admin).

First stop the Windows Media Player Network Sharing Service (WMPNetworkSvc) by giving the following command:

net stop WMPNetworkSvc

When the service has stopped, type the following to the command prompt and press Enter to move to the right folder:

cd c:\Windows\System32\Sysprep

Now type the following and press Enter (notice the name and path of the script we created above, change it if needed. I saved answer file on E so the path is E:\relocate.xml):

Sysprep.exe /audit /reboot /unattend:E:\relocate.xml

You should now see System Preparation Tool dialog telling it is working on our script:



Let it run, don’t touch mouse or keyboard now. When System Preparation Tool is ready, Windows must and will reboot. It reboots back to Audit Mode.


2.3. Exiting Audit Mode

To continue Windows installation we have to exit Audit Mode and reboot. After reboot you’ll land back on Metro interface. Click Desktop to enter classic Windows desktop, click OK on System Preparation Tool dialog to boot normally in OOBE i.e. normal mode.

Before clicking OK, check that System Cleanup Action is set to OOBE, and Shutdown Options set to Reboot:





3. Finalizing installation

Finalize Windows installation.

If you did this from an existing Windows installation, you will notice that for your Windows this is as if it were the first time Windows was booted i.e you are back on OOBE boot, inserting product key and personalizing Windows. It also means that you have to enter so called initial user. In this case Windows does not accept any of the users created earlier, whether local or Microsoft accounts; instead you need to create a new user.

An example from this PC I am using now: I had already created two users and installed software when I decided to do sysprep to relocate Users. I had a local account for me and an Microsoft account using my email address. After finalizing sysprep, I needed to create a third user Test because system does not let me to use either Kari (local account) or Kari (Microsoft account) usernames because those accounts already existed on this PC.

So I created user Test (local), then from Welcome screen logged in as Kari (Microsoft account) and simply deleted the new Test account which I had just created. An extra step, small annoyance but there's nothing to do to avoid it.

When Windows finally boots first time to Start Screen you will see that Users folder is now located on the new drive or partition with all its subfolders.

When you check your system drive [noparse](C still [/noparse]contains Users folder. The old, original Users on C: can contain some Windows Store information that may not be moved, so let the old Users folder stay on C:. It will no longer grow, all new user data will be stored on a new location, but it is essential it remains on C:. You can hide it if you want, you are never again going to need it.

Notice that Users folder is not created on or moved to new location when you return to Audit Mode after running sysprep. Relocation will first happen when you exit Audit Mode and boot to OOBE (Welcome) mode to continue installation. If done on an existing system the first OOBE boot after sysprepping can take quite a long time, depending on how big those folders are that sysprep is physically moving to new location.

Remember also that when you create a new user profile the user folders are not created before the new user logs in first time.

That’s it, folks! Welcome to the Windows 8:






Now create a system image and you wont have to ever again remember jumplists and links everytime you restore the system to earlier point or system image. User account folders are now permanently moved to another drive, all new user profiles are automatically created on this new location and your system drive won’t be full so soon.

Thanks for reading.

Written and published on 02[SUP]nd[/SUP] of March 2012
Edited and updated on 6[SUP]th[/SUP] of February 2013
Edited, answer file's validity checked on 14[SUP]th[/SUP] of April 2013
Added instructions for Windows 8.1 Pro preview on 29th of June 2013

Kari

Related Tutorials

---

• How to Customize Default User Profile in Audit Mode
• How to Change the Default Location of User Folders in Windows 7 and Windows 8
• How to Restore the Default Location of User Folders in Windows 7 and Windows 8

 

[Britton30]

http://www.eightforums.com/tutorial...locate-another-partition-disk.html#post350593

Very good to know this work-around Kari, thanks!

 

[DebE]

I am now up and running again. I might get the courage to try sysprep per you demo above. My issue was I was so stuck in audit mode I could not get to the refresh and as the win 8 came with the computer I could not simply reinstall and for some reason I could not access my saved info on my back HHD. So finally I did get a tech at microsoft who realized that the value for audit in the registry needed to be changed from 1 to 0 so I could restart my machine and return to the normal welcome screen.
My frustration is when I had returned to win 8 from win 8.1 upgrade with the refresh I should have been back to a clean version in my way of thinking. So either the company just put an upgraded win 8 on my machine when they put in the new HHD or when I upgraded initially to win 8.1 when I got it back the audit registry was changed then. Who knows but the company is being notified of this issue. I certainly appreciate the work you have put in and I know others are going to appreciate all your work. Thank you so much. Kari. This has been a great learning experience for me. I have worked with computers all my working life but it has been a long time since I have worked within them ... it has be sort of fun.

 

[Hans]

New install Win 8.1 prollid.

Good day, I've tried using this trick to move my Users dir to the D drive.
But when the system reboots after I left the audit mode the windows installer halts and gives the following eror message.
It can't pharse the script in c:\Windows\Phanter\Unattend.xml. The script isn't va

 

[Hans]

Good day,
I've tried using this trick to relocate my Users folder to the D:\ drive.
The manual is very clear so just followed it.
But when I leave the AUDIT mode (as indicated in the manual.
The system reboots and doesn't start where it left of, it reports a error.
The script can't be pharsed "C:\windows\Phanter\unattend.xml"
I've checked the script several times and used the relocate.rar from the site but doesn't matter.
Please let me know what I can do to resolve this problem.
Regards Hans

 

[Kari]

Hi Hans, welcome to the Eight Forums.

That error message means one of three things:

1. The answer file or sysprep command has a syntax error​

-- OR --​

2. The D: drive does not exist or is unformatted​

-- OR --​

3. A reference path is wrong or missing, for instance you give a wrong path to your answer file in sysprep command or the install.wim file is not located where the answer file tells it is

​

Kari

 

[Hans]

Hello Kari,

The D:\ drive is pressent and formatted (when the fault accours I opened (with shift F10) a command prompt and checked for the drives. Both the drive asn the WIM location where correct. In my case the J drive.

And I copied the file from the rar and changed only the lines indicated in the manual.

The script is as follows:

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<FolderLocations>
<ProfilesDirectory>D:\Users</ProfilesDirectory>
</FolderLocations>
</component>
</settings>
<cpifflineImage cpi:source="wim:J:/sources/install.wim#Windows 8.1 PRO" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

Hans

 

[Kari]

Please attach setupact.log and setuperr.log files to a post, I will check them. Both files can be found in folder C:\Windows\System32\Sysprep\Panther.

Our sister forum the Seven Forums has a tutorial about how to upload a file to your post, the principle is same here: Screenshots and Files - Upload and Post in Seven Forums - Windows 7 Help Forums

Kari

 

[Hans]

Kari,

Here are the files:

View attachment setuperr.zip

Hans

 

[Kari]

OK. It's quite late, it might be I am not able to respond tonight but I promise I'll go them through as soon as possible and post here what I find.

 

[Kari]

Posted too soon the above, it might be we can fix this tonight. I would like to see the sysprep command you use, exatly as you typed it to Command Prompt.

Use the CODE tags to post it: [noparse]

Your Sysprep command here exactly as you typed it when sysprepping

[/noparse]. It produces a clear code view showing your command and nothing else:

Your Sysprep command here exactly as you typed it when sysprepping

 

[Hans]

Good morning Kari,

I went to bed because I didn't expect to such a swift responce.

The code I typed is:
in folder c:\windows\system32\sysprep
.\sysprep /audit /reboot /unattend:d:\relocate.xml

 

[Hans]

Good morning Kari,

I went to bed because I didn't expect to such a swift responce.

The code I typed is:
in folder c:\windows\system32\sysprep

.\sysprep /audit /reboot /unattend:d:\relocate.xml

 

[Hans]

And the code for the relocate file is:

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="[URL]http://schemas.microsoft.com/WMIConfig/2002/State[/URL]" xmlns:xsi="[URL]http://www.w3.org/2001/XMLSchema-instance[/URL]">
<FolderLocations>
<ProfilesDirectory>D:\Users</ProfilesDirectory>
</FolderLocations>
</component>
</settings>
<cpi:offlineImage cpi:source="wim:J:/sources/install.wim#Windows 8.1 PRO" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

 

[Kari]

Your first sysprep runs yesterday had a command line syntax error: SYSPRP ParseCommands:Found unsupported command line option '/reboot/'(from your error log). This simply means you had a typo, you had no space in between /reboot and /unattend switches.

The last sysprep run seems to have run OK. To explain what I mean, I have to start with your first sysprep runs in which you had some typing errors:

(Click to enlarge.)​

All switches were found in correct order on your last sysprep run:

​

Also the answer file was found and used:

​

Finally, sysprep succeeded:

​

According to this log, the last of your sysprep runs should have worked?

Kari

 

[Hans]

No the machine failed on exactly the same fault.
When the machine reboots back (when I leave the administator login) the error of not being able to pharse the script in c:\windows\Panther\
Then the system reboots and after the reboot a message tells the installation was incomplete and needs to be redone.

Is it possible that this is a problem of Windows 8.1 Pro NL?? It's a new oem install.

Also included the last errorlogs from this morning.

View attachment setuperr.zip

Hans

 

[Kari]

I do not know what the problem is, doing my best to analyze this. To compare all logs please post all log files (also the cbs.log) from C:\Windows\Panther, in addition to those you have already posted from C:\Windows\System32\Sysprep. I want to see possible differences in both sets of logs.

In the meantime, you could try this:

Boot to Audit Mode, go to desktop and in Sysprep dialog select Enter System Audit Mode, Generalize and Reboot as in this screenshot:

​

Click OK, when returned to Audit Mode close the Sysprep dialog by clicking the Cancel button and run sysprep manually with your answer file, replacing the /AUDIT switch with /OOBE switch.

Please notice that the generalizing option removes all hardware related information replacing all hardware drivers with default Windows drivers.

I have a wife free weekend , time until Monday morning. We'll figure this out.

Kari

 

[Hans]

Good day Kari,

I've done as you instructed.
The strange thing is that the system didn't reboot into the audit mode.
When the sysprep was finished it rebooted and booted strait to the normal install.
Here I got the same error as I got all the other times.

Can't pharse the answer file, can't pharse of execute for the OOBE fase The asnwer file in invalid.

And again included the log files from both the c:\windows\panther and c:\windows\system32\sysprep\panther locations.

View attachment system32-sysprep-panther.zip View attachment windows-panther.zip

Hans

 

[Kari]

The reason I asked you to do this was to see how sysprep runs on your machine without any answer file, to be sure that the error is not in it. If the sysprep had worked now it had indicated that we have overlooked something, but as it failed again we can now concentrate in finding the reason why the sysprep fails, knowing that your settings, command syntax and answer file is OK.

It booted to normal setup (Welcome or OOBE mode) because I asked you to tell sysprep to do it; the first switch in sysprep command tells the Windows in which mode to boot. Switch /AUDIT boots back to Audit Mode, /OOBE boots to normal Welcome mode to continue setup.

Please post, once again, all log files from both C:\Windows\Panther and C:\Windows\System32\Sysprep.

 

[Hans]

All the logs where in my post, there are two zip files wich contain all the log files the one with 4 files is from windows\panther and the one with 2 files is from windows\system32\sysprep\panther.

Hans

 

[Kari]

Sorry I somehow missed the files.