Win10XPE - Build Your Own Rescue Media [2]

Kyhi said:

Well I have to wonder how your PE differs from the Project PE, which has been out and since 2015

Attachment 415289

Thanks @Kyhi and @fgaifen I just tested this one my friend! It worked out! Successes

Are there updated scripts? The ones in the second post no longer work and Chrome will always fail to build with a registry write error when building the project.

Also, aside from using the "Custom" folder, how would I add a program like MyDefrag or SDelete to the build?

Hello all... been a long time since I have been around ... and been a while since I worked with PE...

so, due to the company I work for, I am unable to use a build tool to build PE disks... and if/when I create a viable disk, I have to document what I did to build it... I am working on a new build and using the WInRE wim as the base and adding stuff to it..

Now, I have come across this before - probably something simple that I have forgotten how to fix, but when I boot my ISO image, instead of coming up with the dos prompt, I am getting the windows 10 setup window (where it is asking you to select what language to install, time and currency format, etc...)... and am wondering if anyone here remembers (or knows) how to get around that...

I am working on a new build and using the WInRE wim as the base and adding stuff to it..

Now, I have come across this before - probably something simple that I have forgotten how to fix, but when I boot my ISO image, instead of coming up with the dos prompt, I am getting the windows 10 setup window (where it is asking you to select what language to install, time and currency format, etc...)... and am wondering if anyone here remembers (or knows) how to get around that...

One way is to put this winpeshl.ini file in windows\system32 of the bootable wim image

winpeshl.ini

Code:

[LaunchApp]
AppPath = cmd.exe

********************************************************************************************
if it is the standard ms boot.wim that comes with the installation media, image 2 is bootable

if winpeshl.ini is not present then setup.exe will be launched
************************************************************************************************

If it is winre.wim it has only one image and there is already a winpeshl.ini present pointing at recenv.exe. Replace it with the above or delete it.

Thanks... Just tried it... same results... it appears to be launching it's own boot image and then the win10 setup. .. instead of the boot.wim file that I placed on the ISO. (wim file is CDROOT\Sources filename: boot.wim)

Basically, I exported index1 from the winre.wim from the windows iso file, mounted it via DISM and then copied the necessary files over. I then loaded the software hive, renamed a few .reg keys that I knew that I would need to keep (added .RE at the end of their names). I then exported them to .reg files, unmounted the WinRe software hive... moved the hive to a .old folder and then copied the Windows software hive files from the original install media. I then imported the keys, renamed the originals to .old and renamed the .RE keys in the 'new' software hive to the original names... I then removed the 'Interactive User' values from classes root, unloaded the hive, unmouted the wim file using the /commit switch and then replaced the original boot.wim on the PE iso with the new one...

- - - Updated - - -

Ok, so i started over... trying to determine what is causing the problem. The WinRE.Wim file has two indexes... I went ahead and used DISM to export 1 and 2 to two separate WIM files. I mounted each image with DISM and only added the winpeshl.ini file... both act as if they are ignoring the boot win and loading directly into a mini-wim or something.. where the start the setup... I can hit shift-f10 to get to the cmd prompt and task manager works... when I go to the setup that is running, it is running setup.exe from the 'sources' folder... which doesnt exist on the iso so far as i can find and doesnt exist inside my wim file...
------------
Update: I figured it out... I was being a dummy and was updating the wrong iso file...lol my test VM was pointed to one ISO but I was saving the wim to a different one.. *duh*

Kyhi said:

I have recently swap Drives and I will have to redo the Mega Links in Post #2 - kinda sucks when a 14 year old spinner with a lot of Data starts to fail... But the good news is it is now a 1TB SATA-lll SSD

LINKS in Post #2 Should work now...

Thank you! I'll rebuild my project in a moment, after updating from those links.

Oh, and I still use platters for my important stuff. They're in a Synology NAS with BTRFS for bit-rot protection. That gets backed up also.

doudiii said:

@adritec
i tested Linux File Systems for Windows by Paragon Software in basic build ok
Attachment 414725
i see you have AOMEI Backupper in your build, try to build new one without AOMEI Backupper ...

Hello @doudiii how are you? I saw this on your desktop print and I was curious, I inserted the "Rainmeter" program but mine doesn't open after starting my winpe. Does yours open automatically? If so, how did you do it, can you help me? Thanks.

bginfo.zip

It is a pecmd script with a .wcs extension.

to make it work, add these lines to your pecmd.ini

ENVI PECMD=PECMD.EXE
ENVI EDIT=notepad
REGI $HKCR\.wcs\=wcsfile
REGI $HKCR\wcsfile\=WCS File
REGI $HKCR\wcsfile\DefaultIcon\=%SystemRoot%\SYSTEM32\%PECMD%,0
REGI $HKCR\wcsfile\shell\open\command\=%PECMD% "LOAD %L"
REGI $HKCR\wcsfile\shell\Edit\command\=%EDIT% %L
REGI $HKCR\inifile\shell\PECMD\=PECMD load
REGI $HKCR\inifile\shell\PECMD\command\=%PECMD% "LOAD %L"
REGI $HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\PATHEXT=.COM;.EXE;.NTR;.NTE;.NTX;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.WCS;.WC E;.WCX;.WCZ