How to install Windows on multiple drives?

Question

Windows

There are 2 disks:

1. 100 GB SSD
   
2. HDD 1 TB
   

100 GB for Windows with programs (which are installed only in C) is not enough.
How to install Windows so that it uses the "speed" of the SSD, but stands on the HDD (or part of it)?

Answer 1

Change to HDD

Answer 2

100 GB for Windows is enough with a huge margin, even with all the desire to take more than 60 gigs for it - it is very problematic.
No, Windows cannot be "installed" on two disks, but you can transfer some of the folders to the HDD. Moreover, this is easily done with programs that are not critical to download speed, they can be installed directly on the HDD.

Answer 3

Programs that only install on C: can be tricked into installing them into a folder that is actually a symbolic link to another folder physically located on D:

Answer 4

Damn, put Windows on ssd, then transfer the folders as you need.
we kind of know what exactly you want to transfer.

Answer 5

looks a lot like

kroilovo leads to popadalovo

after all, you can already buy a 240GB ssd within the limit of 3tr
and you choose the components. empty studio - approximately 600-650Mb, + .Net traditional desktop = 6.5 GB approximately. and so on
, do not keep up with all the hares:
- xamarin / android sdk - more than 20GB, do you need it? if yes, then don't enable UWP
- but then you probably don't need C++ with full stuffing
- it's unlikely, but even if you need it - see how much the mobile sdc takes ajuri, but better not turn on either the ajuri or the web, just the crust, that's all necessary to start and web and ajuri, it will pull up
- a python? do you really need to? turn off anaconda - it's a sea of ​​scientific libraries, study for years
- turn off R
- do not turn on the DB at all, the base set will install UWP, or Core, or Azure
- don't install game dev... and if you install - none of the above, except dot-no-desktop)))
... don't be too lazy to click on optional components in the desired workloads ;))
well, as already mentioned - you can cheat transfer large chunks to another disk, junks and / or symlinks
PS .. oh yes ... cherry on the cake ;)))
https://docs.microsoft.com/ru-ru/visualstudio/inst...

Answer 6

As a rule, Windows itself and the main programs occupy 40-60GB.
Programs that are not critical to the speed of work can be installed on the HDD.
You can also move the "Documents" and "Desktop" folders there.
And there is enough space. No need to store pictures and movies on the system disk and everything will be fine.
In order for the OS to work quickly on the SSD, the following files must be located in order of importance -
1) The paging file.
2) User profile (specifically the AppData folder)
3) The system itself (Windows folder)
4) Program files - (Program Files folders)
Everything else can be placed on the HDD.
The general principle is everything that is often used, and critical to the speed on the SSD.
And archives, large files that are rarely accessed, etc., are on a slow HDD.

with programs (which are installed only in C)

Most programs ask where the installation will go. It's easy to change.
If you suddenly do not ask - which is rare, you can install, and then transfer using a symlink.
PS In any case - do not under any circumstances fill the SSD to capacity, leave at least 30GB of free space - otherwise the speed will drop. Check if TRIM is working - for example, with this utility
. If suddenly TRIM does not work - try to make it work, usually on older computers the problem is that AHCI is turned off.
If TRIM does not work at all and does not work, leave over at least 10GB, more is better. With TRIM running, this is also useful, but not critical.

Answer 7

In such cases, I always put the OS (system) on the SSD and the software on the HDD, and those that "do not want to be installed on the system disk" I transfer with symbolic links, I usually do the paging file on two partitions, one on the system, the other on any non-system partition .
How to move a program to another drive without moving it...
Transferring browser profiles from a Windows drive to another...