3 ms·
> Another "Why would you ever want to do that?" story: IIRC, in Windows 8 there was a semi-official way to place your home directory on a different drive than y
by iggldiggl 5y ago
> Another "Why would you ever want to do that?" story: IIRC, in Windows 8 there was a semi-official way to place your home directory on a different drive than your system directory. Back then I had a 128 GB SSD I wanted to use as a system drive for Windows, but because my downloads folder quickly accumulates a lot of baggage (> 50 GB) I wanted to place it on another drive. A few years down the road the upgrade to Windows 10 failed with a mysterious error code. Again, after a few days of scratching my head I found out that my setup (with the home directory on another drive) is not supported for the Windows 8.1 to 10 upgrade.
That bit was eventually fixed – while I had to move the ProgramData folder back to C:, I successfully upgraded from 7 directly to 10 with my home directory on a different drive.
Although yes, it's apparently still not officially supported – supposedly it breaks installation of apps from the store (but so far, I don't really care about the store anyway), and somewhat more annoyingly, I suspect that during major OS upgrades some misguided migration routine that is hardcoded to C: gets to run, because at least twice now I've noticed file paths in the registry being rewritten to suddenly point to C:\Users, when they actually need to point to D:\Users.
- fomine3 5y agoFor GP's case, they should just move Download directory to D: that is officially supported by GUI, rather than move entire %HOME% to D:.