Early speculation re unattended installs with Win 11


hsehestedt

Well-known member
Pro User
VIP
Local time
4:04 AM
Posts
2,447
Location
Texas, USA
OS
Win11 Pro 23H2
I've become rather addicted to unattended installation and related topics with Win 10 thanks to tutorials from Kari.

However, there is currently a big "gotcha" with Windows 10 and I'm curious to find out if the ADK for Windows 11 will solve this.

Bear with me, I need to provide a little background to explain this...

Microsoft's latest recommendations are that the recovery partition be placed on the drive last, after the partition where Windows is installed. In fact, if you do a normal installation of Windows, this is how it will be installed.

However, when you perform an unattended installation, you provide in the answer file information regarding how many partitions to create and what size to make each partition. For each partition you would specify a size for that partition, except for the Windows partition. For that partition, you instruct unattended setup to use all remaining space on the disk. As a result, there is no space left on the drive to allow you to create the recovery partition after the Windows partition. Because of this, with an unattended installation you would typically have to create the recovery partition before the Windows partition. This works fine but it just bugs me that it doesn't follow the latest guidance from Microsoft.

You could go about calculating exactly how much space is on the disk and specify a precise size for the Windows partition to leave space afterward for the recovery partition, but that would mean performing new calculations and modifying the answer file every time you use a different size disk.

I do have a workaround in place for this, but it is not at all simple. It involves injecting batch files into the WinPE image on the install media and modifying the answer file to run these at the very beginning of the installation process. In fact, I had to write a program to do this for me because it's such a pain in the keister to do manually all the time.

So all that background simply leads me to this question:

I wonder if Microsoft has something planned for unattended setup of Windows 11 that will allow you to create the Windows partition and then leave space sufficient to allow the creation of the recovery partition at the end of the disk.

I'm not expecting any answers to this now, but for anyone who may be playing with a pre-release ADK and Win 11 unattended installation, I'd appreciate hearing if you run into a way to do this.
 

My Computers

System One System Two

  • OS
    Win11 Pro 23H2
    Computer type
    PC/Desktop
    Manufacturer/Model
    Home Built
    CPU
    Intel i7-11700K
    Motherboard
    ASUS Prime Z590-A
    Memory
    128GB Crucial Ballistix 3200MHz DRAM
    Graphics Card(s)
    No GPU - CPU graphics only (for now)
    Sound Card
    Realtek (on motherboard)
    Monitor(s) Displays
    HP Envy 32
    Screen Resolution
    2560 x 1440
    Hard Drives
    1 x 1TB NVMe Gen 4 x 4 SSD
    1 x 2TB NVMe Gen 3 x 4 SSD
    2 x 512GB 2.5" SSDs
    2 x 8TB HD
    PSU
    Corsair HX850i
    Case
    Corsair iCue 5000X RGB
    Cooling
    Noctua NH-D15 chromax.black cooler + 10 case fans
    Keyboard
    CODE backlit mechanical keyboard
    Mouse
    Logitech MX Master 3
    Internet Speed
    1Gb Up / 1 Gb Down
    Browser
    Edge
    Antivirus
    Windows Defender
    Other Info
    Additional options installed:
    WiFi 6E PCIe adapter
    ASUS ThunderboltEX 4 PCIe adapter
  • Operating System
    Win11 Pro 23H2
    Computer type
    Laptop
    Manufacturer/Model
    Lenovo ThinkBook 13x Gen 2
    CPU
    Intel i7-1255U
    Memory
    16 GB
    Graphics card(s)
    Intel Iris Xe Graphics
    Sound Card
    Realtek® ALC3306-CG codec
    Monitor(s) Displays
    13.3-inch IPS Display
    Screen Resolution
    WQXGA (2560 x 1600)
    Hard Drives
    2 TB 4 x 4 NVMe SSD
    PSU
    USB-C / Thunderbolt 4 Power / Charging
    Mouse
    Buttonless Glass Precision Touchpad
    Keyboard
    Backlit, spill resistant keyboard
    Internet Speed
    1Gb Up / 1Gb Down
    Browser
    Edge
    Antivirus
    Windows Defender
    Other Info
    WiFi 6e / Bluetooth 5.1 / Facial Recognition / Fingerprint Sensor / ToF (Time of Flight) Human Presence Sensor
Hi there
One possible drawback in placing the recovery partition AFTER the Windows main partition is that if say you didn't use the whole HDD/SSD for Windows but now you want to increase the size of the windows partition it makes it a bit problematical especially if you have another OS on the same SSD. By having the recovery partition BEFORE the main Windows partition makes it a lot easier moving / re-sizing partitions without encountering errors using typical standard Partition Managers. (This isn't only applicable to W11 but W10 as well).

Cheers
jimbo
 

My Computer

System One

  • OS
    Windows XP,7,10,11 Linux Arch Linux
    Computer type
    PC/Desktop
    CPU
    2 X Intel i7
The issue resides with the fact that the Microsoft guidelines for partition structure are not written to take into account various scenarios, especially like one that @jimbo45 mentions.

Plus, I get the feeling that these Microsoft guidelines were developed more for mechanical drives versus SSDs, because having the recovery partition at the end of the physical mechanical drive might have a performance benefit that is non-existent when using SSDs. I say might, because I honestly don't remember anymore if this was more of an issue with the IDE interface versus SATA, or a fault of older mechanical drives only,. but I do seem to recall reading something, somewhere, at some time, that there is some sort of performance hit on mechanical drives when accessing data from the relative beginning of the space versus relative end.

I may be way off base - but that is what I remember being the case. And if my memory pans out, it makes perfect sense as to why Microsoft was recommending the placement of the recovery partition at the physical end of space, and why it really doesn't matter all that much now, in terms of that performance hit, and also how it can be detrimental for other situations as the one Jimbo mentioned.

Of course, modern systems with SSDs seem to be less susceptible to errors when modifying partitions (regardless of where they reside), also, because (I think) the process is so much faster than on older mechanical drives, and still faster than even modern mechanical drives.

Again, I may be way off base here, but if memory serves me well, then these partition guidelines from Microsoft make more sense.
 

My Computers

