Solved W11 24h2 and old installation setup

SIW2 said:

I think hsehes missed that bit.

Click to expand...

hsehestedt said:

I'm wondering if the difference between the old and new setup is basically just the look and feel of the dialog screens during setup. It looks to me like the end result is all the same, so it may simply be stylistic differences.

Since unattended setup is going to bypass all of this, I wonder if there is simply no need to switch between an old and new setup in unattended setup.

In any case, both the old and new setups work flawlessly for me now, as does unattended setup.

Click to expand...

garlin said:

I installed 24H2 on a ReFS filesystem, using both Setup clients and the same unattended file. Because the disk layout only accepts NTFS or FAT32 as valid options, you're forced to use a diskpart script to format the ReFS volume.

Spoiler

Code:

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="windowsPE">
        <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">
            <ImageInstall>
                <OSImage>
                    <InstallTo>
                        <DiskID>0</DiskID>
                        <PartitionID>3</PartitionID>
                    </InstallTo>
                </OSImage>
            </ImageInstall>
            <RunSynchronous>
                <RunSynchronousCommand wcm:action="add">
                    <Order>1</Order>
                    <Path>cmd /c (for %a in ("sel dis 0" "cle" "con gpt" "cre par efi size=100" "for quick fs=fat32" "cre par msr size=16" "cre par pri" "shr minimum=800" "for quick fs=refs") do @echo %~a) &gt; X:\UEFI.txt</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>2</Order>
                    <Path>cmd /c (for %a in ("cre par pri" "for quick fs=ntfs" "set id=de94bba4-06d1-4d40-a16a-bfd50179d6ac" "gpt attributes=0x8000000000000001") do @echo %~a) &gt;&gt; X:\UEFI.txt &amp; diskpart /s X:\UEFI.txt</Path>
                </RunSynchronousCommand>
            </RunSynchronous>
            <UserData>
                <ProductKey>
                    <Key></Key>
                </ProductKey>
            </UserData>
        </component>
    </settings>
</unattend>

If you're calling setupprep, it doesn't allow for unattended mode because setupprep can only perform in-place upgrades.

In my tests, running the new Setup with this unattended file completed, but my desktop failed to have a taskbar (even after logging out). Repeating the test with the old Setup, it appears to work just fine.

Click to expand...

setup.exe /installfrom:"Another path\install.esd" /unattend:"Another path\unattend.xml"

<ImageInstall>
    <OSImage>
        <InstallToAvailablePartition>true</InstallToAvailablePartition>
    </OSImage>
</ImageInstall>

garlin said:

I installed 24H2 on a ReFS filesystem, using both Setup clients and the same unattended file. Because the disk layout only accepts NTFS or FAT32 as valid options, you're forced to use a diskpart script to format the ReFS volume.

Spoiler

Code:

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="windowsPE">
        <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">
            <ImageInstall>
                <OSImage>
                    <InstallTo>
                        <DiskID>0</DiskID>
                        <PartitionID>3</PartitionID>
                    </InstallTo>
                </OSImage>
            </ImageInstall>
            <RunSynchronous>
                <RunSynchronousCommand wcm:action="add">
                    <Order>1</Order>
                    <Path>cmd /c (for %a in ("sel dis 0" "cle" "con gpt" "cre par efi size=100" "for quick fs=fat32" "cre par msr size=16" "cre par pri" "shr minimum=800" "for quick fs=refs") do @echo %~a) &gt; X:\UEFI.txt</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>2</Order>
                    <Path>cmd /c (for %a in ("cre par pri" "for quick fs=ntfs" "set id=de94bba4-06d1-4d40-a16a-bfd50179d6ac" "gpt attributes=0x8000000000000001") do @echo %~a) &gt;&gt; X:\UEFI.txt &amp; diskpart /s X:\UEFI.txt</Path>
                </RunSynchronousCommand>
            </RunSynchronous>
            <UserData>
                <ProductKey>
                    <Key></Key>
                </ProductKey>
            </UserData>
        </component>
    </settings>
</unattend>

If you're calling setupprep, it doesn't allow for unattended mode because setupprep can only perform in-place upgrades.

In my tests, running the new Setup with this unattended file completed, but my desktop failed to have a taskbar (even after logging out). Repeating the test with the old Setup, it appears to work just fine.

Click to expand...

garlin said:

This is what you don't get when ReFS replaces NTFS:

Functionality	ReFS	NTFS
File system compression (CompactOS)	No	Yes
File system encryption (required for paid Store apps, like Xbox Game Pass)	No	Yes
Short names	No	Yes
Extended attributes	No	Yes
Disk quotas	No	Yes
Bootable (not true as we've proven)	No	Yes
Supported on removable media	No	Yes

Click to expand...