Windows 11

garlin said:
WinPE Setup for 24H2 defaults to a new Setup client.

Some users claim to have install problems with it, while others think it's too ugly. If you prefer seeing the "Classic" client, you can apply this reg file to boot.wim (Setup):
Code: 
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\Setup]
"CmdLine"="X:\\sources\\setup.exe"
Click to expand...
while applying this method with this REG tweak, integrated into the boot.wim 2 (i.e. Microsoft Windows Setup (x64) via NTlite
getting this error msg
0XAIr.jpg

on the same Pen drive, using W11 24H2 unmodified ISO with it's default (new) installer, no issue
 
That error message wasn't caused by this reg change. Your boot.wim is missing a driver.

The hack changes the default CmdLine reg value from "winpeshl.exe" to "X\sources\setup.exe".

winpeshl's role in boot.wim is to run setup.exe if found on the X:\ volume. And the new CmdLine jumps over winpeshl to directly run setup. Otherwise, it's the same boot.wim.
 

Attachments

  • Capture.PNG
    Capture.PNG
    59.9 KB
  • Windows 11 x64-2024-08-07-14-45-35.png
    Windows 11 x64-2024-08-07-14-45-35.png
    20.3 KB
  • Windows 11 x64-2024-08-07-14-53-48.png
    Windows 11 x64-2024-08-07-14-53-48.png
    14.4 KB
garlin said:
That error message wasn't caused by this reg change. Your boot.wim is missing a driver.

The hack changes the default CmdLine reg value from "winpeshl.exe" to "X\sources\setup.exe".

winpeshl's role in boot.wim is to run setup.exe if found on the X:\ volume. And the new CmdLine jumps over winpeshl to directly run setup. Otherwise, it's the same boot.wim.
Click to expand...
I'm not saying that this reg hack causing this particular error
just asked as I've not faced this issue earlier while using the unmodified ISO/boot.WIM
neither have seen it earlier before 24H2, i.e. on 22/23H2 ISO

I did no other modification into the boot.wim 2 except just adding this reg.

As you're saying boot.wim is missing a driver (probably Intel RST driver I guess) then why there's no issue while I use the same boot.wim without adding the .REG file?

P.S: This is obvious but still mentioning
the issue is only there if I test this on real HW, on VM, no such error
 
Last edited:
If you're having driver loading issues, try this:
Code: 
[HKEY_LOCAL_MACHINE\SYSTEM\Setup]
"CmdLine"="cmd /c start /min wpeinit && \\sources\\setup"
 
garlin said:
If you're having driver loading issues, try this:
Code: 
[HKEY_LOCAL_MACHINE\SYSTEM\Setup]
"CmdLine"="cmd /c start /min wpeinit && \\sources\\setup"
Click to expand...
adding to the same boot.WIM (2) Microsoft Windows Setup (x64) via NTLite
with the same/earlier reg? like this?
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\Setup]
"CmdLine"="X:\\sources\\setup.exe"

[HKEY_LOCAL_MACHINE\SYSTEM\Setup]
"CmdLine"="cmd /c start /min wpeinit && \\sources\\setup"
Click to expand...
or excluding the earlier, just this?
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\Setup]
"CmdLine"="cmd /c start /min wpeinit && \\sources\\setup"
Click to expand...
Click to expand...
Guess you're referring to the second one, still, asking for confirmation.
 
garlin said:
Just the new line, added to boot.wim (Setup).
Click to expand...
garlin tried this

-load the vanilla 26100.1 boot.wim 2 (setup) with NTL
-added only this new reg into it (reg section)
-no other modifications done
-made the ISO & copy it to the (ventoyed) flash drive

Same result,
while the old (23H2) setup is there working
but after selecting lang & KB layout, stuck on the same media driver missing page on the next screen
 
You're using Ventoy. Run this on a normal Rufus-prepared USB drive.

Ventoy does some bootloader tricks in order to host different ISO volumes on the same physical drive.
[issue]: Win11 - Missing Media Driver #1133

Windows PE startup sequence explained

"P.P.S. If \windows\system\winpeshl.exe is deleted, the system boots and then restarts.

Here is my best guess after experimenting with a Win10 boot.wim image #2 (#2 is the image used for installs)…

Winpeshl.exe is run (required file) – if winpeshl.ini exists the application(s) specified in X:\Windows\system32\winpeshl.ini are run.
If the winpeshl.ini file exists but is invalid, a cmd shell will be opened and the process will stop.
If winpeshl.ini does not exist then X:\Setup.exe is run, if it exists.
X:\Setup.exe allows the user to choose a language and then choose either Repair or Install – if you choose Install it runs X:\sources\setup.exe.

The \Sources\Setup.exe will look on all drives for a \Sources folder containing both the file “setup.exe” and a install.wim, install.swm or install.esd file in the same folder – if not found it will prompt you to install CD\DVD drivers. Windows can then be installed using the \Sources\install.* files.
If no winpeshl.ini file is found and no X:\Setup.exe is found then cmd /k X:\Windows\system32\startnet.cmd is run.
Usually, Windows PE’s boot.wim install images contain the X:\Windows\system32\Startnet.cmd file which just contains the command Wpeinit.exe.
Wpeinit.exe loads network resources and coordinates with networking components like DHCP. It also loads a wpeinit unattend XML file if it can find one at X:\Unattend.xml.
When Wpeinit.exe completes, the Command Prompt window is displayed.
The boot process of Windows PE is complete."

