Solved W11 24h2 and old installation setup

hsehestedt · Apr 7, 2025

SIW2 said:
I think hsehes missed that bit.

Indeed I did

.

Thanks for pointing that out. Weird thing is I read it like 3 times. I guess I kept seeing what I wanted to see each time

duanydias · Apr 7, 2025

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.

With the modern setup interface, it's possible to install Windows on a partition formatted with ReFS. In the legacy interface, a message is displayed stating that the file system is not supported.

garlin · Apr 7, 2025

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.

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.

duanydias · Apr 8, 2025

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.

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.

I sincerely appreciate your attention and that of the other colleagues. Could you please test by referencing an install.esd file from another location? For example:

Batch:

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

If it works, I’ll try your XML configuration, since I’m currently using:

XML:

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

spapakons · Apr 8, 2025

What is so important about ReFS over NTFS? In case something happens to Windows and you cannot boot, how are you going to retrieve your data? I am not sure you could read it. Back in Windows XP first days, I would avoid NTFS and install on FAT32 for exactly that reason. I had a lot of ways to read data from a FAT32 disk, but hardly from NTFS. I converted the disk from FAT32 to NTFS to upgrade to Vista.

z3r010 · Apr 8, 2025

@duanydias Posts must be in English.

duanydias · Apr 8, 2025

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.

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.

I appreciate your attention and that of all the other members participating in this discussion. I corrected my answer file, and now everything is working fine. The goal is to provide the option to use ReFS for those who need it, rather than making it the default in the installation performed by the tool I developed to automate Windows setup.

garlin · Apr 8, 2025

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

duanydias · Apr 8, 2025

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

I am aware of the limitations; however, some sections of Microsoft's documentation are outdated: DISM and OneDrive work perfectly on ReFS in version 24H2.

garlin · Apr 8, 2025

You may be informed, but others who read this thread might not understand the limits. Like Xbox Game Pass.

Rbcc · Jun 27, 2025

What is the link for the 5-line version of Garlin's to do this? J

Rbcc · Jun 27, 2025

Thank you very much for everyone's input !

garlin · Jun 27, 2025

Rbcc said:
What is the link for the 5-line version of Garlin's to do this? J

Why do you keep asking the same question on 3 different threads? Are you not taking the time to read the replies??
Stop posting "great support" if you're not going to bother reading the answers.

mum microsoft update package ?
mum microsoft update package ?
How do I bypass the New Windows Install and only have to Old Setup?

Rbcc · Jun 29, 2025

Sileighty said:
Thanks, i literally just tried that before your post and sadly didn´t work either

I tried that and it reboot my machine to re begin windows 11 install

Rbcc · Jul 1, 2025

for %%A in (D E F G H I J K L M N O P Q R S T U V W Y Z) do if exist %%A:\sources\setup.exe (<br> set DRIVE=%%A<br> goto :continue
1. Is there a way to make sure that this goes in Windows setup and not Windows PE Setup?

Rbcc · Jul 1, 2025

I had a problem with AutoUnattend.xml and registry hacks. Basically the Autounattend.xml wasn't even seen by Windows. so, I went ahead and asked my what Windows 11 version I wanted to Install [I only had one PRO]

hsehestedt · Jul 1, 2025

Rbcc said:
for %%A in (D E F G H I J K L M N O P Q R S T U V W Y Z) do if exist %%A:\sources\setup.exe (<br> set DRIVE=%%A<br> goto :continue
1. Is there a way to make sure that this goes in Windows setup and not Windows PE Setup?

Windows PE is index #1 of the boot.wim while index #2 is Windows Setup. If you make changes to index #2 then you are targeting Windows Setup.

blueskyler · Oct 18, 2025

hi,
I modified the Win 11 25H2 ISO with the winpeshl.ini file as suggested in the thread.

What doesn't work is loading the unattend.xml file with cmd

%WINDIR%\System32\Sysprep\Sysprep.exe /oobe /unattend:C:\unattend.xml /reboot
at the OOBE screen "Is your location"?

It seems the debloating and settings instructions are being ignored; only the offline user setting is being taken.
Is there a solution to this?
Thanks

hani_yassine1 · Oct 21, 2025

for anyone that dont want the hassle of editing the iso file what i did and worked for me (windows 11 25h2 build: 26200):
1. Save the following content as winpeshl.ini (thanks to @Young Min Oh)

[LaunchApps]
%SystemDrive%\setup.exe /legacy

2. open the windows 11 iso with 7zip navigate to sources folder and extract boot.wim
3.open the extracted boot.wim with 7 zip navigate to Windows\System32 and drop winpeshl.ini in there and exit 7zip it will ask you if you want to save it press yes
4.use rufus to make a usb with the original win 11 iso after it finish open the usb and go to the "sources" folder and replace boot.wim file with the one we crated in step 3, Done
i tried to add my unattended.xml file in the usb and it work normally (my xml file answer all the question all the way to the desktop and even run custom script all of them worked)
The whole point for switching to old setup for me is on the hard drive selection tab i use "tab" on the keyboard to quickly select partitions and delete them , in the new UI you need to use the mouse or like 8 tabs to reach the partitions i hate it as an it that do alot of formats daily, hope that help someone.

SIW2 · Oct 21, 2025

Been using winpeshl.ini for years in my pebuilds.

typically I do this

Code:

[LaunchApp]
AppPath="Pecmd.exe Main %SystemDrive%\Windows\System32\Pecmd.ini"

however it can be pointed at something else like below

Code:
Anybody can do this.

make a new text file . Name it winpeshl.ini

copy this code into winpeshl.ini

Code:

[LaunchApp] AppPath="%SystemDrive%\sources\setup.exe"

copy winpeshl.ini into boot.wim image2 \windows\system32

easily done with 7-zip only takes a few seconds

How do I bypass the New Windows Install and only have to Old Setup?

I would like to have the old Windows Install without going through the New one at boot, How is this done? TIA John

www.elevenforum.com

Winpeshl.ini Reference: Launching an app when WinPE starts

learn.microsoft.com

It needs to be in system32 of the bootable image.
The ms supplied boot.wim that comes with installation media has 2 images. Image 2 is marked bootable

If you want to use winpeshl.ini to launch something in winre.wim there is only one image

Solved W11 24h2 and old installation setup

Well-known member

My Computers

New member

My Computer

Well-known member

Attachments

My Computer

New member

My Computer

Well-known member

My Computers

Administrator

My Computers

New member

My Computer

Well-known member

My Computer

New member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Member

My Computer

Well-known member

My Computers

Similar threads