System One System Two

  • OS
    Windows 11 23H2 Current build
    Computer type
    PC/Desktop
    Manufacturer/Model
    HomeBrew
    CPU
    AMD Ryzen 9 3950X
    Motherboard
    MSI MEG X570 GODLIKE
    Memory
    4 * 32 GB - Corsair Vengeance 3600 MHz
    Graphics Card(s)
    EVGA GeForce RTX 3080 Ti XC3 ULTRA GAMING (12G-P5-3955-KR)
    Sound Card
    Realtek® ALC1220 Codec
    Monitor(s) Displays
    2x Eve Spectrum ES07D03 4K Gaming Monitor (Matte) | Eve Spectrum ES07DC9 4K Gaming Monitor (Glossy)
    Screen Resolution
    3x 3840 x 2160
    Hard Drives
    3x Samsung 980 Pro NVMe PCIe 4 M.2 2 TB SSD (MZ-V8P2T0B/AM) } 3x Sabrent Rocket NVMe 4.0 1 TB SSD (USB)
    PSU
    PC Power & Cooling’s Silencer Series 1050 Watt, 80 Plus Platinum
    Case
    Fractal Design Define 7 XL Dark ATX Full Tower Case
    Cooling
    NZXT KRAKEN Z73 73.11 CFM Liquid CPU Cooler (3x 120 mm push top) + Air 3x 140mm case fans (pull front) + 1x 120 mm (push back) and 1 x 120 mm (pull bottom)
    Keyboard
    SteelSeries Apex Pro Wired Gaming Keyboard
    Mouse
    Logitech MX Master 3S | MX Master 3 for Business
    Internet Speed
    AT&T LightSpeed Gigabit Duplex Ftth
    Browser
    Nightly (default) + Firefox (stable), Chrome, Edge
    Antivirus
    Defender + MB 5 Beta
  • Operating System
    ChromeOS Flex Dev Channel (current)
    Computer type
    Laptop
    Manufacturer/Model
    Dell Latitude E5470
    CPU
    Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz, 2501 Mhz, 2 Core(s), 4 Logical Processor(s)
    Motherboard
    Dell
    Memory
    16 GB
    Graphics card(s)
    Intel(R) HD Graphics 520
    Sound Card
    Intel(R) HD Graphics 520 + RealTek Audio
    Monitor(s) Displays
    Dell laptop display 15"
    Screen Resolution
    1920 * 1080
    Hard Drives
    Toshiba 128GB M.2 22300 drive
    INTEL Cherryville 520 Series SSDSC2CW180A 180 GB SATA III SSD
    PSU
    Dell
    Case
    Dell
    Cooling
    Dell
    Mouse
    Logitech MX Master 3S (shared w. Sys 1) | Dell TouchPad
    Keyboard
    Dell
    Internet Speed
    AT&T LightSpeed Gigabit Duplex Ftth
I think that the issue is not so much that they want the recovery partition at the end for any performance issues, but it so that the size can be easily adjusted.

We've probably all seen systems where there is more than one recovery partition, a result of having to create a whole new partition if the old one is not large enough when an upgrade is performed.

With the new scheme, the Windows partition is shrunk and the Recovery partition employs the unique ability to expand backward into that freed space.

If you installed Win 11 clean (not using unattended setup) and you open Disk Management, you will see that the recovery partition is positioned last.
 

My Computers

System One System Two

  • OS
    Win11 Pro 23H2
    Computer type
    PC/Desktop
    Manufacturer/Model
    Home Built
    CPU
    Intel i7-11700K
    Motherboard
    ASUS Prime Z590-A
    Memory
    128GB Crucial Ballistix 3200MHz DRAM
    Graphics Card(s)
    No GPU - CPU graphics only (for now)
    Sound Card
    Realtek (on motherboard)
    Monitor(s) Displays
    HP Envy 32
    Screen Resolution
    2560 x 1440
    Hard Drives
    1 x 1TB NVMe Gen 4 x 4 SSD
    1 x 2TB NVMe Gen 3 x 4 SSD
    2 x 512GB 2.5" SSDs
    2 x 8TB HD
    PSU
    Corsair HX850i
    Case
    Corsair iCue 5000X RGB
    Cooling
    Noctua NH-D15 chromax.black cooler + 10 case fans
    Keyboard
    CODE backlit mechanical keyboard
    Mouse
    Logitech MX Master 3
    Internet Speed
    1Gb Up / 1 Gb Down
    Browser
    Edge
    Antivirus
    Windows Defender
    Other Info
    Additional options installed:
    WiFi 6E PCIe adapter
    ASUS ThunderboltEX 4 PCIe adapter
  • Operating System
    Win11 Pro 23H2
    Computer type
    Laptop
    Manufacturer/Model
    Lenovo ThinkBook 13x Gen 2
    CPU
    Intel i7-1255U
    Memory
    16 GB
    Graphics card(s)
    Intel Iris Xe Graphics
    Sound Card
    Realtek® ALC3306-CG codec
    Monitor(s) Displays
    13.3-inch IPS Display
    Screen Resolution
    WQXGA (2560 x 1600)
    Hard Drives
    2 TB 4 x 4 NVMe SSD
    PSU
    USB-C / Thunderbolt 4 Power / Charging
    Mouse
    Buttonless Glass Precision Touchpad
    Keyboard
    Backlit, spill resistant keyboard
    Internet Speed
    1Gb Up / 1Gb Down
    Browser
    Edge
    Antivirus
    Windows Defender
    Other Info
    WiFi 6e / Bluetooth 5.1 / Facial Recognition / Fingerprint Sensor / ToF (Time of Flight) Human Presence Sensor
I found the information where I had originally seen that recommendation. In case anyone is interested in a little lite reading :)


From that document:

"We recommend that you place this partition immediately after the Windows partition. This allows Windows to modify and recreate the partition later if future updates require a larger recovery image."

So, that makes sense because the requirements for the size of the recovery partition have crept up over time. The same article says that a minimum of 250MB is recommended, but I notice that is was created as 500MB in my Win 11 install by default.
 

My Computers