Posted by steveSi | 2019-01-09, 13:08
 
garlin said:
You're using Ventoy. Run this on a normal Rufus-prepared USB drive.

Ventoy does some bootloader tricks in order to host different ISO volumes on the same physical drive.
[issue]: Win11 - Missing Media Driver #1133

Windows PE startup sequence explained

"P.P.S. If \windows\system\winpeshl.exe is deleted, the system boots and then restarts.

Here is my best guess after experimenting with a Win10 boot.wim image #2 (#2 is the image used for installs)…

Winpeshl.exe is run (required file) – if winpeshl.ini exists the application(s) specified in X:\Windows\system32\winpeshl.ini are run.
If the winpeshl.ini file exists but is invalid, a cmd shell will be opened and the process will stop.
If winpeshl.ini does not exist then X:\Setup.exe is run, if it exists.
X:\Setup.exe allows the user to choose a language and then choose either Repair or Install – if you choose Install it runs X:\sources\setup.exe.

The \Sources\Setup.exe will look on all drives for a \Sources folder containing both the file “setup.exe” and a install.wim, install.swm or install.esd file in the same folder – if not found it will prompt you to install CD\DVD drivers. Windows can then be installed using the \Sources\install.* files.
If no winpeshl.ini file is found and no X:\Setup.exe is found then cmd /k X:\Windows\system32\startnet.cmd is run.
Usually, Windows PE’s boot.wim install images contain the X:\Windows\system32\Startnet.cmd file which just contains the command Wpeinit.exe.
Wpeinit.exe loads network resources and coordinates with networking components like DHCP. It also loads a wpeinit unattend XML file if it can find one at X:\Unattend.xml.
When Wpeinit.exe completes, the Command Prompt window is displayed.
The boot process of Windows PE is complete."

Posted by steveSi | 2019-01-09, 13:08
Click to expand...
The problem is I can't leave ventoy as I deal with multiple ISO for multiple systems, so I have to keep all those ISOs inside the USB drive
that's the reason I started using ventoy since 2020/21 & left Rufus because that doesn't have this multiboot feature.

Apart from Ventoy, there're a few apps that support the multiboot function, already tried YUMI-exFAT-1.0.2.7 but with that too, it's the same issue as Ventoy, gonna try Easy2Boot v2.20 & WinSetupFromUSB 1.10

EDIT: tried WinSetupFromUSB 1.10, same result

If there is any other alternative that supports multiboot, let me know.
 
Last edited:
Windows 11 2024 Update (24H2), How to Install It on Unsupported CPUs
www-hwupgrade-it.translate.goog

Windows 11 2024 Update (24H2), come installarlo su CPU non supportate

Lo sviluppatore di Rufus ha creato uno script che consente l'aggiornamento a Windows 11 24H2 su dispositivi non ufficialmente supportati. La prossima versione del software includerà questa funzionalità, semplificando il processo per gli utenti.
www-hwupgrade-it.translate.goog www-hwupgrade-it.translate.goog
Script in progress in Rufus (not tested yet):
reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\CompatMarkers" /f 2>NUL
reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Shared" /f 2>NUL
reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators" /f 2>NUL
reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\HwReqChk" /f /v HwReqChkVars /t REG_MULTI_SZ /s , /d "SQ_SecureBootCapable=TRUE,SQ_SecureBootEnabled=TRUE,SQ_TpmVersion=2,SQ_RamMB=8192,"
reg.exe add "HKLM\SYSTEM\Setup\MoSetup" /f /v AllowUpgradesWithUnsupportedTPMOrCPU /t REG_DWORD /d 1
 
Windows 11 24H2, installation files can't be removed. And they are 8.63GB
www.hwupgrade.it

Windows 11 24H2, i file dell'installazione non possono essere rimossi. E sono 8,63GB

L'ultimo aggiornamento di Windows 11 sta causando problemi agli utenti che non riescono a liberare spazio sull'unità di archiviazione. Microsoft potrebbe aver introdotto intenzionalmente questa novità con i nuovi Checkpoint Cumulative Updates.
www.hwupgrade.it www.hwupgrade.it
Does anyone know?
 
clarensio said:
Windows 11 24H2, installation files can't be removed. And they are 8.63GB
www.hwupgrade.it

Windows 11 24H2, i file dell'installazione non possono essere rimossi. E sono 8,63GB

L'ultimo aggiornamento di Windows 11 sta causando problemi agli utenti che non riescono a liberare spazio sull'unità di archiviazione. Microsoft potrebbe aver introdotto intenzionalmente questa novità con i nuovi Checkpoint Cumulative Updates.
www.hwupgrade.it www.hwupgrade.it
Does anyone know?
Click to expand...
Yeah, microsoft know and are apparently 'working on a fix' . Being covered by many places.
 
Also, SFC bugs have been reported after the latest update ...

"Windows Resource Protection found corrupt files and successfully repaired them. For online repairs, details are included in the CBS log file located at windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline repairs, details are included in the log file provided by the /OFFLOGFILE flag."
 
Time to let this one go for now till everything is fixed in 24h2. I am still in 22H2 and staying till I know everything is good and that I am not losing performance switching to another update.
 
You must log in or register to reply here.
Back
Top