Move Users Folder Location in Windows 10

Kari · 23 Dec 2016

johnshaia said:

Okay, I tried creating a bootable flash drive. It still did not work. Per Kari's request, here are the steps I took:

First, I have mentioned it several times in this thread but apparently forgotten to edit the tutorial itself, that the CPI Source Image line in answer file is unnecessary (was a remnant from Windows 7 tutorial of same topic), and the Windows install media does not have to be present when sysprepping.

I've now edited the example answer file in Step 2 (under Method One), removing CPI Source line from answer file and references to Windows install media.

Second, that nothing happens, not even error messages, can only be one of two things: either an OEM Windows when sysprepped finds OEM unattended answer files which make Sysprep to ignore a user made answer file, or that Windows OOBE really does not find target drive for Users folder.

Have you checked the partition ID letters after you have sysprepped? Is the D: stil ID for your target drive?

Let's start with checking this OEM stuff: Open File Explorer > Drive C:, type name:unattend in Search and tell us what it finds (check properties of each possibly found unattend file, tell in which folders they were found).

Have to go to see my doctor now, will be back in couple of hours to see your reply.

Kari

johnshaia · 23 Dec 2016

Yes, D: remains D: after sysprep.

The search for "name:unattend" finds seven folders, in C:\Windows\SxS and in C:\Windows\Panther. All in the former folder were created on 7/16/2016. The two in Panther were created on 10/26/2016 and 10/27/2016.

There are also 23 files - application extension files, an OOBE file, a BBVV file, MUI files, a text document, manifest files, and a OA3 file. None were modified this month. There is one XML document named unattend that was modified today. It is in c:\Windows\Panther

Thanks.

johnshaia · 23 Dec 2016

Here's the text in the XML document in case it is helpful:

<?xml version="1.0" encoding="utf-8"?><unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="generalize"> <component name="Microsoft-Windows-PnpSysprep" 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"> <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls> </component> </settings> <settings pass="auditUser"> <component name="Microsoft-Windows-Deployment" 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"> <Generalize> <ForceShutdownNow>false</ForceShutdownNow> <Mode>OOBE</Mode> </Generalize> </component> </settings> <settings pass="oobeSystem"> <component name="Microsoft-Windows-Deployment" 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"> <Reseal> <Mode>OOBE</Mode> <ForceShutdownNow>false</ForceShutdownNow> </Reseal><DeviceForm>3</DeviceForm> <ExtendOSPartition> <Extend>true</Extend> </ExtendOSPartition> </component> <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"> <RegisteredOwner>HP</RegisteredOwner> <RegisteredOrganization>HP</RegisteredOrganization> <OEMName>HP</OEMName> <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <RequiresUserInput>false</RequiresUserInput> <Order>1</Order> <Description>POST OOBE Command BEGIN</Description> <CommandLine>C:\System.sav\Util\TDCTWKs\hidecmd.vbs C:\System.Sav\Util\postpin\PostOOBEB.CMD</CommandLine> </SynchronousCommand> <SynchronousCommand wcm:action="add"> <RequiresUserInput>false</RequiresUserInput> <Order>2</Order> <Description>POST OOBE Command MIDDLE</Description> <CommandLine>C:\System.sav\Util\TDCTWKs\hidecmd.vbs C:\System.Sav\Util\postpin\PostOOBEM.CMD</CommandLine> </SynchronousCommand> <SynchronousCommand wcm:action="add"> <RequiresUserInput>false</RequiresUserInput> <Order>3</Order> <Description>POST OOBE Command LAST</Description> <CommandLine>C:\System.sav\Util\TDCTWKs\hidecmd.vbs C:\System.Sav\Util\postpin\PostLast.CMD</CommandLine> </SynchronousCommand> </FirstLogonCommands> </component> </settings> <cpi

fflineImage cpi:source="" xmlns:cpi="urn:schemas-microsoft-com:cpi" /></unattend>