System One System Two

  • OS
    Win11 Pro 23H2
    Computer type
    PC/Desktop
    Manufacturer/Model
    Home Built
    CPU
    Intel i7-11700K
    Motherboard
    ASUS Prime Z590-A
    Memory
    128GB Crucial Ballistix 3200MHz DRAM
    Graphics Card(s)
    No GPU - CPU graphics only (for now)
    Sound Card
    Realtek (on motherboard)
    Monitor(s) Displays
    HP Envy 32
    Screen Resolution
    2560 x 1440
    Hard Drives
    1 x 1TB NVMe Gen 4 x 4 SSD
    1 x 2TB NVMe Gen 3 x 4 SSD
    2 x 512GB 2.5" SSDs
    2 x 8TB HD
    PSU
    Corsair HX850i
    Case
    Corsair iCue 5000X RGB
    Cooling
    Noctua NH-D15 chromax.black cooler + 10 case fans
    Keyboard
    CODE backlit mechanical keyboard
    Mouse
    Logitech MX Master 3
    Internet Speed
    1Gb Up / 1 Gb Down
    Browser
    Edge
    Antivirus
    Windows Defender
    Other Info
    Additional options installed:
    WiFi 6E PCIe adapter
    ASUS ThunderboltEX 4 PCIe adapter
  • Operating System
    Win11 Pro 23H2
    Computer type
    Laptop
    Manufacturer/Model
    Lenovo ThinkBook 13x Gen 2
    CPU
    Intel i7-1255U
    Memory
    16 GB
    Graphics card(s)
    Intel Iris Xe Graphics
    Sound Card
    Realtek® ALC3306-CG codec
    Monitor(s) Displays
    13.3-inch IPS Display
    Screen Resolution
    WQXGA (2560 x 1600)
    Hard Drives
    2 TB 4 x 4 NVMe SSD
    PSU
    USB-C / Thunderbolt 4 Power / Charging
    Mouse
    Buttonless Glass Precision Touchpad
    Keyboard
    Backlit, spill resistant keyboard
    Internet Speed
    1Gb Up / 1Gb Down
    Browser
    Edge
    Antivirus
    Windows Defender
    Other Info
    WiFi 6e / Bluetooth 5.1 / Facial Recognition / Fingerprint Sensor / ToF (Time of Flight) Human Presence Sensor
Thanks. I do recall going over that before. It makes a certain sort of sense.
 

My Computers

System One System Two

  • OS
    Windows 11 23H2 Current build
    Computer type
    PC/Desktop
    Manufacturer/Model
    HomeBrew
    CPU
    AMD Ryzen 9 3950X
    Motherboard
    MSI MEG X570 GODLIKE
    Memory
    4 * 32 GB - Corsair Vengeance 3600 MHz
    Graphics Card(s)
    EVGA GeForce RTX 3080 Ti XC3 ULTRA GAMING (12G-P5-3955-KR)
    Sound Card
    Realtek® ALC1220 Codec
    Monitor(s) Displays
    2x Eve Spectrum ES07D03 4K Gaming Monitor (Matte) | Eve Spectrum ES07DC9 4K Gaming Monitor (Glossy)
    Screen Resolution
    3x 3840 x 2160
    Hard Drives
    3x Samsung 980 Pro NVMe PCIe 4 M.2 2 TB SSD (MZ-V8P2T0B/AM) } 3x Sabrent Rocket NVMe 4.0 1 TB SSD (USB)
    PSU
    PC Power & Cooling’s Silencer Series 1050 Watt, 80 Plus Platinum
    Case
    Fractal Design Define 7 XL Dark ATX Full Tower Case
    Cooling
    NZXT KRAKEN Z73 73.11 CFM Liquid CPU Cooler (3x 120 mm push top) + Air 3x 140mm case fans (pull front) + 1x 120 mm (push back) and 1 x 120 mm (pull bottom)
    Keyboard
    SteelSeries Apex Pro Wired Gaming Keyboard
    Mouse
    Logitech MX Master 3S | MX Master 3 for Business
    Internet Speed
    AT&T LightSpeed Gigabit Duplex Ftth
    Browser
    Nightly (default) + Firefox (stable), Chrome, Edge
    Antivirus
    Defender + MB 5 Beta
  • Operating System
    ChromeOS Flex Dev Channel (current)
    Computer type
    Laptop
    Manufacturer/Model
    Dell Latitude E5470
    CPU
    Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz, 2501 Mhz, 2 Core(s), 4 Logical Processor(s)
    Motherboard
    Dell
    Memory
    16 GB
    Graphics card(s)
    Intel(R) HD Graphics 520
    Sound Card
    Intel(R) HD Graphics 520 + RealTek Audio
    Monitor(s) Displays
    Dell laptop display 15"
    Screen Resolution
    1920 * 1080
    Hard Drives
    Toshiba 128GB M.2 22300 drive
    INTEL Cherryville 520 Series SSDSC2CW180A 180 GB SATA III SSD
    PSU
    Dell
    Case
    Dell
    Cooling
    Dell
    Mouse
    Logitech MX Master 3S (shared w. Sys 1) | Dell TouchPad
    Keyboard
    Dell
    Internet Speed
    AT&T LightSpeed Gigabit Duplex Ftth
About the location of the recovery partition: I explained all this in a post on Ten Forums in November 2019, when MS changed default Windows Setup disk layout in Version 20H1:


Short version of that quite long post:

Before v. 20H1, Windows Setup placed recovery partition first on system disk (yellow highlight in screenshot). When an upgrade needed more space for recovery partition, the original could not expand, EFI partition blocking its way. A new recovery partition was created directly acter C: partition (blue highlight):

Recovery Partitions.jpg

Because recovery partition can something no other partition can, expand backwards if placed directly after C: partition, "stealing" space from it, this is a good place. In the future upgrades, there will be no need to create additional recovery partitions. Simply, next time recovery partition requires more space, it just takes that from C: (green highlight):

Recovery Partition expanding.jpg

Size of C: partition should be fixed, not changed after a recovery partition is created after it. A mistake (big or small, pick your choice!) would for instance be shrink C: and create a new partition in freed space. Now, when again an upgrade requires more space for recovery partition, a new one (green highlight) would be created, again after C: partition, because the previous (blue highlight) can ONLY expand backwards when directly after C:

Third Recovery Partition.jpg

Quite simple!

Kari
 
Last edited:

My Computers

