Move Users Folder Location in Windows 10  

Hi all. Can't install bst dongle on win 10 x64 gives an error Sorry,this application cannot run under a virtual mac, the users folder moved to the D drive please help

Kari

This is a truly excellent piece of work, as evidenced by everyone's interest - all 111 PAGES of postings.
This thread is now 3 years old and STILL busy - you really have met a community need.

Win 10 has gone through several versions since public release and your techniques have stood the test of time.
But, with 111 pages of postings, I can't be 100% sure I haven't missed something important

Could you find the time to add to your tutorial introduction a summary the current status of the tutorial and videos for newcomers to the thread? (even if it says when the tutorial was last updated and that there no known issues as of <date>

I have in mind something like the following:

Status Summary as of <date>
Method 1 tutorial has no known problems as of v1703 Build xxxx, (tested on <date>)
Method 2 tutorial states <here> a need to disable existing user accounts before sysprep.
This should NOT be done as of v1703 Build xxxx
You are reminded (again!) of the need to make a backup image before you start Method 2
Method X says 'blah blah blah' <link> but this has had issues in some cases
- see <link to> this post, dated xx/xx/yyyy
Since v1703 was released, the normal Windows Update process to install a feature update has worked without any problems on systems with re-located Users folders.

I would find such a status paragraph greatly reassuring.
For instance I read in early posts a need to be disconnected from the net during Method 1 (I usually am anyway).
But I'm not quite sure if this warning still applies.

Having said all this, I still plan to try Method 1 out this coming week, just as soon as my new SSD is delivered.
I have every confidence it will work - always provided I read and follow every word of the tutorial.

We all owe guys like you (and Brink) a debt of gratitude. Thanks again.

spilly

Thanks Kari, been looking for info like this for a while.

Has anyone done a clean install and then tried using a tool like PCMover to reinstall the users, apps and file to the new places? Ideally, that would be a great way to accomplish this.

Today I attempted this solution.

Ever since Windows 7, I have used a junction from C:\users to d:\users and it has served me quite well. Very neat and simple.
I have done the same on my new Win10 laptop. However there seems to be some glitches to this solution under Win10.

Today I installed the Fall Creators Update, and it broke my junction and recreated the Users folder on c:
I also got all sorts of errors since obviously my AppData was also on d: before I attempted the upgrade

I then proceeded to roll back to my previous stable setup and tried your Method #2. Right before doing so, I backed up my files and created an image of c: (fortunately)

I am working with an OEM installation... so I am aware that this may cause problems. I followed all the steps, but after I am done with the OOBE and create a new dummy profile, all my profiles are still on c: despite the fact that my unattend file species d:
I am wondering if there is a way to check that my drive letter really is d: under sysprep? I have set it to d: under disk management, but I do know that when I go to the recovery environment, it moves around.

Also, is it possible to verify that the unattend file is being read correctly?

Thanks a lot!

The HDD I am currently housing my Users folder on is starting to throw some SMART errors, so I thought I'd replace it. Will Method 2 work for this? Or should I go the clean install route?

Kari said:

you had junctions in place which failed to work after upgrade which you then rolled back to stage where junctions were working.

In my description, I forgot to write a step. After rolling back the system to a stable image, I then deleted the junction and moved back all Users content on the system drive (c:\).

Then I applied method 2, which failed. I am suspecting the unattend file isnt being read, or the OEM file is interfering.

I'm wondering if there can be UAC access issues after a clean install in certain cases

Assume Windows is installed on C:
The Users have been migrated to D: but there is now no longer space to return to the MS standard Data & S/ware All on C:

Can you do a clean install of C: and still easily recover all the user data on D: ?

If you do a clean reinstall, will the the SIDs differ from the original and so the NTFS Master index on D: might then be treated as coming from a foreign system? If so, then a prior backup is essential is it not/

Or am I worrying unnecessarily?

Kari said:

You would first need to move Users back to C:, replace the HDD and then move Users to new HDD. Too many things can go unexpected. I recommend a clean install: back up all personal files from Users, replace HDD, clean install and do Method One.

Kari

Thanks, Kari. That's what I will plan on doing then.