Win10XPE - Build Your Own Rescue Media [2]

@thenicestguy24
add this to Additions under "Add or Edit converted PE registry"

Code:

//Rounded Corners
RegWrite,HKLM,0x4,Tmp_Software\Microsoft\Windows\Dwm,ForceEffectMode,2
//-----------------------------------
RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Services\FBWF,WinPECacheThreshold,20000
//-----------------------------------
//Enable Launch Folder Windows in a Separate Process
RegWrite,HKLM,0x4,Tmp_Default\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced,SeparateProcess,1
//fix for WinXShell with dpi
RegWrite,HKLM,0x1,"Tmp_Default\Software\Microsoft\Windows\CurrentVersion\App Paths\WinXShell.exe",,"X:\Program Files\WinXShell\WinXShell.exe"
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\Windows\CurrentVersion\App Paths\WinXShell.exe",,"X:\Program Files\WinXShell\WinXShell.exe"
//avoid flashing screen thanks to Noel-Blanc
RegWrite,HKLM,0x4,Tmp_Default\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced,StartMenuInit,13
//**************************************************

with basic build and this


nb: do not updated sab ( with lasted ver calendar not work, vol level too , ...)

thenicestguy24 said:

...
Where do you go in the PE builder to choose boot.wim instead of using winre.wim?

with "22631.3296" i get bsod when booting , i updated some sys 32 file from my system host and boot ok
ex:

Code:

;3085
C:\Windows\System32\actxprxy.dll
;3235
C:\Windows\System32\aepic.dll
C:\Windows\System32\apphelp.dll
C:\Windows\System32\AppResolver.dll
;2506
C:\Windows\System32\avicap32.dll
C:\Windows\System32\avifil32.dll
C:\Windows\System32\batmeter.dll
;3235
C:\Windows\System32\cdp.dll
;2506
C:\Windows\System32\comctl32.dll
C:\Windows\System32\CompMgmtLauncher.exe
;3085
C:\Windows\System32\CoreMessaging.dll
;2506
C:\Windows\System32\CoreUIComponents.dll
;3235
C:\Windows\System32\d3d11.dll
;2506
C:\Windows\System32\DataExchange.dll
;3235
C:\Windows\System32\dcomp.dll
;2506
C:\Windows\System32\DDORes.dll
C:\Windows\System32\desk.cpl
;2506
C:\Windows\System32\deviceaccess.dll
C:\Windows\System32\DeviceCenter.dll
;3235
C:\Windows\System32\devmgr.dll
;10.0.10586
C:\Windows\System32\Display.dll
;2715
C:\Windows\System32\dlnashext.dll
;3235
C:\Windows\System32\dmenrollengine.dll
;2506
C:\Windows\System32\dmocx.dll
;19041.572
C:\Windows\System32\drvload.exe
;3235
C:\Windows\System32\dsound.dll
C:\Windows\System32\dsreg.dll
;2506
C:\Windows\System32\dwm.exe
;3235
C:\Windows\System32\dwmcore.dll
;3085
C:\Windows\System32\dwmredir.dll
;3235
C:\Windows\System32\dxgi.dll
;2506
C:\Windows\System32\dxtrans.dll
C:\Windows\System32\eappcfg.dll
;3085
C:\Windows\System32\esent.dll
;3235
C:\Windows\System32\FntCache.dll
;0.2309.22621.2792
C:\Windows\System32\GameInput.dll
....

@thenicestguy24



you have done something wrong, or your win10xpe is screwed up.

I just downloaded the en-us_windows_11_consumer_editions_version_23h2_x64_dvd_8ea907fb.iso from on click

With that iso there is no need to use boot.wim. It should be fine using winre.wim

install.wim is dated 1/10/23



and it is 2428

You might come across some media where it is better to use boot.wim image 2 as the base.

Years ago I persuaded I persuaded Chris not to use boot.wim and instead to extract winre using wimlib because it made sense at the time.

But we didnt know back then that MS would much later be mixing different builds for the bootable wims and install.wim

