Win10XPE - Build Your Own Rescue Media [2]

biatche · 1 Day Ago

SIW2 said:

It is easily done manually in about 30 seconds

Note: boot.wim image 2 does not have wireless.

I add it myself but I cba to explain that bit. It doesnt matter to me because I dont use wireless, but I add it anyway

dont worry about explaining the steps, i know how to do it manually. and i dont need/want wireless (i only use ipxe/lan). was hoping this could all be done within the program. i recall ages ago using win10pese or something and i recall that the source utilized was boot.wim. but all good.

well seems like the older variants did have some features/methods i prefer over the new.

speaking of which... i wish it'd generate the wim only without the iso... but i guess i'd have to use my own scripts again..

i might as well ask, what's the recommended way of managing own scripts? there a recommended custom directory for it or something?

SIW2 · 1 Day Ago

dont worry about explaining the steps, i know how to do it manually. and i dont need/want wireless (i only use ipxe/lan). was hoping this could all be done within the program.

You might be able to change some of the build script. I think there was a script called core build or something like that. I havent looked at it for quite a while. You can dig around and have a play. There are probably some lines extracting winre.wim with wimlib

i dont need/want wireless

Neither do I but I put it in anyway.

post #2368

Cipri · 1 Day Ago

biatche said:

speaking of which... i wish it'd generate the wim only without the iso... but i guess i'd have to use my own scripts again..

i might as well ask, what's the recommended way of managing own scripts? there a recommended custom directory for it or something?

Create boot.win only without the iso: In Create ISO there is an almost invisible button (below R of Rufus download word) to show Advanced Options
MoPlugins is the directory for own scripts files.

biatche · 1 Day Ago

Cipri said:

Create boot.win only without the iso: In Create ISO there is an almost invisible button (below R of Rufus download word) to show Advanced Options
MoPlugins is the directory for own scripts files.

lol wtf im impressed you actually noticed such a mini tickbox

KernelPower · 19 Hours Ago

KernelPower said:

Is there someplace to download previous builds of Win10XPE.

Kyhi said:

WHY?

As one builds upon the other - and they are all backwards compatible...

I use it for troubleshooting. I went back and built my project from a build from last 8-26-24 and it fixed my taskbar issue. I just wanted to see where something changed. I ended up grabbing the startallback script and .exe and inserting it into the newest build and that seemed to fix the problem. I haven't investigated why it worked yet. Its on my todo list though.

KernelPower said:

I used Win11 24H2 for my build and I am having an issue when PXE booting it loads in very low resolution(800x600). To fix this I installed intel display drivers. However when the drivers load and the screen flashes to the correct resolution(1920x1080 or 3840x2160 depending on monitor) the taskbar remains in the middle of the screen about where 800x600 would be.

biatche said:

oh i face this same issue too. i'd like to know, there any reason to use win11 base instead of win10 base?

I fixed it by grabbing an old startallback script and .exe(3.5.7) from an old build. I need to use Win11 because on one of the machines I built the processor was not supported by Win10 at the time. Its only a matter of time before that becomes more common.

Homes32 · 6 Hours Ago

biatche said:

itll work for most people yeb, i do have a special setup, this way, i wont need to ever use original notepad.exe junk. this sort of issue has never arised.

As KYHI alluded, The ShellExecute line will launch a program, then wait until it terminates. when it detects the process has died then it will move on to the next line of code, in this case re-encode the script. notepad launcher starts notepad++ then terminates. Winbuilder sees that notepad launches is dead and re-encodes the script.

biatche said:

but its a simple question -- why re-encode? what purpose does it serve? why not utilize a permanent custom file instead like 'build core'. its done there, so it makes perfect sense.

because it's more of a sandbox/temporary solution that's meant to be easy to coach someone though adding a few lines of script.

It's expected that advanced users will already know how to use a permanent custom script/file and link it into the project so no need to add clutter. This particular feature is for beginners and quick testing, without having to worry about the structure of the underlying script.

- - - Updated - - -

biatche said:

i might as well ask, what's the recommended way of managing own scripts? there a recommended custom directory for it or something?

since your an experienced user, best practice is to put your scripts custom scripts in their own directory somewhere. Then you can link to that directory and they will be included in the project, without mixing them in with the project files. This also simplifies updates as you can have multiple releases all pointing at your single folder.

Once you have your directory, open Projects\Win10XPE\Folder.Project in notepad/notepad++ and add your directory to the [Links] section.

Example:

Code:

[Main]
Title=Win10XPE
Type=XPEPlugin
Description=Build Win10XPE by using an Original Windows 10 ISO x86 or x64...#$xThe build is based on the Winre.wim recovery environment.
Author=ChrisR
Date=2018.01.30
Version=001
Selected=True
Download_Level=0
Contact=


[Links]
Projects\MyPlugins\*.*
Projects\MoPlugins\*.*
Projects\CustomPlugins\*.*                           <-------------------------- HERE

karl500 · 1 Hour Ago

karl500 said:

Is there some plan do make this happen ?
Or with some guidance maybe I could take a look at it myself ?

Hi, any chance for ARM64 support? Or is this just not happening ?
As I said maybe I can take a look into it? Any chance to get access to the source code ?

Anyway, a great project alltogether and works excellent.