Tiny WinPE via Win10XPE

This project is the most stable program for me to prepare winpe.

However, the wim file size created according to other winpe projects is really huge.

Can an update come to prepare a small size winpe

Does BOLD print help ??

Does BOLD print help ??

I don't know if using bold was forbidden for forum rules.

I will pay attention after that.

Use LiveSystem pro. this will create small WinPE. the best idea unselect all plugins and use portable apps instead.

Thanks

Okay, this got me a little curious about the plugins/xpeplugins. Aren't these plugins portable already? I thought that was the case, and the plugins are sort of in a portable format using portableapps (as that is what I've seen a couple WinPE's using). Isn't that the case? Or are the plugins integrated into the winpe as actual softwares like installing something in live windows?

Asking because of what @neps4u said, and to use the portable apps instead of the plugins. I thought the option "boot from ram" option was simply putting the plugins inside the boot.wim file but still in portable app mode. Hmm, this is interesting now.

The Applications are integrated into the winpe as actual softwares like installing something in live windows... Some (Not Many) use the Portable App Format...

I haven't came across that many projects I guess then. Bob'Omb's was there. Then strelec and some others not from here. Gandalf, Hiren and I am not sure when I noticed the portable apps format and when I didn't. I simply was in the thought that the plugins were in fact creating some sort of portable apps or sfx archives. If they sort of get integrated into the windows as if they were installed, whenever one would want to update the plugin/software within then they have to build the entire WinPE no? Which would change some stuff in the boot.wim file even if I chose the option to run the programs from USB or does the boot.wim file remains intact from the first time around?

I think I saw somewhere how to integrate portable apps into the windows too as external programs. I guess I'll have to look into it more then. Also, is there an advantage over using the plugins and integrating into the windows over using the portable apps, or vice versa. Could you provide me a little information about it, listing their advantages/disadvantages then? @James

PortableApps (paf) use a self contained wrapper around the programs files - thus they run and save program setting (Registry, LocalData, ProgramData, etc.) within the Apps program folder....
When I create Applications I follow Normal Program Installation - thus I add the registry, LocalData & ProgramData information as required...

In either case in order to run Program - the required (shared) System Files must be present in WinPE, which does not bode well for TinyPE

The other method of App integration is in SFX Format which is a Self-Extracting Exe - that contains the program files - a shortcut is then created to that exe.
When launched the compressed files (Program Files) are extracted to a %Temp% directory and the main program exe is then run... This is another common method used by others in Premade ISO distribution...
Again this method is defendant upon the amount of Ram available, which does not bode well for TinyPE...
Most of the XPE applications are self-updating - thus the User has control to update program files as required, rather then rely on somebody else to Administer Updates..
Those updates are from the OEM Developers Website and require no Administration from a XPE stand point - although from time to time - The processes used to integrate the application within XPE may have to be adjusted, due to OEM Program Changes..
 

Now if you are looking for a one and done WinPE Media creation - then Build with your Programs to USB (Y:\Programs) Y has to be on writable Media (Not Within Booted ISO)
Then after you create the First Build - you can just Update the Program Files as required in the "USB:\Programs" folder...
When using Y with PortableApps (PAF) format then your settings and data will also be saved into the Programs Folder on the USB...
Normally any settings or data saved into the WinPE OS will not be saved upon reboot...
There are many options, variables and considerations when creating personalized WinPE - everybody has the own requirements...
I consider the Masses as a whole and what is the easiest and must User Friendly method to distribute

I see now. I guess, the issue with portable apps requiring more storage/ram to extract first in some %TEMP% place and then running will be an issue for a tiny winpe. If my understanding is correct, these files go to the Ramdisk (or the B partition as default, set by the winpe). That's the same as running the plugin (applications from the ram) unless one were to choose "run from USB" or am I incorrect?

So the only option which doesn't require too much ram is having the programs running from the USB (Y:\Programs) folder. Okay. So, let's say I were to create a WinPE with that option. I get a boot.wim file (inside the sources folder) and all my programs under \Programs folder. When I update those plugins at a later stage, would the process make changes to the boot.wim file too? Or will it be intact. (That's as far as I don't add/remove any programs, just update the ones I implemented)

And what if I were to distribute this WinPE is there a way for people to update those applications themselves? Or would I need to share/publish the whole project folder that Win10XPE creates? (P.S. I am not looking for distribution at this stage, but this is only in the consideration in case and whether at a later stage I decide to publish it here or some other place). I'd want users to be able to add/remove/update whatever they wanted to that winpe for themselves. Would that be possible?

If the "Programs Files" are on USB and not inside Boot.wim - then User could just Update Existing "Program Files" with Newer Program File Version....