I havent looked at win10xpe for a while, but if there isnt a way to select boot.wim, a convoluted workaround should be possible.

something llike this will probably work

1. export boot.wim image 2 as winre.wim

2. change the name and description in your exported winre.wim from
Microsoft Windows Setup (amd64)
to
Microsoft Windows Recovery Environment (amd64)

3. delete all images from install.wim except the one you want to use

4. replace winre.wim in the single remaining image with your newly created version.

the level volum & calendar not working is from sab with win11 style only, with win7 & win10 style is ok

Code:

https://imgbox.com/f2Hfp2d9

doudiii said:

@thenicestguy24
add this to Additions under "Add or Edit converted PE registry"

Code:

//Rounded Corners
RegWrite,HKLM,0x4,Tmp_Software\Microsoft\Windows\Dwm,ForceEffectMode,2
//-----------------------------------
RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Services\FBWF,WinPECacheThreshold,20000
//-----------------------------------
//Enable Launch Folder Windows in a Separate Process
RegWrite,HKLM,0x4,Tmp_Default\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced,SeparateProcess,1
//fix for WinXShell with dpi
RegWrite,HKLM,0x1,"Tmp_Default\Software\Microsoft\Windows\CurrentVersion\App Paths\WinXShell.exe",,"X:\Program Files\WinXShell\WinXShell.exe"
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\Windows\CurrentVersion\App Paths\WinXShell.exe",,"X:\Program Files\WinXShell\WinXShell.exe"
//avoid flashing screen thanks to Noel-Blanc
RegWrite,HKLM,0x4,Tmp_Default\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced,StartMenuInit,13
//**************************************************

with basic build and this


nb: do not updated sab ( with lasted ver calendar not work, vol level too , ...)



with "22631.3296" i get bsod when booting , i updated some sys 32 file from my system host and boot ok
ex:

Code:

;3085
C:\Windows\System32\actxprxy.dll
;3235
C:\Windows\System32\aepic.dll
C:\Windows\System32\apphelp.dll
C:\Windows\System32\AppResolver.dll
;2506
C:\Windows\System32\avicap32.dll
C:\Windows\System32\avifil32.dll
C:\Windows\System32\batmeter.dll
;3235
C:\Windows\System32\cdp.dll
;2506
C:\Windows\System32\comctl32.dll
C:\Windows\System32\CompMgmtLauncher.exe
;3085
C:\Windows\System32\CoreMessaging.dll
;2506
C:\Windows\System32\CoreUIComponents.dll
;3235
C:\Windows\System32\d3d11.dll
;2506
C:\Windows\System32\DataExchange.dll
;3235
C:\Windows\System32\dcomp.dll
;2506
C:\Windows\System32\DDORes.dll
C:\Windows\System32\desk.cpl
;2506
C:\Windows\System32\deviceaccess.dll
C:\Windows\System32\DeviceCenter.dll
;3235
C:\Windows\System32\devmgr.dll
;10.0.10586
C:\Windows\System32\Display.dll
;2715
C:\Windows\System32\dlnashext.dll
;3235
C:\Windows\System32\dmenrollengine.dll
;2506
C:\Windows\System32\dmocx.dll
;19041.572
C:\Windows\System32\drvload.exe
;3235
C:\Windows\System32\dsound.dll
C:\Windows\System32\dsreg.dll
;2506
C:\Windows\System32\dwm.exe
;3235
C:\Windows\System32\dwmcore.dll
;3085
C:\Windows\System32\dwmredir.dll
;3235
C:\Windows\System32\dxgi.dll
;2506
C:\Windows\System32\dxtrans.dll
C:\Windows\System32\eappcfg.dll
;3085
C:\Windows\System32\esent.dll
;3235
C:\Windows\System32\FntCache.dll
;0.2309.22621.2792
C:\Windows\System32\GameInput.dll
....

Thank you doudiii!! I will give this a try.

SIW2 said:

@thenicestguy24



you have done something wrong, or your win10xpe is screwed up.

I just downloaded the en-us_windows_11_consumer_editions_version_23h2_x64_dvd_8ea907fb.iso from on click

