Win10XPE - Build Your Own Rescue Media

Agreed, please stop the petty bickering. It lends nothing to WIN10XPE nor to anyone's reputation. Agree to disagree if necessary and please get back to just WIN10XPE. I don't really care about other similar programs or the grand history of what got us here. I just want to know about WIN10XPE, how to work with it and resolve problems I and others come up against while using it.

I'm very close to unsubscribing from this thread because of all the bickering.

Please, please stop.

Me, too, haven't figured out the best/easiest way to go.

Kyhi said:

Q2) Beyond Compare should launch as a 30 Free Trial ??...Reply: I will look into BS Folder compare

BS Folder Compare is very intuitive, but seemed like it was taking a long time to compare things so I compared Beyond Compare, BS Folder Compare, and WinMerge. The difference was crazy. BS Folder Compare took 3:26, WinMerge took 1:34, Beyond Compare took 0:01. I don't know how that is possible. Beyond Compare makes it easier to visualize where the differences are as well. It took me a while to catch on when you said it is a 30-day trial. You never make it to 30 days without a reboot on a repair disk, duh! I regret asking for BS Folder Compare. Everything else is perfect.

Kyhi said:

Test... Be sure to set language scrollbox on App interface..
"\MEGA\Win10XPE-Backup\Projects\MoPlugins\Apps\Accessibility\OneLoupe_XPE.Script"
"\MEGA\Win10XPE-Backup\Projects\MoPlugins\Apps\Accessibility\OneLoupe_XPE_File.Script"

OneLoupe works very nice. A keystroke to toggle on and off, and another keystroke to toggle between magnifier and full screen, and it's very fast.

Earlier we spoke of loading the drivers as the way to get full screen resolution. I just tried SetMaxResolution and it works perfectly.

Kyhi said:

Build Core/ "Edit Pecmd.ini" under "_SUB Shortcuts" you will find the shortcuts for "KeyboardLayout.cmd" to prevent shortcut mark out beginning of line with //...

Worked perfectly and I'm starting to learn more about how things work.
Question 1: I also noticed that nowhere near all of the apps are in that file. Where are the links for the others? I also don't see a way of controlling what goes to the task bar.

Question 2: I implemented CherryTree Information database using PStart. Everything on PStart survives boot. Everything runs on Y: except .ini, .cfg, and registry items. That means that I need to have to run something on start for registry items and .ini/.cfg files, and maybe make copies during shutdown. What's the best way to do that? I have to have a couple start on boot too.
Edit:Found what I need on startup in Additions and entering commands in XPEStartup.ini. Now all that's left is a spot for logging to pull back current versions.

Question 3: Misc:
a. Do you use DISM++ for anything?
b. Chrome is checked to be on the taskbar but isn't.
c. IE is on the taskbar but I don't see a way get rid of it.

Question 4: I believe there are some basic concepts I'm missing concerning how to leverage RegShot2 and WhatsChanged to best advantage. Any thoughts appreciated.

Thanks!
PS: I worked with "What Changed". A lot of stuff comes backs but I don't need most of it for apps.
PS: Thank you for all of your hard work to make life better for me and others. The comments that have nothing to do with WinXPE made by some are annoying, confusing, and distracting. The past few days, of 10 notifications I get in my E-mail it seems 9 of them are attacks and responses. If they could and were doing what you are doing, they wouldn't have time.

A1] For the Features you select on Build Core interface the shortcuts are usually pre-configured in Pecmd.ini
Now when you enable an App from the left pane - the shortcut is written into Pecmd.ini
To visualize - after Build - open > /Target/Windows/System32/Pecmd.ini (Now you will see all the App Shortcuts

A1a] On the Apps Interface enable > Pin To Taskbar - in shortcut box...

A2] for Registry Entries you can use Reg.exe via XPEStartup command
for ini & cfg files these would seem Program specific - and would need to be copied to Y
And again then XPEstartup.cmd to copy them to proper location upon startup

For Me - I just attach the basic INI & CFG file(s) to the Script and extract the file(s) to the proper Folder location during the build.. This is all part of the App Integration Process - it is a matter of using Whatchanged & regshot2 to track file and registry changes... Then use Process Monitor to find required System Files, that may not be included in a basic build... this is where it takes experience...

A3a] I prefer ImageX - but usually never use.. I just run MS DISM commands directly..
A3b] Is Chrome set to run from Y - ??
A3c] shortcut internal of Features/IE11.script