System One System Two

  • OS
    Windows 11 PRO x64 Dev
    Manufacturer/Model
    Hyper-V Virtual Machine (host in System 2 specs)
    CPU
    Intel Core i7-8550U
    Memory
    6 GB
    Graphics Card(s)
    Microsoft Hyper-V Video
    Monitor(s) Displays
    Laptop display (17.1") & Samsung U28E590 (27.7")
  • Operating System
    Windows 11 PRO x64 Dev Channel
    Computer type
    Laptop
    Manufacturer/Model
    HP HP ProBook 470 G5
    CPU
    Intel Core i7-8550U
    Motherboard
    HP 837F KBC Version 02.3D.00
    Memory
    16 GB
    Graphics card(s)
    Intel(R) UHD Graphics 620 & NVIDIA GeForce 930MX
    Sound Card
    Conexant ISST Audio
    Monitor(s) Displays
    Laptop display (17.1") & Samsung U28E590 (27.7")
    Hard Drives
    128 GB SSD & 1 TB HDD
    Mouse
    Wireless Logitech MSX mouse
    Keyboard
    Wireless Logitech MK710 keyboard
    Internet Speed
    100 Mbps down, 20 Mbps up
    Browser
    Edge Chromium Dev Channel
    Antivirus
    Windows Defender
    Other Info
    2 * 3 TB USB HDD
    6 TB WD Mirror NAS
OK, unattended deployment:

I wonder if Microsoft has something planned for unattended setup of Windows 11 that will allow you to create the Windows partition and then leave space sufficient to allow the creation of the recovery partition at the end of the disk.

I'm not expecting any answers to this now, but for anyone who may be playing with a pre-release ADK and Win 11 unattended installation, I'd appreciate hearing if you run into a way to do this.

Seems that nothing will change.

Playing with WSIM, answer files and unattended deployment, the closest I can come is to simply not create a recovery partition. Here's a working autounattend.xml file for PRO edition, only creating EFI, MSR and Windows partitions, using all free space after first two for third, Windows partition:

XML:
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="windowsPE">
        <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <SetupUILanguage>
                <UILanguage>en-GB</UILanguage>
            </SetupUILanguage>
            <InputLocale>0409:0000040b</InputLocale>
            <UILanguage>en-GB</UILanguage>
            <UILanguageFallback>en-GB</UILanguageFallback>
            <UserLocale>en-GB</UserLocale>
            <SystemLocale>en-GB</SystemLocale>
        </component>
        <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <DiskConfiguration>
                <Disk wcm:action="add">
                    <CreatePartitions>
                        <CreatePartition wcm:action="add">
                            <Order>1</Order>
                            <Size>100</Size>
                            <Type>EFI</Type>
                        </CreatePartition>
                        <CreatePartition wcm:action="add">
                            <Order>2</Order>
                            <Size>128</Size>
                            <Type>MSR</Type>
                        </CreatePartition>
                        <CreatePartition wcm:action="add">
                            <Extend>true</Extend>
                            <Order>3</Order>
                            <Type>Primary</Type>
                        </CreatePartition>
                    </CreatePartitions>
                    <ModifyPartitions>
                        <ModifyPartition wcm:action="add">
                            <Order>1</Order>
                            <PartitionID>1</PartitionID>
                            <Label>System</Label>
                            <Format>FAT32</Format>
                        </ModifyPartition>
                        <ModifyPartition wcm:action="add">
                            <Order>2</Order>
                            <PartitionID>2</PartitionID>
                        </ModifyPartition>
                        <ModifyPartition wcm:action="add">
                            <Order>3</Order>
                            <PartitionID>3</PartitionID>
                            <Letter>C</Letter>
                            <Label>Windows</Label>
                            <Format>NTFS</Format>
                        </ModifyPartition>
                    </ModifyPartitions>
                    <WillWipeDisk>true</WillWipeDisk>
                    <DiskID>0</DiskID>
                </Disk>
            </DiskConfiguration>
            <UserData>
                <AcceptEula>true</AcceptEula>
                <Organization>ACME Computers</Organization>
                <ProductKey>
                    <Key>VK7JG-NPHTM-C97JM-9MPGT-3V66T</Key>
                </ProductKey>
            </UserData>
            <ImageInstall>
                <OSImage>
                    <InstallTo>
                        <DiskID>0</DiskID>
                        <PartitionID>3</PartitionID>
                    </InstallTo>
                </OSImage>
            </ImageInstall>
        </component>
    </settings>
</unattend>

My solution, and recommendation: use MDT!

Kari
 

My Computers

System One System Two

  • OS
    Windows 11 PRO x64 Dev
    Manufacturer/Model
    Hyper-V Virtual Machine (host in System 2 specs)
    CPU
    Intel Core i7-8550U
    Memory
    6 GB
    Graphics Card(s)
    Microsoft Hyper-V Video
    Monitor(s) Displays
    Laptop display (17.1") & Samsung U28E590 (27.7")
  • Operating System
    Windows 11 PRO x64 Dev Channel
    Computer type
    Laptop
    Manufacturer/Model
    HP HP ProBook 470 G5
    CPU
    Intel Core i7-8550U
    Motherboard
    HP 837F KBC Version 02.3D.00
    Memory
    16 GB
    Graphics card(s)
    Intel(R) UHD Graphics 620 & NVIDIA GeForce 930MX
    Sound Card
    Conexant ISST Audio
    Monitor(s) Displays
    Laptop display (17.1") & Samsung U28E590 (27.7")
    Hard Drives
    128 GB SSD & 1 TB HDD
    Mouse
    Wireless Logitech MSX mouse
    Keyboard
    Wireless Logitech MK710 keyboard
    Internet Speed
    100 Mbps down, 20 Mbps up
    Browser
    Edge Chromium Dev Channel
    Antivirus
    Windows Defender
    Other Info
    2 * 3 TB USB HDD
    6 TB WD Mirror NAS
Makes sense. When I cleanly installed 10 early May (with pre-release preview 21H1) I go EFI / System / Recovery, the way Microsoft wants it to be. Upgrading to leak didn't change that at all. So I suppose 11 is happy with the structure.
 

My Computers

