creating partitions with diskpart in boot.wim

[RBCC122]

I am using VMWare Workstation 17.6.3 as a tester/virtualizing machine with 3 Files put into the boot.wim file in Windows 11 pro-26200.5670.  These three files are:  winpeshl.ini, partitions.txt and applywim.cmd.  I am having trouble is every partition is made except U T D. Is this a problem for VMWare with making partitions like this in VMware?  The size of the hard disk for guest machine is 500Gigabytes and 4 gig memory.

Attachment(s)

partitions.txt   834 B 1 version

MYFILES.rar   656 B 1 version

[Morc001]

I don't see how this could be a VMWare problem. If Windows creates some partitions, then VMWare is working fine. Are you sure your partition scheme is being applied partially? For example is drive C labelled as "Golden-Windows"? If not, then Windows is applying some other partitioning scheme. By the way 100MB EFI partition may be too small. There was a problem with one Windows 10 update which wanted to fix something on the EFI partition, but could not, because 100MB was not enough. Microsoft advises to resize the partition if possible, to at least 500MB.

[RBCC122]

Technically here is my partitioning scheme!

sel dis 0
 lis par
 cle 
Convert GPT
cre par efi size=550 
for quick fs=fat32 label="System" 
echo creating msr partition
cre par msr size=16
cre par pri size=700 
for quick fs=NTFS label="WinRE"
 primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac 
gpt attributes=0x8000000000000001
cre part pri size=122070 
for quick fs=ntfs label="Golden-Windows"
**** letter="C"
creating Applications Partition
cre par pri size=48830
for quick fs=ntfs label="Applications" 
**** letter="A" 
echo creating Utilities partition
cre par pri size=48830
for quick fs=ntfs label="Utilities" 
**** letter="U"
echo creating temp partition
cre par pri size=117190
for quick fs=ntfs label="Temp" 
**** letter="T"
creating Downloads Parition 
cre par pri size=138174 
for quick fs=ntfs label="Downloads" 
**** letter="D"

Is this a partial partitioning schemes the partitions add up to 476.92G  I set up my Workstation at 500 GB ,  is that adequate?  

[RBCC122]

For example is drive C labelled as "Golden-Windows"? Yes

[RaSystemlord]

I'm not familiar with those procedures, but:

Windows does its own partitioning, by default, or assisted by the installer. Afterwards, you can use Disk Manager to partitioning, if there is free space allocated in VMware.

Why are you making those partitions anyway? Maybe you have a specific reason, but generally speaking ...

... partitioning a disk perhaps made sense with DOS. Afterwards, with something else than the braindead-fat-filesystem, it has never made any sense. 

For the topics that your titles suggest, you use folders, not partitions.

With proper filesystems like NTFS and ext.n, a partition - practically speaking - never breaks. What is breaking is the disk itself and then with a high certainly, all the partitions are gone or with even higher certainty the partition that you wanted to save, will be gone. So there was no point to have partitions. Instead, you need to use a valid backup scheme for the data - I'm not saying this is the only reason for backups.

Also, during DOS times, the early versions of UNIX (like that from AT&T) had FFS, Fast File System. That had a limited number of i-nodes (let's say files) and you DID NEED to partition your disk if it was relatively large. So, the need for partitioning your data, has a history based on weaknesses of the operating system filesystems - which were left in 90s - so 30 years old problems.

Operating systems (distros) have their own concepts which are based on partitions, but those can normally be left alone and decided by the OS (distro).

As pointed out - this has nothing to do with VMware Workstation - other than the concept of allocating disk space for the OS (distro), rather than buying a physical disk for each VM computer.

[Morc001]

@RBCC122: I looked at your files and looked up this feature of the Windows installer as I was not aware of it. To me, who never used it, your partition file and the other files look OK. I was wondering whether the problem is drive letter collision. The WinRE assigns the boot media to letter X. I was thinking maybe U is used for something during install by the installer and hence partitioning fails at that point, but the installer continues on?