A4] A lot of thoughts - But it took me many years and a lot of testing to gain the skills needed to get the whole process down.. But really it is a matter of following the files - the registry changes - the system file dependencies - then knowing how to implement them into a script.. what the script actually does is it pre-installs the program without running the installer.. So what I do is Run the Installer while in WinPE - and record the changes - then create a script of those changes.. Because we know that after a reboot the changes are lost... So we integrate the App via a script..

PS: Thank you for all of your hard work to make life better for me and others. The comments that have nothing to do with WinXPE made by some are annoying, confusing, and distracting.

My Point Exactly.... But as was Pointed out today ChrisR has posted the Project release on Github (By Request because TheOven was down) Which is the same reason I shared My Backup Folder
And he has referenced this Topic in regards to additional support...

ChrisR and I are Co-Authors of this Project, (The Developers of Win10XPE) so there are no issues with the Base of Win10XPE being any different.

Jack,
Let's take OneLoupe for example.... You questioned the language setting being written to file somewhere....
Ok, I went to Website and found an x86.zip and a x64.zip file
I downloaded them both - extracted the x64 package
Booted into Win10XPE (All Programs to RAM)
Launched Whatchanged (File Scan Only) as registry scan is poor with that program..
Launch Regshot2 - took first shot - whole registry
Launched Oneloupe

Took second scan with whatchanged
Found what File Changed (in this case File was Added) the oneloupe.ini
took second shot of whole registry with Regshot
Regshot2 revealed nothing worth using...

Then changed Language(s) via tray icon - and noted the change(s) in the INI file...

Then used XPE Packed Plugin Creator - Pointed to the two zip packages, entered the Program.exe
Then edited the script created to included the system files and to pre-write the lng setting into the oneloupe.ini file.. I simply followed the changes that the program made while in PE and integrated them into the script.....

I test with a Basic Build - all programs to RAM - Thus during testing I only need to scan X drive for changes..
After that the script will decide what to reference to X or Y

Sounds simple enough - But It's Experience...

There are two aspects of the project -
The first aspect is the General User - They select a Few Apps - booted their PC - do what they got to do..
I am a second aspect User - I like to take thing apart, figure out how they work and put them back together...

The Base Win10XPE Project Released By ChrisR - Contains 60 Apps
What I Add to the Win10XPE Base Project is 196 Additional Apps

For Project History - The First Release of Win10XPE contained Limited Features and 10 Apps
Over Time certain Features and Apps where integrated into the Small Base Project..
Reason being Chris does not have the time to maintain or support a Large Project...
So, that is how we roll (Chris & Myself ) with a Small Base Project for General Forum Users & My Large Add-On Package.

I am retired so I have the time to support such a large project... I spend most of my time in the forums helping folks and offering support and advise for the project, when I am not testing New Apps or Features to Integrate into the project..

So This Is My Work From Home Job which occupies most of my time and something I Enjoy !!
KYHI

Kyhi said:

A1] For the Features you select on...

Got it!
- Build Core -> Edit Pecmd.ini = C:\Win10XPE\Custom\Pecmdini
- Tree Selections = C:\Win10XPE\Target\Windows\System32\Pecmd.ini

Question 1: It appears that the C:\Win10XPE\Custom\Pecmdini works by commenting and uncommenting a fixed number of entries while with C:\Win10XPE\Target\Windows\System32\Pecmd.ini the entries either exist or don't exist, depending on whether you check the box on in the tree app. There is also no edit button for this file. That made me wonder if the entire file is rewritten every time someone changes a check box in the tree. Internet Explorer has no options in the WinBuilder interface, yet here I see there is an entry for Start/Network, Desktop, and [PinUtil] entries refer to the shortcut in Start/Network. If I were to remove both [PinUtil] entries and renumber them, and I were to uncheck DISM++, and then Create boot.wim and ISO, would Internet Explorer be re-added to [PinUtil]? Internet Explorer was not re-added to [PinUtil] but I was surprised that DISM++ was not removed as well. Next, I decided to go into DISM++ with the box unchecked and press the green play button to see if it would remove it. To my surprise again, I now had two DISM++ links, with a new one at the very top of the file. So what I gather from this is adding something, and generating with the green play button ONCE works with doing "Create boot.wim and ISO", but removing something requires a regen. However, changes I make in Build Core/C:\Win10XPE\Custom\Pecmdini survive regens. So it seems like everything gets cleared in ISO, Target, and Temp on a regen, and everything else stays. Does this sound about right?

Kyhi said:

...for Registry Entries you can use Reg.exe via XPEStartup command
for ini & cfg files these would seem Program specific - and would need to be copied to Y
And again then XPEstartup.cmd to copy them to proper location upon startup

Question 2: Got it! So then at the bottom of XPEstartup.cmd add entries something like?