System One System Two

  • OS
    Windows 11 23H2 Current build
    Computer type
    PC/Desktop
    Manufacturer/Model
    HomeBrew
    CPU
    AMD Ryzen 9 3950X
    Motherboard
    MSI MEG X570 GODLIKE
    Memory
    4 * 32 GB - Corsair Vengeance 3600 MHz
    Graphics Card(s)
    EVGA GeForce RTX 3080 Ti XC3 ULTRA GAMING (12G-P5-3955-KR)
    Sound Card
    Realtek® ALC1220 Codec
    Monitor(s) Displays
    2x Eve Spectrum ES07D03 4K Gaming Monitor (Matte) | Eve Spectrum ES07DC9 4K Gaming Monitor (Glossy)
    Screen Resolution
    3x 3840 x 2160
    Hard Drives
    3x Samsung 980 Pro NVMe PCIe 4 M.2 2 TB SSD (MZ-V8P2T0B/AM) } 3x Sabrent Rocket NVMe 4.0 1 TB SSD (USB)
    PSU
    PC Power & Cooling’s Silencer Series 1050 Watt, 80 Plus Platinum
    Case
    Fractal Design Define 7 XL Dark ATX Full Tower Case
    Cooling
    NZXT KRAKEN Z73 73.11 CFM Liquid CPU Cooler (3x 120 mm push top) + Air 3x 140mm case fans (pull front) + 1x 120 mm (push back) and 1 x 120 mm (pull bottom)
    Keyboard
    SteelSeries Apex Pro Wired Gaming Keyboard
    Mouse
    Logitech MX Master 3S | MX Master 3 for Business
    Internet Speed
    AT&T LightSpeed Gigabit Duplex Ftth
    Browser
    Nightly (default) + Firefox (stable), Chrome, Edge
    Antivirus
    Defender + MB 5 Beta
  • Operating System
    ChromeOS Flex Dev Channel (current)
    Computer type
    Laptop
    Manufacturer/Model
    Dell Latitude E5470
    CPU
    Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz, 2501 Mhz, 2 Core(s), 4 Logical Processor(s)
    Motherboard
    Dell
    Memory
    16 GB
    Graphics card(s)
    Intel(R) HD Graphics 520
    Sound Card
    Intel(R) HD Graphics 520 + RealTek Audio
    Monitor(s) Displays
    Dell laptop display 15"
    Screen Resolution
    1920 * 1080
    Hard Drives
    Toshiba 128GB M.2 22300 drive
    INTEL Cherryville 520 Series SSDSC2CW180A 180 GB SATA III SSD
    PSU
    Dell
    Case
    Dell
    Cooling
    Dell
    Mouse
    Logitech MX Master 3S (shared w. Sys 1) | Dell TouchPad
    Keyboard
    Dell
    Internet Speed
    AT&T LightSpeed Gigabit Duplex Ftth
Seems that nothing will change.
Kari, thanks so much taking a look at that and letting me know what you found. I have a workaround for now. I have a script that I inject into the WinPE image that gets run very early in the unattended install process, before the disk is partitioned, that performs the disk configuration for me.

The one weakness of the script is that it assumes that you will be installing to disk 0. If installing elsewhere, I would have to modify the script.

Thanks again for your help!
 

My Computers

System One System Two

  • OS
    Win11 Pro 23H2
    Computer type
    PC/Desktop
    Manufacturer/Model
    Home Built
    CPU
    Intel i7-11700K
    Motherboard
    ASUS Prime Z590-A
    Memory
    128GB Crucial Ballistix 3200MHz DRAM
    Graphics Card(s)
    No GPU - CPU graphics only (for now)
    Sound Card
    Realtek (on motherboard)
    Monitor(s) Displays
    HP Envy 32
    Screen Resolution
    2560 x 1440
    Hard Drives
    1 x 1TB NVMe Gen 4 x 4 SSD
    1 x 2TB NVMe Gen 3 x 4 SSD
    2 x 512GB 2.5" SSDs
    2 x 8TB HD
    PSU
    Corsair HX850i
    Case
    Corsair iCue 5000X RGB
    Cooling
    Noctua NH-D15 chromax.black cooler + 10 case fans
    Keyboard
    CODE backlit mechanical keyboard
    Mouse
    Logitech MX Master 3
    Internet Speed
    1Gb Up / 1 Gb Down
    Browser
    Edge
    Antivirus
    Windows Defender
    Other Info
    Additional options installed:
    WiFi 6E PCIe adapter
    ASUS ThunderboltEX 4 PCIe adapter
  • Operating System
    Win11 Pro 23H2
    Computer type
    Laptop
    Manufacturer/Model
    Lenovo ThinkBook 13x Gen 2
    CPU
    Intel i7-1255U
    Memory
    16 GB
    Graphics card(s)
    Intel Iris Xe Graphics
    Sound Card
    Realtek® ALC3306-CG codec
    Monitor(s) Displays
    13.3-inch IPS Display
    Screen Resolution
    WQXGA (2560 x 1600)
    Hard Drives
    2 TB 4 x 4 NVMe SSD
    PSU
    USB-C / Thunderbolt 4 Power / Charging
    Mouse
    Buttonless Glass Precision Touchpad
    Keyboard
    Backlit, spill resistant keyboard
    Internet Speed
    1Gb Up / 1Gb Down
    Browser
    Edge
    Antivirus
    Windows Defender
    Other Info
    WiFi 6e / Bluetooth 5.1 / Facial Recognition / Fingerprint Sensor / ToF (Time of Flight) Human Presence Sensor
The one weakness of the script is that it assumes that you will be installing to disk 0. If installing elsewhere, I would have to modify the script.

I might have a solution for that. Today, too anxious to get first official Insider W11 build installed, will post here in very near future.

Kari
 

My Computers

System One System Two

  • OS
    Windows 11 PRO x64 Dev
    Manufacturer/Model
    Hyper-V Virtual Machine (host in System 2 specs)
    CPU
    Intel Core i7-8550U
    Memory
    6 GB
    Graphics Card(s)
    Microsoft Hyper-V Video
    Monitor(s) Displays
    Laptop display (17.1") & Samsung U28E590 (27.7")
  • Operating System
    Windows 11 PRO x64 Dev Channel
    Computer type
    Laptop
    Manufacturer/Model
    HP HP ProBook 470 G5
    CPU
    Intel Core i7-8550U
    Motherboard
    HP 837F KBC Version 02.3D.00
    Memory
    16 GB
    Graphics card(s)
    Intel(R) UHD Graphics 620 & NVIDIA GeForce 930MX
    Sound Card
    Conexant ISST Audio
    Monitor(s) Displays
    Laptop display (17.1") & Samsung U28E590 (27.7")
    Hard Drives
    128 GB SSD & 1 TB HDD
    Mouse
    Wireless Logitech MSX mouse
    Keyboard
    Wireless Logitech MK710 keyboard
    Internet Speed
    100 Mbps down, 20 Mbps up
    Browser
    Edge Chromium Dev Channel
    Antivirus
    Windows Defender
    Other Info
    2 * 3 TB USB HDD
    6 TB WD Mirror NAS
