Maybe it could be useful to have this explanation also at the end of the tutorial.Yes, it's totally OK. You can leave it as it is, or change it, as you wish. Everything saved in your user profile folder will in any case be saved on E: drive.
Thank you for the great tutorial and help!
Has there been any kind of change to this process from a few months ago?
I'm trying to follow these instructions on Windows 10 Pro build 10240 and it seems like Windows is ignoring the instructions of the answers.xml file.
There is no error message that pops up and I'm following these instructions exactly. But Windows is not creating the new users directory where I want it to. I even went ahead and created the Users directory in the place that I want to but nothing is being put there but instead Windows is still creating new users on the main OS drive.
Additionally I'm making sure to do this with the system in Audit mode by pressing CTRL + SHIFT + F3 and while in that mode, I'm using the disk management system to make sure the drive letters are correct.
No error messages but the relocation of the Users folder ignored can only mean a value of a parameter in answer file is wrong, or other user made mistake.
Please post the answer file you are using and a screenshot of your Disk Management. In addition please tell if you are installing a 32 or 64 bit Windows, and where and how you got the install media?
Kari
Thank you. This is the 64-bit Windows 10 Professional. I obtained the ISO from the Windows tool that was released last year to aid people in the upgrade. This is being done as a fresh install.
Here is a copy of my .XML file:
Here is a screenshot of my disk management.Code:<?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="oobeSystem"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" 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>F:\Users</ProfilesDirectory> </FolderLocations> </component> </settings> <cpi:offlineImage cpi:source="wim:G:\sources\install.wim#Windows 10 Pro" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>
UPDATE: I forgot I stopped myself in the middle of a third attempt at either of these two methods. THIS is how the drive is aligned now. Drive G is the CD-drive, Drive H is the USB drive I'm using to hold the relocate file.
You are absolutely sure you have 64 bit install media? You have checked that the installed system is 64 bit, and that the install media you are using to sysprep is 64 bit?
Checking the bit version when Windows is installed:
Check the install media with this command in an elevated (admin) command prompt, replacing the drive letter (K: in this example) with the correct one:
Code:dism /Get-WimInfo /WimFile:K:\sources\install.wim /index:1
Son of a... I could've swore I downloaded and installed a 64-bit installer...
Okay found the Windows Install Tool... Made DAMN sure I chose the 64-Bit installer.
I can't use the dism tool, I keep getting told "File not found." I searched the G:\sources\ directory to find out that I don't have a install.wim file but rather I have an install.esd file instead. Is that what is causing me problems?
EDIT: Here is the culprit .WIM file of the installer I used. I guess somehow/some reason I made a 32-bit version:
Is there a way to check install.esd?Code:Deployment Image Servicing and Management tool Version: 10.0.10240.16384 Details for image : G:\sources\install.wim Index : 1 Name : Windows 10 Home Description : Windows 10 Home Size : 9,333,934,255 bytes WIM Bootable : No Architecture : x86 Hal : acpiapic Version : 10.0.10240 ServicePack Build : 16384 ServicePack Level : 0 Edition : Core Installation : Client ProductType : WinNT ProductSuite : Terminal Server System Root : WINDOWS Directories : 14256 Files : 76558 Created : 9/9/2015 - 11:47:26 PM Modified : 10/22/2015 - 10:58:57 PM Languages : en-US (Default) The operation completed successfully.
Last edited by retched; 21 Feb 2016 at 19:26.
Another Update: So I went ahead and downloaded the Windows Media Tool from here. However, when I went to look at the ISO that it made, it burned an install.esd file instead of install.wim. I went ahead and converted and noticed that I get this now when I check it. Will this change the steps in anyway? (I noticed that its saying Technical Preview instead of just Pro but it is x64 version.)
After blindly working through the night... I got this to work! There is a link available on the first page of this tutorial that will take you to the Windows site to download a "special" installer... Ended up using that. Even though the WIM read as Technical Preview, I didn't need to change anything besides "Windows 10 Pro"... Other than that, it worked out well. Thanks!Code:Deployment Image Servicing and Management tool Version: 10.0.10240.16384 Details for image : D:\install.wim Index : 1 Name : Windows 10 Pro Technical Preview Description : Windows 10 Pro Technical Preview Size : 13,905,900,578 bytes WIM Bootable : No Architecture : x64 Hal : <undefined> Version : 10.0.10586 ServicePack Build : 0 ServicePack Level : 0 Edition : Professional Installation : Client ProductType : WinNT ProductSuite : Terminal Server System Root : WINDOWS Directories : 19312 Files : 98317 Created : 10/30/2015 - 4:27:01 AM Modified : 2/21/2016 - 7:50:34 PM Languages : en-US (Default) The operation completed successfully.
Last edited by retched; 21 Feb 2016 at 23:25.
First, thanks Kari, it worked nearly as expected and I ended up with Users folder relocated.
Just a few comments you may wanna check by your own:
My first try after installing Windows 10 Pro x64 using "10.0.10586 (th2_release.151029-1700)" with German language used your Method two. I ended up with relocated Users folder plus the extra admin accounts folder on D: which wasn't removable plus my original admin account (no Microsoft account) split between C: and D:. I have to confess while D: had no Users folder it wasn't empty before the attempt.
As installation doesn't take long I've decided to give Method one a try and it worked nearly as expected. Before installation I wiped out D: with Disk Management to prevent mismatches. Relocation ended with C: having no Users folder anymore. D: had an additional folder named after my admin account "myadmin.DESKTOP-xxxxxxx" which I had no problem to delete.
You may consider to simplify the process using a batch file i.e. "sysprep.bat" which I put beside "relocate.xml" on the usb drive. No need for copy'n'paste or typing, just prepare it before starting the whole process. You could use parameters for "D:" and the source installation drive but in case using notepad for editing seems ok.
Hi, Can win10 Pro X64 (what is installed) be installed over the moved profile without having to move everything back to Drive C? I am getting a media display error that I think is related to the video driver used to display pages such as CNN video. I had an ASUS R7240 Video card installed. I reinstalled it's drivers, but this did not fix the problem. I removed this card and went back to the Intel graphics built into the I5, but still have the problem. I was wondering if reinstalling the
Win10 over the top of the existing Win10 might fix the problem. The original Win10 is an upgrade from Win7. I do not have a reinstall key.
Help
Tomseay
Quote