Code:

//Begin User Added Entries
REG IMPORT "Y:\User Files\WinXPE Files\REG_Files\MyApp.reg" (which is a previously exported key)
xcopy "Y:\User Files\WinXPE Files\INI_Files\MyApp.ini" "X:\Users\Administrator\AppData\Roaming\MyApp" /S/Q/Y
//End User Added Entries

Question 3: Under what conditions are XPEstartup.ini & .cmd overwritten?

Comment: I don't see myself learning or using DISM so my thoughts are to drop it.

Kyhi said:

...it is a matter of using Whatchanged & regshot2 to track file and registry changes... Then use Process Monitor to find required System Files, that may not be included in a basic build... this is where it takes experience...what the script actually does is it pre-installs the program without running the installer...Let's take OneLoupe for example....
I went to Website and found an x86.zip and a x64.zip file
I downloaded them both - extracted the x64 package
Booted into Win10XPE (All Programs to RAM)
Launched Whatchanged (File Scan Only) as registry scan is poor with that program..
Launch Regshot2 - took first shot - whole registry
Launched Oneloupe
Took second scan with whatchanged
Found what File Changed (in this case File was Added) the oneloupe.ini
took second shot of whole registry with Regshot
Regshot2 revealed nothing worth using...
I test with a Basic Build - all programs to RAM - Thus during testing I only need to scan X drive for changes..
After that the script will decide what to reference to X or Y

Comment: That makes a ton of sense. I didn't do All Programs to RAM, plus I just used WhatChanged figuring why not use one utility to get both at once? But the registry stuff was unusable.

Kyhi said:

Is Chrome set to run from Y - ??

Code:

LINK %Programs%\Network\Google Chrome,Y:\Programs\Google Chrome_x64\Chrome.exe
...
[PinUtil]
TaskBar4=%StartMenu%\Programs\Office\LibreOffice.lnk
TaskBar3=%StartMenu%\Programs\Network\Mozilla Firefox Quantum ESR.lnk
TaskBar2=%StartMenu%\Programs\Network\Google Chrome.lnk
TaskBar1=$Start_Menu\Programs\Network\Internet Explorer.lnk
StartMenu1=$Start_Menu\Programs\Network\Internet Explorer.lnk
StartMenu0=%WinDir%\Explorer.exe
TaskBar0=%SystemRoot%\System32\cmd.exe
TaskBar9=%SystemRoot%\Explorer.exe

LibreOffice, Firefox, and Chrome are NOT on the task bar. I don't know if this is related to the change "Switch to Administrator" or not, but they were there at one time.
Edit: Something is odd. I did a WhatChanged and RegShot2 for a program. Then I rebooted. Now they are on the task bar like they should be.

Questions about WinBuilder/Additions
Question 4: Windows 10 Files and Folders: I assume is if you want something out of your source copy of Windows that isn’t normally taken across you would enter it here?

Question 5: Merge Registry file:
a. I’m guessing that %GCustom% I see is C:\Win10XPE\Custom
b. I’m guessing it could be simply the contents of .reg files that were exported? If so, would this be a better place than in XPEStartup.cmd so I could preserve the files in %CD:~0,3%\Win10XPE_Sources\REG_Files\MyFile.reg?
c. I’m guessing if I executed them with the green play button, I wouldn’t have to do a full regen just as with apps?

Question 6: Add or Edit converted PE registry
So it appears the advantage here is I can delete and replace keys. However, when I press the button and it brings me to c:\WinXPE\Temp\AddReg.txt. Temp? How temporary? Overwritten with every regen?

Question 7: Run this script After checkbox
a. After what, the above or on logout or shutdown?
b. Which format is the RunAfter.script required to be in, batch commands, WSF...?

Non-WinBuilder/Additions Related
Question 8: Regen vs. Create ISO only
I’m guessing that when you uncheck a box, nothing happens other than it is not included, and if you re-check the box it is. If it’s unchecked an you hit the green play button, it simply generates it but still doesn't include it, whereas with a regen, everything gets wiped, recompiled from scratch, and those not checked are not compiled and not even there to be included, so if you want it, without a regen, you have to not only add it, but also press the green play button?

Question 9: C:\Win10XPE\Custom\x64\AdditionalFiles\Program Files
Here it says in the ReadMe.txt:

You can add portable applications here in: \Custom\x64(x86)\AdditionalFiles\Program Files.
Without creating plugins, it is an easy solution for portable Apps.
However No shortcuts are created in this case.
To create them, you can add LINK %Desktop%\xxx|%Programs%\xxx in pecmd.ini