LOL, I'm also installing as we speak :-).

Thanks, Kari.
 

My Computers

System One System Two

  • OS
    Win11 Pro 23H2
    Computer type
    PC/Desktop
    Manufacturer/Model
    Home Built
    CPU
    Intel i7-11700K
    Motherboard
    ASUS Prime Z590-A
    Memory
    128GB Crucial Ballistix 3200MHz DRAM
    Graphics Card(s)
    No GPU - CPU graphics only (for now)
    Sound Card
    Realtek (on motherboard)
    Monitor(s) Displays
    HP Envy 32
    Screen Resolution
    2560 x 1440
    Hard Drives
    1 x 1TB NVMe Gen 4 x 4 SSD
    1 x 2TB NVMe Gen 3 x 4 SSD
    2 x 512GB 2.5" SSDs
    2 x 8TB HD
    PSU
    Corsair HX850i
    Case
    Corsair iCue 5000X RGB
    Cooling
    Noctua NH-D15 chromax.black cooler + 10 case fans
    Keyboard
    CODE backlit mechanical keyboard
    Mouse
    Logitech MX Master 3
    Internet Speed
    1Gb Up / 1 Gb Down
    Browser
    Edge
    Antivirus
    Windows Defender
    Other Info
    Additional options installed:
    WiFi 6E PCIe adapter
    ASUS ThunderboltEX 4 PCIe adapter
  • Operating System
    Win11 Pro 23H2
    Computer type
    Laptop
    Manufacturer/Model
    Lenovo ThinkBook 13x Gen 2
    CPU
    Intel i7-1255U
    Memory
    16 GB
    Graphics card(s)
    Intel Iris Xe Graphics
    Sound Card
    Realtek® ALC3306-CG codec
    Monitor(s) Displays
    13.3-inch IPS Display
    Screen Resolution
    WQXGA (2560 x 1600)
    Hard Drives
    2 TB 4 x 4 NVMe SSD
    PSU
    USB-C / Thunderbolt 4 Power / Charging
    Mouse
    Buttonless Glass Precision Touchpad
    Keyboard
    Backlit, spill resistant keyboard
    Internet Speed
    1Gb Up / 1Gb Down
    Browser
    Edge
    Antivirus
    Windows Defender
    Other Info
    WiFi 6e / Bluetooth 5.1 / Facial Recognition / Fingerprint Sensor / ToF (Time of Flight) Human Presence Sensor
Hi all - Apologies for necrothreading, especially on my first post, but my question relates directly to the original question posed by @hsehestedt. I am also using an autounattend.xml and want to follow the most recent guidance on recovery partition placement. After reading Kari's post abut simply omitting the creation of a recovery partition in the <CreatePartitions> section, I did this, but expanded upon this by creating a batch file to create the recovery partition after the installation, as a command inside <FirstLogonCommands>.

Code:
<SynchronousCommand wcm:action="add">
    <Order>6</Order>
    <RequiresUserInput>false</RequiresUserInput>
    <CommandLine>"%InstallDrive%:\cfs-extras\scripts\create_recovery_partition.cmd"</CommandLine>
    <Description>Create Recovery Partition</Description>
</SynchronousCommand>

Batch:
SETLOCAL
FOR /F "tokens=*" %%A IN ('^""%SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe" -command "$env:firmware_type"^"') DO SET "Firmware=%%A"


IF "%Firmware%" == "UEFI" (
SET "Partition_To_Shrink=3"
SET "Create_Partition_Cmd=create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac"
SET "Gpt_Attributes=gpt attributes =0x8000000000000001"
)
IF "%Firmware%" == "Legacy" (
SET "Partition_To_Shrink=2"
SET "Create_Partition_Cmd=create partition primary id=27"
SET "Gpt_Attributes= "
)


(
ECHO select disk 0
ECHO select partition %Partition_To_Shrink%
ECHO shrink desired=700 minimum=700
ECHO %Create_Partition_Cmd%
ECHO %Gpt_Attributes%
ECHO format quick fs=ntfs label="Windows RE tools"
ECHO exit
) | "%SystemRoot%\System32\diskpart.exe"


"%SystemRoot%\System32\ReAgentc.exe" /enable

I have tested this and it works adequately, but I'm wondering if my approach has any downsides? I feel like I must have missed something because it seems so simple.

Thanks :-)
 

My Computer

System One

  • OS
    Windows 10
    Computer type
    PC/Desktop

My Computers

System One System Two

  • OS
    Windows 11 Pro 22H2 [22621.3155]
    Computer type
    PC/Desktop
    Manufacturer/Model
    Intel NUC12WSHi7
    CPU
    12th Gen Intel Core i7-1260P, 2100 MHz
    Motherboard
    NUC12WSBi7
    Memory
    64 GB
    Graphics Card(s)
    Intel Iris Xe
    Sound Card
    built-in Realtek HD audio
    Monitor(s) Displays
    Dell U3219Q
    Screen Resolution
    3840x2160 @ 60Hz
    Hard Drives
    Samsung SSD 990 PRO 1TB
    Keyboard
    CODE 104-Key Mechanical Keyboard with Cherry MX Clears
  • Operating System
    Linux Mint 21.2 (Cinnamon)
    Computer type
    PC/Desktop
    Manufacturer/Model
    Intel NUC8i5BEH
    CPU
    Intel Core i5-8259U CPU @ 2.30GHz
    Memory
    32 GB
    Graphics card(s)
    Iris Plus 655
    Keyboard
    CODE 104-Key Mechanical Keyboard - Cherry MX Clear
Looks good to me. Maybe I get a little carried away, but I create my Recovery Tools partition to be about 2 GB. But I do this simply because I always have plenty of spare space on my Windows drive.

But, @Jim123, I now have a question for you:

I notice that in your answer file snipet, you reference a path of %InstallDrive%. During unattended installation, does that resolve to X: (the RamDrive) created by setup, or does that actually resolve to drive that Windows setup was booted from? If that actually resolves to the Windows media boot drive I would kick myself for not knowing this extremely easy way of getting that drive letter!