With that iso there is no need to use boot.wim. It should be fine using winre.wim

install.wim is dated 1/10/23



and it is 2428

LOL! Yes, I also assumed that I did something wrong based on the difference, I was just more looking for confirmation. So the issue has to be that I built with 2861 for a while and continued to have the startallback issue, then I just changed the PE build to point to the 2428 ISO, so clearly there are still parts of 2861 left behind from where I was building with it, hence the warning about 2 different versions. I will start with a clean build folder with 2428 and that should alleviate the problem. Thanks SIW2!

SIW2 said:

You might come across some media where it is better to use boot.wim image 2 as the base.

Years ago I persuaded I persuaded Chris not to use boot.wim and instead to extract winre using wimlib because it made sense at the time.

But we didnt know back then that MS would much later be mixing different builds for the bootable wims and install.wim

I havent looked at win10xpe for a while, but if there isnt a way to select boot.wim, a convoluted workaround should be possible.

something llike this will probably work

1. export boot.wim image 2 as winre.wim

2. change the name and description in your exported winre.wim from
Microsoft Windows Setup (amd64)
to
Microsoft Windows Recovery Environment (amd64)

3. delete all images from install.wim except the one you want to use

4. replace winre.wim in the single remaining image with your newly created version.

Thank you SIW2!

Kyhi said:

Adding the Optional Add-On Package - still requires the Updated BackUpper Script from Post #2


Win10XPE use WimRE.wim - No option to use Boot.wim (As there are files in RE that are not in PE - thus required files are not extracted from Install.wim to support Boot.wim use............

SIW2 > does not use XPE
XPE > Does not use Boot.wim
Yet SIW2 still posts to confuse this Topic CONSTANTLY...

So let me be Clear SIW2 does not use this project - but is a very well known PE Builder..

Hey Kyhi, I am a bit confused here. Why do you need to files from post #2 when adding the optional add-on packages from mega? It looks like to me that it pulls both the script and the file script for the programs from that package?

Also for the Aomei Backupper issue, I am confusing the add-on packages with the normal built in ones on the XPE build I believe. But I am referring to Aomei Backupper 7.3.3.0, which after looking again, looks like it may be a built in package, and not from the add-on packages:





I will try it after adding your script from post #2 to see if I can get rid of that dll error.

Kyhi said:

Click "Yes" to continue

Thanks, I have been able to click yes and the build continue, I just wasn't sure why I was getting the error stating 2 different versions when I have seen other state that version 2428 have matching wim files. I have figured out that I bonkered up my XPE folder by using 2861 for a while, then moving back to 2428 which is causing this file version mismatch.

- - - Updated - - -

Kyhi said:

Adding the Optional Add-On Package - still requires the Updated BackUpper Script from Post #2

Hey Kyhi,

So due to my pe builder being borked by using 2 different versions of Win11 as explained in my last post. I started with a brand new clean build folder and used Win11 2428 (this did fix the different wim versions warning). I then downloaded all the add-on packages from mega, and tried Aomei as is and I got the dll error in PE. I then replaced the script file with the script from post #2 in this thread, still the same dll error. I did get aomei to work but the only way it worked was to download both script files from here: Win10XPE_2023-08-23 - TheOven.org

Which brings me to something I have wondered for a little bit now. Back about 5 or 6 years ago, there was a thread on theoven.org that had a TON of user submitted scripts / apps for adding into PE. A lot of these were added by you into that thread ( I even made one or 2 and added them in there), but each time someone made a new script, they would create a new post in that thread and attach the files into it. That thread had so many good apps in it but it looks like it has possibly been removed. Is there a way that you could talk to APT and have that thread put back online?

did it say what the .dll was?

v7.3.4 is available Changelog – AOMEI Backupper

SIW2 said:

did it say what the .dll was?

Yes

thenicestguy24 said:

When launching it in PE, I get this error "lib7zg.dll was not found" I assume that this could be related to using Win 11 2428 instead of Win 10 20h1? Because the builder gives no errors or warnings when building Aomei in the logs.