What does that mean, a stand-alone .exe? The program installation that has been 7-zipped? Are these in sub-directories above %Programs%?

Kyhi said:

...as was Pointed out today ChrisR has posted the Project release on Github...because TheOven was down...Which is the same reason I shared My Backup Folder...ChrisR and I are Co-Authors...

I don't know where on Github, but as long as your H: drive works...

Kyhi said:

...I like to take thing apart, figure out how they work and put them back together...

Me too, but my end game having an IT company is to make something more useful than my standard flash drive on my key chain. I could have used that to save a lot of time a few weeks ago when the hard drive got corrupted on a CNC machine at a customer and it took about 2 days to get set back up because we needed just one directory off the old hard drive. I've used PE for restores in conjunction with backup software as well as portable versions of the same utility. In general, the portable version is a more clunky interface, if the portable version doesn't have what you need, it's not as easy to find what you need, and adding it won't be standard. With PE, you have drivers that are easy to find, PNP, and an interface that is a lot more intuitive, which is important, because you don't use it that often. I do a lot in UNIX which can handle massive loads, but not in Linux anymore which cannot, and where there is considerable variation between major distros. Then I had this brainstorm about a USB on my key chain that could do both rescue and contain all of the normal apps,data, and malware eradication tools, plus be a bootable rescue disk and did some Googling to see if there was anything like that. I found there were, and this one was not only maintained, it was the best supported. I also have another that has a lock-unlock switch that I use for infected computers that I will write this to.

Gonna take a few response edits. As you got a lot going on...

Q1] the DEFAULT Pecmd.ini used by the Project is located in >
"\Win10XPE\Projects\Include\x*\AdditionalFiles\Windows\System32\Pecmd.ini"

If you Edit & Customize Pecmd.ini - your custom version is stored in >
"\Win10XPE\Custom\Pecmdini\pecmd.ini"

IF "\Win10XPE\Custom\Pecmdini\pecmd.ini" EXISTS it takes Preference over the DEFAULT and is used in TARGET on every Build

As you Add Shorcuts via Apps Interface - the TARGET Pecmd.ini is edited
If using the Green Play Button to Include an Additional App into Existing Build -
The pecmd.ini is edited again with the new App shortcuts...
The only way to Remove the Prior Selected/Integrated App and Pecmd.ini Shortcuts - is to Rebuild Project

So it seems like everything gets cleared in ISO, Target, and Temp on a regen, and everything else stays. Does this sound about right?

Exactly.....

Q2] Reg Import - is a windows cmd so you use in XPEstartup.cmd is correct...
Where you have to be certain is the Drive Letter & Program Location in registry key...
If you where to export the RegKey from Host - The values would need to be Edited to reflect PE Values

That is why we use > Create ISO > Reg Convert PE Button
To test export a Registry Key from Host - Hit Button - Point to exported reg file - hit Gooo Reg File Button save as script... Those are the regwrite lines we edit and add inside the [Add-Registry] section in the script.
We replace the Hardcoded values with Script Variables - so Reg value is written correctly depending on build..

we also use > Create ISO > Reg Convert PE Button with the Second Shot of Regshot2 (Report.reg.redo.txt)

Those are the Regwrite lines we also edit and can be added inside the [Add-Registry] section in Additions. (Except we do not add the HiveLoad/HiveUnLoad Lines in Additions)

Most likely this helps answer a few of your other questions...

Q3] XPEstartup is only overwritten if script is re-ren - yet only writes your existing values... That is personal for your use - not used by project - but IF EXISTS it is run by Win10XPE at startup

Q4] You would add the Files or Folders you want to be extracted from Source Install.wim into your WinPE Build using Additions.. You can also enable Merge Registry - or Regwrite sections - if regwrite > edit & Save
Be sure to edit - save - enable those Sections as needed...

Q7] It would enable you to Run an Additional Script at end of Build - which we pretty much do not use anymore - as it a leftover part of First Release - but development preceded it....

Q8] After an Existing Build & ISO creation - IF you want to ADD an App without complete Rebuild
Use Green Play Button on App Interface - then use > Create Boot.wim and ISO Button - to integrate New App into Build..
Create ISO Only Button - RePacks the ISO Folder into a New ISO - used if wanting to include Additional Files/Folders in ISO Root after first ISO creation.. Note: Boot.wim is created from TARGET Folder

Q9] Again left over from First Release - But still useful
If you have a Program ( ie 7-Zip) you copy that Program Folder into AdditionalFiles\Program Files
Thus > AdditionalFiles\Program Files\7-zip
It will be included into TARGET / Boot.wim

Same with other AdditionalFiles\ Folders