BTW, welcome to ElevenForum!
 

My Computers

System One System Two

  • OS
    Win11 Pro 23H2
    Computer type
    PC/Desktop
    Manufacturer/Model
    Home Built
    CPU
    Intel i7-11700K
    Motherboard
    ASUS Prime Z590-A
    Memory
    128GB Crucial Ballistix 3200MHz DRAM
    Graphics Card(s)
    No GPU - CPU graphics only (for now)
    Sound Card
    Realtek (on motherboard)
    Monitor(s) Displays
    HP Envy 32
    Screen Resolution
    2560 x 1440
    Hard Drives
    1 x 1TB NVMe Gen 4 x 4 SSD
    1 x 2TB NVMe Gen 3 x 4 SSD
    2 x 512GB 2.5" SSDs
    2 x 8TB HD
    PSU
    Corsair HX850i
    Case
    Corsair iCue 5000X RGB
    Cooling
    Noctua NH-D15 chromax.black cooler + 10 case fans
    Keyboard
    CODE backlit mechanical keyboard
    Mouse
    Logitech MX Master 3
    Internet Speed
    1Gb Up / 1 Gb Down
    Browser
    Edge
    Antivirus
    Windows Defender
    Other Info
    Additional options installed:
    WiFi 6E PCIe adapter
    ASUS ThunderboltEX 4 PCIe adapter
  • Operating System
    Win11 Pro 23H2
    Computer type
    Laptop
    Manufacturer/Model
    Lenovo ThinkBook 13x Gen 2
    CPU
    Intel i7-1255U
    Memory
    16 GB
    Graphics card(s)
    Intel Iris Xe Graphics
    Sound Card
    Realtek® ALC3306-CG codec
    Monitor(s) Displays
    13.3-inch IPS Display
    Screen Resolution
    WQXGA (2560 x 1600)
    Hard Drives
    2 TB 4 x 4 NVMe SSD
    PSU
    USB-C / Thunderbolt 4 Power / Charging
    Mouse
    Buttonless Glass Precision Touchpad
    Keyboard
    Backlit, spill resistant keyboard
    Internet Speed
    1Gb Up / 1Gb Down
    Browser
    Edge
    Antivirus
    Windows Defender
    Other Info
    WiFi 6e / Bluetooth 5.1 / Facial Recognition / Fingerprint Sensor / ToF (Time of Flight) Human Presence Sensor
Looks good to me. Maybe I get a little carried away, but I create my Recovery Tools partition to be about 2 GB. But I do this simply because I always have plenty of spare space on my Windows drive.

But, @Jim123, I now have a question for you:

I notice that in your answer file snipet, you reference a path of %InstallDrive%. During unattended installation, does that resolve to X: (the RamDrive) created by setup, or does that actually resolve to drive that Windows setup was booted from? If that actually resolves to the Windows media boot drive I would kick myself for not knowing this extremely easy way of getting that drive letter!

BTW, welcome to ElevenForum!
Thank you for the welcome, and for the information about how you're doing things :-)

Yes, I created the InstallDrive environment variable, which is the drive letter of the USB drive, in the earlier <settings pass="specialize"> section, like this:
Code:
<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS"
    xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <RunSynchronous>
        <RunSynchronousCommand wcm:action="add">
            <Order>1</Order>
            <Description>Set InstallDrive environment variable</Description>
            <Path>"%ComSpec%" /c FOR %i IN (C D E F G H I J K L N M O P Q R S T U V W X Y Z) DO IF NOT DEFINED InstallDrive IF EXIST %i:\cfs-extras "%SystemRoot%\System32\setx.exe" InstallDrive %i /M</Path>
        </RunSynchronousCommand>
    </RunSynchronous>
</component>
This simply checks each drive for a directory that's known to exist on the USB stick, and if it exists, it sets an InstallDrive environment variable to the drive letter of the drive with that directory. In the above this is a directory named cfs-extras. You can then reference %InstallDrive% later on in <settings pass="oobeSystem"> commands/scripts. At the end of this section, I remove the environment variable with:
Code:
<SynchronousCommand wcm:action="add">
    <Order>7</Order>
    <RequiresUserInput>false</RequiresUserInput>
    <CommandLine>"%SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe" -command [Environment]::SetEnvironmentVariable('InstallDrive',$null,'Machine')</CommandLine>
    <Description>Remove InstallDrive machine environment variable. Always run this last.</Description>
</SynchronousCommand>
...just to keep things clean and tidy.
 

My Computer

System One

  • OS
    Windows 10
    Computer type
    PC/Desktop
Thanks for sharing that information.
 

My Computers

System One System Two

  • OS
    Win11 Pro 23H2
    Computer type
    PC/Desktop
    Manufacturer/Model
    Home Built
    CPU
    Intel i7-11700K
    Motherboard
    ASUS Prime Z590-A
    Memory
    128GB Crucial Ballistix 3200MHz DRAM
    Graphics Card(s)
    No GPU - CPU graphics only (for now)
    Sound Card
    Realtek (on motherboard)
    Monitor(s) Displays
    HP Envy 32
    Screen Resolution
    2560 x 1440
    Hard Drives
    1 x 1TB NVMe Gen 4 x 4 SSD
    1 x 2TB NVMe Gen 3 x 4 SSD
    2 x 512GB 2.5" SSDs
    2 x 8TB HD
    PSU
    Corsair HX850i
    Case
    Corsair iCue 5000X RGB
    Cooling
    Noctua NH-D15 chromax.black cooler + 10 case fans
    Keyboard
    CODE backlit mechanical keyboard
    Mouse
    Logitech MX Master 3
    Internet Speed
    1Gb Up / 1 Gb Down
    Browser
    Edge
    Antivirus
    Windows Defender
    Other Info
    Additional options installed:
    WiFi 6E PCIe adapter
    ASUS ThunderboltEX 4 PCIe adapter
  • Operating System
    Win11 Pro 23H2
    Computer type
    Laptop
    Manufacturer/Model
    Lenovo ThinkBook 13x Gen 2
    CPU
    Intel i7-1255U
    Memory
    16 GB
    Graphics card(s)
    Intel Iris Xe Graphics
    Sound Card
    Realtek® ALC3306-CG codec
    Monitor(s) Displays
    13.3-inch IPS Display
    Screen Resolution
    WQXGA (2560 x 1600)
    Hard Drives
    2 TB 4 x 4 NVMe SSD
    PSU
    USB-C / Thunderbolt 4 Power / Charging
    Mouse
    Buttonless Glass Precision Touchpad
    Keyboard
    Backlit, spill resistant keyboard
    Internet Speed
    1Gb Up / 1Gb Down
    Browser
    Edge
    Antivirus
    Windows Defender
    Other Info
    WiFi 6e / Bluetooth 5.1 / Facial Recognition / Fingerprint Sensor / ToF (Time of Flight) Human Presence Sensor
