Win10XPE - Build Your Own Rescue Media [2]

i found by using 'Regshot 1.9' some reg key not write corectly in admin session ...
one of this is TEMP & TMP ...

Code:

;syst
[HKEY_USERS\.DEFAULT\Environment]
"TEMP"=hex(2):42,00,3a,00,5c,00,54,00,65,00,6d,00,70,00,00,00
"TMP"=hex(2):42,00,3a,00,5c,00,54,00,65,00,6d,00,70,00,00,00

;admin
;[HKEY_USERS\.DEFAULT\Environment]
;"TEMP"=hex(2):42,3a,5c,54,65,6d,70,00
;"TMP"=hex(2):42,3a,5c,54,65,6d,70,00

Steve C said:

I downloaded the latest Windows 10 ISO file using the Media Creation Tool but the WinBuilder Tool complains the mounted ISO contains no install.wim image. What now?

Could be that the ISO contains ESD instead of WIM.

When I built Win10XPE today I got the following error messages, which I didn't get during last build about one month ago:





Win10XPE is 2023-08-23 with all updates from post #2. Source is Win10 20H2 (10.0.19041.631). Where could these errors come from? Antivirus is disabled for Winbuilder directory.

- - - Updated - - -

SIW2 said:

Just made 19045.4046 winpe.

Used boot.wim image 2 as the base

Kyhi said:

Nothing New There - Old News and has been supported for some time, really....

Are there any disadvantages with Win10 22H2? On GitHub 20H2 is the last mentioned build and 20H1 is the recommended one.

Steve C said:

I downloaded the latest Windows 10 ISO file using the Media Creation Tool but the WinBuilder Tool complains the mounted ISO contains no install.wim image. What now?

There is a \sources\install.esd

There are various ways to convert ESD files to WIM format for WinBuilder.

Open a cmd.exe window as administrator, go to the folder where the ESD file is located and enter the following command:

dism /Get-WimInfo /WimFile:install.esd

Choose the version of Windows to extract (Index: X)

Enter the following command to convert to WIM, replacing X with the desired index:

dism /export-image /SourceImageFile:install.esd /SourceIndex:X /DestinationImageFile:install.wim /Compress:max /CheckIntegrity

There are programs available for automatic conversion such as WinReducer ESD (instructions at Extract Install.WIM to Install.ESD with WinReducer ES-WIM converter) or ESD-Decrypter.

Hey Guys, I think I found some issues with NET_Desktop_Runtime_XPE.script

NET_Desktop_Runtime_XPE.script
Is using the variable %PEPrograms% below,
In a Booted PE, I get %PEPrograms% in the registry and in the Path Environment
You will find them starting around line 80 in the .script, there are three of them.
The only other reg entry that I saw showing up in the registry was the %ProgramVer%,1
Next one was the one responsible for the path problem.
RegWrite,HKLM,0x1,"Tmp_System\ControlSet001\Control\Session Manager\Environment","Path","%SysPath%;%PEPrograms%\%ProgramFolder%\;"

And a typo here as well maybe...
If,%Architecture%,Equal,x86,Begin
RegWrite,HKLM,0x4,"Tmp_Software\dotnet\Setup\InstalledVersions\x86",%ProgramVer%,1
RegWrite,HKLM,0x1,"Tmp_Software\dotnet\Setup\InstalledVersions\x64","InstallLocation","%PEPrograms%\ %ProgramFolder%"
End \x64 <-- I think this should be x86

Regards
RoyM