Kari · 23 Dec 2016

OK, I now have an idea. It's as I thought, the OEM install "fights" your own answer file.

On a tram now on my way home from doc, I'll post more when home.

Kari · 23 Dec 2016

Sorry the delay.

johnshaia said:

Here's the text in the XML document in case it is helpful:

No, it is not helpful posted like that. Impossible to read. Honestly, I hate editing code posted by another members only to make it readable. That being said, I made it readable and it is as suspected a typical OEM unattended file.

I recommend you to either forget this procedure, or clean install Windows 10 and go for Method One.

Kari

johnshaia · 23 Dec 2016

I sincerely apologize for that. I did not know it would be an issue and do not know if there is a way to retain the formatting. If it is helpful, I would be happy to reformat the file in the post. Could I append your language to the existing file or would that not work? Do I lose any OEM installed functionality by doing a clean install? As I understand it, I would not have to reformat my hard drives to do a clean install. Am I correct in my understanding? Again, sorry for the post and I am happy to format it if it would be helpful. Thanks again for your help.

johnshaia · 23 Dec 2016

You also suggested that maybe I should forget this procedure. Is there an alternative way to move the User folder to another drive for both existing and new users? I realized from re-reading your last post that you already reformatted the XML text. Again, I apologize. It was not my intention for you to have to do that.

Kari · 23 Dec 2016

johnshaia said:

I sincerely apologize for that.

No apologies needed, don't let my bad mood disturb you. I managed to read it.

johnshaia said:

You also suggested that maybe I should forget this procedure. Is there an alternative way to move the User folder to another drive for both existing and new users? I realized from re-reading your last post that you already reformatted the XML text. Again, I apologize. It was not my intention for you to have to do that.

A clean install is a clean install. It gives you a default Windows 10 without any whatsoever OEM features, applications, settings and apps.

To do this on your OEM machine, it would in my opinion require too much editing and / or removing existing OEM settings files, which in best case scenario would only remove your system recovery possibilities when / if something happens, in worst case scenario make the machine an expensive paper weight.

johnshaia · 23 Dec 2016

Last few questions - thanks for you patience.

I assume the only way I can get the Users folder moved for existing and future users is this method, right?

I definitely don't want to do Method 2 - I get that. Is there anything I am likely to care about losing in a clean install. I suspect it will mostly or all be bloat that has no value anyway. Can you tell if there is anything of value from the file I sent?

Will the clean install also reset my recovery partition, so that my recovery matches my install? I assume it will.

Thanks for all of the help.

Kari · 23 Dec 2016

Yes, Sysprep is the only really working solution to simply move everything user profile related. You could try changing the storage locations in Settings, but it can only move certain folders and needs to be done separately for every user. See the tutorial: https://www.tenforums.com/tutorials/...dows-10-a.html

Please understand this is just my personal opinion and way to do things, other members might think otherwise, but I simply refuse to use OEM installations. I do not need NortonMcAfeeAvira this test version, SuperMultiMedia DVD Player app, HP / Dell / Asus Care One Click Optimizers, and so on.

Windows 10 is extremely good in finding correct drivers, setting up a working, slim Windows without bloatware. Worst case scenario with clean install is that you have to manually download and install a driver or two from manufacturer's website.

My suggestion, requires some time but in best case you might learn something useful:

Make a full system image, containing all original disks and partitions (those that were on PC when you bought it), excluding those disks you've added later, tutorial: https://www.tenforums.com/tutorials/...p-restore.html
Link your Windows 10 license to a Microsoft account, tutorial: https://www.tenforums.com/tutorials/...ows-10-pc.html
Clean install Windows 10, the same edition as your OEM. When asked for product key, skip it; Windows 10 can be installed without product key and it will be automatically activated with a digital license, tutorial: https://www.tenforums.com/tutorials/...n-install.html
See how it works, if not happy restore the system image to be back where you started

Please post all your partitioning and other clean install related questions in relevant tutorial thread.