Assuming Disk 0 is used to install Windows.
The diskpart commands to create the partitions:
select disk=0
clean
convert gpt
create partition efi size=100
format quick fs=fat32
create partition msr size=16
create partition primary
shrink minimum=2000
format quick fs=ntfs label="windows"
create partition primary
format quick fs=ntfs label="recovery"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001

Note that the shrink command will make roon of 2 Gb for Recovery partition

So the unattended file should contain the commands above:
Code:
<ImageInstall>
                    <OSImage>
                        <InstallToAvailablePartition>true</InstallToAvailablePartition>
                    </OSImage>
                </ImageInstall>
                <runsynchronouscommand wcm:action="add">
                    <order>1</order>
                    <path>cmd.exe /c "&gt;&gt;"x:\diskpart.txt" echo select disk=0"</path>
                </runsynchronouscommand>
                <runsynchronouscommand wcm:action="add">
                    <order>2</order>
                    <path>cmd.exe /c "&gt;&gt;"x:\diskpart.txt" echo clean"</path>
                </runsynchronouscommand>
                <runsynchronouscommand wcm:action="add">
                    <order>3</order>
                    <path>cmd.exe /c "&gt;&gt;"x:\diskpart.txt" echo convert gpt"</path>
                </runsynchronouscommand>
                <runsynchronouscommand wcm:action="add">
                    <order>4</order>
                    <path>cmd.exe /c "&gt;&gt;"x:\diskpart.txt" echo create partition efi size=100"</path>
                </runsynchronouscommand>
                <runsynchronouscommand wcm:action="add">
                    <order>5</order>
                    <path>cmd.exe /c "&gt;&gt;"x:\diskpart.txt" echo format quick fs=fat32"</path>
                </runsynchronouscommand>
                <runsynchronouscommand wcm:action="add">
                    <order>6</order>
                    <path>cmd.exe /c "&gt;&gt;"x:\diskpart.txt" echo create partition msr size=16"</path>
                </runsynchronouscommand>
                <runsynchronouscommand wcm:action="add">
                    <order>7</order>
                    <path>cmd.exe /c "&gt;&gt;"x:\diskpart.txt" echo create partition primary"</path>
                </runsynchronouscommand>
                <runsynchronouscommand wcm:action="add">
                    <order>8</order>
                    <path>cmd.exe /c "&gt;&gt;"x:\diskpart.txt" echo shrink minimum=2000"</path>
                </runsynchronouscommand>
                <runsynchronouscommand wcm:action="add">
                    <order>9</order>
                    <path>cmd.exe /c "&gt;&gt;"x:\diskpart.txt" echo format quick fs=ntfs label="windows""</path>
                </runsynchronouscommand>
                <runsynchronouscommand wcm:action="add">
                    <order>10</order>
                    <path>cmd.exe /c "&gt;&gt;"x:\diskpart.txt" echo create partition primary"</path>
                </runsynchronouscommand>
                <runsynchronouscommand wcm:action="add">
                    <order>11</order>
                    <path>cmd.exe /c "&gt;&gt;"x:\diskpart.txt" echo format quick fs=ntfs label="recovery""</path>
                </runsynchronouscommand>
                <runsynchronouscommand wcm:action="add">
                    <order>12</order>
                    <path>cmd.exe /c "&gt;&gt;"x:\diskpart.txt" echo set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac""</path>
                </runsynchronouscommand>
                <runsynchronouscommand wcm:action="add">
                    <order>13</order>
                    <path>cmd.exe /c "&gt;&gt;"x:\diskpart.txt" echo gpt attributes=0x8000000000000001"</path>
                </runsynchronouscommand>
                <runsynchronouscommand wcm:action="add">
                    <order>14</order>
                    <path>cmd.exe /c "&gt;&gt;"x:\diskpart.log" diskpart.exe /s "x:\diskpart.txt""</path>
                </runsynchronouscommand>
 

My Computers

System One System Two

  • OS
    Windows 11 Pro 23H2
    Computer type
    Laptop
    Manufacturer/Model
    Microsoft Surface Laptop 4 13.5”
    CPU
    Quad Core 11th Intel® Core™ i7-1185G7 processor
    Memory
    32GB LPDDR4x RAM
    Graphics Card(s)
    Intel® Iris® Xᵉ Graphics
    Screen Resolution
    2256 x 1504 (201 PPI)
    Hard Drives
    1TB SSD
    Browser
    Chrome
    Antivirus
    WD
  • Operating System
    Windows 10 & 11 Pro & Linux Mint X64
    Computer type
    PC/Desktop
    Manufacturer/Model
    MSI Z77 MPower (MS-7751)
    CPU
    Intel(R) Core(TM) i7-3770K CPU @ 4.20 GHz
    Motherboard
    Z77 MPower (MS-7751)
    Memory
    32.0GB Dual-Channel CMY16GX3M2A1600C9
    Graphics card(s)
    NVIDIA GeForce GT 740
    Monitor(s) Displays
    40" Samsung
    Screen Resolution
    1920X1080
    Hard Drives
    WIN10 - 111GB Samsung SSD 840 Series
    WIN11 - 223GB Crucial CT240BX500SSD1
    931GB Crucial CT1000MX500SSD1
    931GB Crucial CT1000BX500SSD1
    931GB Crucial CT1000MX500SSD1
    232GB Samsung SSD 960 EVO 250GB
    PSU
    Antec 850W
    Case
    Antec
    Cooling
    H20
    Mouse
    Logitech MX Master 2S
    Keyboard
    Logitech K800 Wireless
    Browser
    Chrome
    Antivirus
    Windows Defender

Latest Tutorials

Back
Top Bottom