Windows 10 fresh installation on computer delivered with Win-10 OEM

eLPuSHeR said:

I chose 300MB because with 100MB you cannot increase cluster size (using unit=4k on diskpart for instance). I modified some diskpart script created by some member of these forums. Kudos to him/her for creating the script.

I've been super busy the last while and this Win-10-Pro prep job has been moving slowly. I've finally had some time to fully review the script samples you referred to in the forum and also numerous other available sources on the web for various DISKPART commands and command options switches and have pretty much finalized my own DISKPART command sequence which I'll execute manually. I'm used to doing things this way and completely comfortable with command line sequences in any case.

I've considered your point about using 300MB for the EFI partition space and decided to use 320 MB for my own configuration for that EFI partition. As I mentioned before, I plan to have several user data partitions beyond the operating system partition drive C. But there is one particular point I didn't quite understand when reviewing the scripts, that it was necessary NOT to manually assign the drive letter C using the DISKPART command ASSIGN for the drive letter on which Win-10 is intended to be installed on after disc partition preparations were completed, but rather to assign a "non-reserved" temporary drive letter to it using the DISKPART ASSIGN command, and somehow we're supposed to let Win-10 installation process to assign drive letter C. Do you or anyone else understand the odd reasoning behind this?

In the past I simply pre-partitioned and formatted all user drive letters I needed within Windows recovery console and then just rebooted from the OS installation optical media and just pointed the Windows installation to drive C and that would be it.

Secondly, since I will have multiple user partitiion / drive letters after C, such as D, E, F, etc. Would those subsequent NTFS primary partitions NOT be assigned their intended final drive letters as well? Or would that be a concern only for the drive partition that is to receive the OS installation?

As for the EFI partition and Windows recovery partition (the latter of which I don't plan to set up actually), there are no limitations as to the VOLUME label that must be used for these two partition types and this does not affect the partition type / function in anyway, I would have to assume?

It's probably good that this project has been delayed. I see that Win-10 version 1909 will be released soon and I'd like to get as late a release as possible to replace the older version that came OEM installed with the system.

wintenprouser said:

I've considered your point about using 300MB for the EFI partition space and decided to use 320 MB for my own configuration for that EFI partition. As I mentioned before, I plan to have several user data partitions beyond the operating system partition drive C. But there is one particular point I didn't quite understand when reviewing the scripts, that it was necessary NOT to manually assign the drive letter C using the DISKPART command ASSIGN for the drive letter on which Win-10 is intended to be installed on after disc partition preparations were completed, but rather to assign a "non-reserved" temporary drive letter to it using the DISKPART ASSIGN command, and somehow we're supposed to let Win-10 installation process to assign drive letter C. Do you or anyone else understand the odd reasoning behind this?

Good day.

I think it's just because letter C might be currently assigned upon booting up from an usb stick, for instance (specially if there are hard disks already partitioned). Thus, letting diskpart assigning the first letter available. This is just a wild guess, though.