Win10XPE - Build Your Own Rescue Media [2]

Wiebenor · 27 Aug 2023

I have been using this since back when Win7PESE was the big thing to use, plus I've used mostly everything since, and I'm used to that "old" way of doing the projects, and all my "old" plugins I'd use for advanced things have, for the most part, disappeared. Yes, I was only mainly slightly better than a script kiddie, but I was proficient in finding since, or multiple, scripts for copying parts from, editing, or, using them as templates. But now??? Everything just feels so different, and honestly, I'm one of those who, when they get into a routine, or doing something a certain way, it can be hard to catch up.

For a reference to what I can do, I was the one who provided the original files for the WMP "dark" skin, although my username seems to have disappeared from the forum's database for some reason, and I tried recreating it, and well, it won't send the activation email to my registered email, which is why I'm here instead of there... another thing I'm proficient at, is taking the windows 8 start screen background and removing unwanted backgrounds to save space, as well as replacing the main one with a custom one... that, of course has nothing to do with my problem, but it shows that I'm at the very least, not a COMPLETE idiot. That said though, I certainly feel like one, because yeah, I just can't get it to work as of yet, but I'll check the area you recommended that I check, to see what I might have missed.

Is xpe startup only for USB? That could be my issue, although if that's true, then I wish I could get it ISO compatible, for use with ventoy, so that not every ISO tries loading my custom registry entries...

Also, don't know if this helps, but I generally use regshot while running in PE mode, to monitor the registry during installs, and my resulting file has had all non-registry data removed from it

- - - Updated - - -

Gawd I've been a blooming idiot, TRULY... I had the xpe startup.cmd in the WIM root, NOT the CD root... DOH!!! Maybe I'll get it working now?(yeah, with my luck today???🤣🤣🤣 I'd love to see me try)

**Edit**
I also found an issue, where I wasn't logged in to the application as administrator, and it wasn't allowing me to edit any files that had an edit button on the various plugins, and I just thought that that was some computer error but it was my fault, which then made the other errors more grievous than they had to be...

eLPuSHeR · 28 Aug 2023

ChrisR said:

That's good, and it will be easier for users who still use x86 builds

I've updated the link in the post above.
And to be on the same page, I'm going to update the package, without "ReDeploy" x86 version, due to its size.

A big thank you to both ChrisR and Kyhi.

eLPuSHeR · 29 Aug 2023

I have noticed two issues when comparing with earlier version:

1. I cannot run Auslogics disk defrag portable (older version), because it says opengl32.dll is not found.
2. I select Windows 10 home in Windows sources folder, but when booting it says Windows Enterprise. Not a big deal though.

ChrisR · 29 Aug 2023

Auslogics disk defrag needs some dependencies that are not included by default.
I don't have your portable version but If I refer to the MoPlugins\Apps\HD Tasks\Auslogics_DiskDefrag_XPE.Script, you need

Code:

\Windows\System32\opengl32.dll
\Windows\System32\imagehlp.dll
\Windows\System32\glu32.dll
\Windows\System32\??-??\glu32.dll.mui

They are included in Components\DirectX plugin
Or, add these 4 lines in Additions plugin:

Edit "Add Windows 10 Files and Folders", add the dependencies, then save and close notepad.
You can include them directly with the little "Play" button. Then in Create ISO, use "Create boot.wim and ISO" button.
To have them when building, enable the checkbox and the Additions plugin

#
Yes, all constructions display Windows Enterprise, regardless of the edition (Home, Professional,...) selected.
The name is stored in ProductOptions, ProductPolicy (built using windows 10 enterprise) and this name has no impact on the build, just the name displayed.

eLPuSHeR · 30 Aug 2023

Thank you very much ChrisR for clarifying things up.

JOKER77 · 04 Sep 2023

Does anyone know why the boot time for a build is the same using a flash memory USB2.0 with read speeds not exceeding 35MB and between flash memory USB3.0 flash with a speed of 150MB or higher?
Is there an option in the project that makes me benefit from the flash boot speed in booting the project?
The way I use it is to export the ISO files to the root of the flash memory formatted with gpt and ntfs and boot with uefi (I don't use rufus or ventoy)

PetePossum · 05 Sep 2023

JOKER77 said:

Does anyone know why the boot time for a build is the same using a flash memory USB2.0 with read speeds not exceeding 35MB and between flash memory USB3.0 flash with a speed of 150MB or higher?
Is there an option in the project that makes me benefit from the flash boot speed in booting the project?
The way I use it is to export the ISO files to the root of the flash memory formatted with gpt and ntfs and boot with uefi (I don't use rufus or ventoy)

I think the boot process works as follows: Load WIM into RAM (this is the X: Drive after startup), proceed boot process from within RAMDISK. In other words, the USB speed really only matters when loading a large file (between 700 MByte and 1300 MByte depending on integrated components and plugins). Even a slow speed USB Stick usually handles large files quickly, so the difference in duration is not really remarkable compared to the full boot process. Using your example above with a 1 GB boot WIM, the slow stick would take 30 seconds to read the WIM, the fast stick about 7 seconds... Still a difference, but compared to the full process including hardware detection and all the system startup processes, it does not really matter.

Running APPS from the Y-Drive after boot though, would directly benefit from a better USB speed, especially when dealing with a lot of small files.

This is all different, if you are using flat boot, which means you would extract the WIM image to the USB Stick, similar to booting from a standard windows installation. But this is not the standard...

Homes32 · 09 Sep 2023

ChrisR said:

With latest Windows 11 version the sound requires Admin account login, session.

I have updated the audio patch in PhoenixPE master branch to allow sound under the SYSTEM account with Win11 10.0.22621.1702. These patches are fairly specific to the dll, so it can be expected to break with each new version until a better method is found.

Should be easy enough for you and/or @Kyhi to adapt to Win10XPE.

Cheers!
Homes32

Cipri · 09 Sep 2023

Thanks Homes32

I propose this modification for CreateISO.script:

Code:

/-Windows 11 System Sound Patch
If,Not,%SourceBuild%,Smaller,22000,Begin
//If,%Admin%,Equal,False,Begin (System may be chosen also when Admin is True)
If,Existfile,%Gtarget_Sys%\AudioSrvPolicyManager.dll,ShellExecute,Hide,%GTools%\binmay.exe,"-u #$q%Gtarget_Sys%\AudioSrvPolicyManager.dll#$q -s FB010F849200000085DB -r FB01E9930000000085DB"  
If,Existfile,%Gtarget_Sys%\AudioSrvPolicyManager.dll,ShellExecute,Hide,%GTools%\binmay.exe,"-u #$q%Gtarget_Sys%\AudioSrvPolicyManager.dll#$q -s 83FF017426  -r 83FF01EB26" 
//End
End

doudiii · 10 Sep 2023

JTKim said:

Hello.
When running desktop view (Winkey +D) on "Win11XPE"
About the symptoms of "explorer.exe" re-running
I wonder if you know anything.

this happen only with startallback...
with WinXShell "win + d" & "ShowDesktopButton" work ok
with startallback i mapped "win + d" to Minimize All Windows using ahk & desactived "ShowDesktopButton" 'TaskbarSd,0'
....

ChrisR said:

Win10XPE_2023-08-23 update
....

thankyou four the update :)

Win10XPE - Build Your Own Rescue Media [2]

Found an issue I didn't know I was having, and fixed that as well