Jump to content











Photo
* * * * - 2 votes

Make_WinPE - Make PE WIM File from x64 Windows ISO

winpe wimlib winntsetup wim

  • Please log in to reply
198 replies to this topic

#176 wimb

wimb

    Platinum Member

  • Developer
  • 3755 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 4 weeks ago

7. Copy PE_Tools.zip and Drive.y to Root of any Drive e.g. USB Drive with Portable Tools

   Use 7-zip R-mouse Menu to Extract here to get PE_Tools folder with Portable PE Tools e.g. WinNTSetup and BOOTICE
8. Reboot and Select WinPE-WIM in Windows EFI or Boot Manager Menu
9. On Desktop click on Run_PE_Tools to get Menu with Portable PE Tools

 

Above is the Info for using most important Portable Apps present in the PE_Tools folder as given in the Download.

In fact PE_Tools is already enough to perform most wanted tasks in PE environment.

PE_Tools folder can be on any drive and Run_PE_Tools will launch PE_Tools Menu

 

PE_Tools_2022-04-13_115227.jpg == sshot-2022-06-03-18-23-14.jpg

 

================================================================================

 

For more Portable Apps like in FirefoxPortable  and VLC  and  LibreOfficePortable folder on Drive Y:

- After booting with PE then on Desktop click Set Drive-Y to so that the drive with Drive.y file in root gets Drive Letter Y:

 

Drive Y: is needed to make the icons on PE Desktop work to launch FirefoxPortable and VLC and LibreOfficePortable

In these cases PE Registry is Fixed for using Drive Y: so that e.g. double-click on mp3 will launch VLC player on Drive Y:

 

The Make_WinPE_Trusted-44 folder contains VHD_WIMBOOT.pdf and on page 3 there is extra info:

 

How to Make and Use Drive Y with Portable Apps

 

================================================================================

 

Searching for PStart folder and System_Info folder on any drive is supported as well with icons on PE Desktop

 

As you see there are enough possibilities to adjust the use of Portable Apps to your personal preference.



#177 steve6375

steve6375

    Platinum Member

  • Developer
  • 7491 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars
  •  
    United Kingdom

Posted 4 weeks ago

Ok thanks. I use PESTARTUP  with all my WinPE  WIM files/ISOs.

https://rmprepusb.co...sing-pestartup/

It allows me to add any shortcuts I want to the Desktop and change the wallpaper, etc. without needing to change the wim file at all.

Some WinPEs even have the hook built in to automatically run the batch file on the USB drive to load it (\somename_Startup.cmd).

I use PortableApps on the USB drive so all the apps in that automatically get added to any WinPE I boot to.

There is no messing about with Y: drives and hard-links, etc. and I can get the desktop I want with many different pre-made WinPEs without needing to change the wim.


  • wimb and antonino61 like this

#178 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1483 posts
  •  
    Italy

Posted 4 weeks ago

Sorry folks, 

My usual butt-in time, this time after months - since we have reached a respectable level of "OS miniaturization" (wimboot, miniwin, smartwinpe, and what more and what not),

1) can u tell me how distant this smartwinpe is from, say, miniwin, in terms of constituents and facilities?

2) can we think of a "feasible concoction" of the 2?  



#179 alacran

alacran

    Platinum Member

  • .script developer
  • 2572 posts
  •  
    Mexico

Posted 3 weeks ago

JFYI

 

Ok thanks. I use PESTARTUP  with all my WinPE  WIM files/ISOs.


I use PortableApps on the USB drive so all the apps in that automatically get added to any WinPE I boot to.

 

That approach has severe limitations:

  1. PESTARTUP only works if the PE uses Windows Explorer as shell.
  2. PortableApps and Pstart only work in 32 bits, so they don't work if the PE is only x64 (lacks SysWOW64). 

 

Make_WinPE is capable to make SMALL version PE (using 10 2004 source my SMALL PE version is 347 MB) capable to run only x64 programs, using as shell WinXShell.

 

To take care of PortableApps and Pstart limitations suggested to wimb include in Make_WinPE LaunchBar as an additional option, wich has x64 version, and is very useful to launch/run x64 Apps in only x64 environment, and doesn't require Windows Explorer.

 

Of course in SMALL PE version we need to use real x64 Apps, as an example Apps from PortableApps do not run in only x64 environment, because they use a 32 bit (x86) launcher.

 

LaunchBar-1.jpg

 

alacran


  • wimb likes this

#180 alacran

alacran

    Platinum Member

  • .script developer
  • 2572 posts
  •  
    Mexico

Posted 3 weeks ago

Attached you will find LaunchBar_launcher_x64.7z  Password = alacran

 

It contains a readme file with following info into it:

 

 

For now this is only for testing pourposes, I'm asking wimb to make a little program in AutoIt similar to his PS_x64.exe, but in this case looking in all available drives for \LaunchBar\LB_launcher_x64.cmd, and not for \PStart\PStart.exe.  Having that program in our destop will be a very useful option..

This LB_launcher_x64.cmd is particularly usefull when making an SMALL version PE with Make_WinPE by wimb, because this PE version is only x64 and as it lacks SysWOW64, it's not capable to run 32 bits (x86) programs as PortableApps and Pstart.

It was made for users that do not want to use Drive: Y, and let them be able to have a program to launch x64 Apps from any partition on their USB device or internal HD.

Just extract the two folders into the LaunchBar_launcher_x64.7z to same partition/drive, the folder Portables has some sample files for user convenience, when running LB_launcher_x64.cmd directly or from a link in desktop, it will run LaunchBar_x64.exe and also set the current drive/partition where it is located as the drive where the config file will be launched that in turn will run the Apps located into the folder Portables or any other folder (as long as in same drive) that is set in config_x64.txt

Just add your favorite Apps and edit the config_x64.txt file in accordance.


LaunchBar page: https://www.lerup.com/LaunchBar/

 

@ wimb

 

Hi my friend, would you have some free time to make a little program in AutoIt similar to your PS_x64.exe, but in this case looking in all available drives for \LaunchBar\LB_launcher_x64.cmd, and not for \PStart\PStart.exe?

 

I think it will be very usefull for Small PE version.

 

alacran

Attached Files



#181 wimb

wimb

    Platinum Member

  • Developer
  • 3755 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 3 weeks ago

Attached you will find LaunchBar_launcher_x64.7z  Password = alacran

 

It contains a readme file with following info into it:

 

 

@ wimb

 

Hi my friend, would you have some free time to make a little program in AutoIt similar to your PS_x64.exe, but in this case looking in all available drives for \LaunchBar\LB_launcher_x64.cmd, and not for \PStart\PStart.exe?

 

I think it will be very usefull for Small PE version.

 

 

Good idea and Yes alacran, I will make AutoIt3 program to search LaunchBar on any drive and launch \LaunchBar\LB_launcher_x64.cmd



#182 wimb

wimb

    Platinum Member

  • Developer
  • 3755 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 3 weeks ago

Hi alacran,

 

Attached you will find Run_LaunchBar with program Run_LaunchBar_x64.exe to Find and Run \LaunchBar\LB_launcher_x64.cmd on any Drive

 

Encrypted with password = bootwimb

 

Attached File  Run_LaunchBar-E.zip   589.15KB   8 downloads


  • alacran likes this

#183 alacran

alacran

    Platinum Member

  • .script developer
  • 2572 posts
  •  
    Mexico

Posted 3 weeks ago

Thanks my friend, your Run_LaunchBar_x64.exe works very fine to Find and Run my \LaunchBar\LB_launcher_x64.cmd in any drive.

 

LB_launcher_x64.cmd is the key file that sets the drive containing LB_launcher_x64.cmd as the working drive, and runs LaunchBar_x64.exe program with additional parameters, then loads the config_x64.txt file to create all required links in LaunchBar program to run additional portable Apps, allowing us to use a relative path for the Apps, not having this way to use absolute paths that include the drive letter in the path, so links are created from a set of folders located on any internal or external drive.

 

Now we can say with no doubt, that we have a very good replacement for PortableApps and Pstart (that only work in 32 bits, or when having SysWOW64), when working in only x64 environment (as SMALL PE version) where SysWOW64 and Windows Explorer are absent, and we are not forced to assign a fixed drive letter to the drive containing our Portable Apps.

 

alacran


  • wimb likes this

#184 alacran

alacran

    Platinum Member

  • .script developer
  • 2572 posts
  •  
    Mexico

Posted 3 weeks ago

JFYI

 

I have to admit I prefer to use Drive Y, as I see additional advantages using it, as SendTo context menu additions.

Also the Y drive (even Compact LZX compressed) is very easily cloned to a new drive location (internal or external), keeping the Compact LZX compression, by means of DiskGenius Free Edition, (I recommend the Portable version), in a matter of minutes, primary, logical or GPT partitions are valid targets as long as the target partition is long enought to hold the content of source partition, and DiskGenius not running from the partition we are cloning.

Attached a photo cloning drive Y from a drive/partition in my internal HD to a drive/partition in a USB device by means of DiskGenius running from another partition in Win7x64 that has installed diskmod filter driver from karionyx (signed version of paraglider).

 

But of course all depends of user preferences, that's why I decided to make LB_launcher_x64.cmd and asked wimb to make his new Run_LaunchBar_x64.exe (AutoIt3 program) to find and run \LaunchBar\LB_launcher_x64.cmd from any drive.

 

alacran

Attached Files


  • wimb likes this

#185 wimb

wimb

    Platinum Member

  • Developer
  • 3755 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 3 weeks ago

Good to hear that Run_LaunchBar_x64.exe is working for you.

 

Using Drive Y: is still of value for some cases.

File Association works in registry with absolute path.

For double-click on .mp3 to launch VLC program we fix the PE registry for drive Y:

 

If you share your My_Shortcuts_x64 and My_Shortcuts_x86-x64 with your preferred Set of Links,

then in next version of Make_WinPE_Trusted I can Update the Set of Links for LaunchBar.

Take your time since in the coming weeks I have no time to perform this task.


  • antonino61 likes this

#186 alacran

alacran

    Platinum Member

  • .script developer
  • 2572 posts
  •  
    Mexico

Posted 3 weeks ago

Attached you will find My_Folders.7z  Password = alacran

 

This contains into it the following files, NOT encripted:

  • LaunchBar.7z (updated version including new LB_launcher_x64.cmd and 2 version of config_x64.txt)
  • My_Shortcuts_folders_on drive_Y_for LaunchBar.7z
  • Alacran-Links_for_PE.7z (includes Run_LaunchBar_x64.exe on desktop)
  • Basic-FF-Profile.7z (just in case someone may need it)

Each one has its own Readme file with instructions for use.

 

This files contain basically the updated version of all my additions to Make_WinPE that can be used for general use.

 

The rest of my additions are Drivers for my USB WiFi device, and Spanish lang files added to Explorer++_x64 and IrfanView_x64, also removed almost all lang files in 7-Zip_x64 and PENetwork_x64, keeping only English and Spanish lang files.

 

By the way my new PE_10x64_US_S.wim build made using Make_WinPE_Trusted-44 is now 389 MB a little bigger because of all new drivers you added, (but as long as it is under 400 MB, it is fine to me), and it is fully updated including the Run_LaunchBar_x64.exe on destop.

 

So it is capable to run LaunchBar from the link in desktop pointing to LaunchBar_x64.exe program in Drive Y, and also from any drive, if not using Drive Y, by means of Run_LaunchBar_x64.exe + LB_launcher_x64.cmd

 

Fully tested and all is working fine, not a single issue, congratulations my friend !!!

 

NOTE: Just in case some user may want download links for some portables I use, that are not included into PE_Tools or System_Info (both multi-programs packages by wimb), please see this post.

 

alacran

Attached Files


  • wimb likes this

#187 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1483 posts
  •  
    Italy

Posted 3 weeks ago

Hi folks, 

only one consideration, which I obviously consider useful, otherwise I would not have made it.

Since the virtues of winpe are so meticulously talked about and corroborated in these days (think of the additions of links to crucial files and stuff), would u pls point out what one could do with winpe that could not do without, lest some should think that it is good replacement for ordinary wimboot, miniwin and stuff?

We have been educated to think of winpe as good maintenance software, but now this maintenance sofware seems to have almost more facilities than ordinary os!!! I would not object to it, if only it were the case...



#188 alacran

alacran

    Platinum Member

  • .script developer
  • 2572 posts
  •  
    Mexico

Posted 3 weeks ago

JFYI

 

My new PE_10x64_US_M.wim build made using Make_WinPE_Trusted-44 is now 489 MB only 100 MB bigger than SMALL version, a little price to pay for full access to x86 Apps too, also it is fully updated including the Run_LaunchBar_x64.exe on destop.

 

So it is capable to run Pstart from Y drive or any drive, and additionally run LaunchBar from the link in desktop pointing to LaunchBar_x64.exe program in Drive Y, and also from any drive, if not using Drive Y, by means of Run_LaunchBar_x64.exe + LB_launcher_x64.cmd

 

Also as it has full access to x86 Apps, LibreOfficePortable and FirefoxPortable from PortableApps work very fine in the MEDIUM build.

 

Fully tested and all is working fine, not a single issue, good work wimb !!!

 

Just to make a comparative my current version of Win10XPE_x64.wim is 613 MB, and the MEDIUM version is 124 MB smaller, In both I have same functionality and can run same portable Apps located outside of the PE.

 

alacran


  • wimb likes this

#189 alacran

alacran

    Platinum Member

  • .script developer
  • 2572 posts
  •  
    Mexico

Posted 3 weeks ago

JFYI

 

I will tell you a trick I found to reduce the space used by FirefoxPortable, valid if we don't want to run it from any x86 PE:

1.- Open \FirefoxPortable\App\Firefox folder, delete all content into it, and create (I used Notepad++ for this) a fake 0 bytes file named firefox.exe

2.- On x64 PEs having SysWOW64, the \FirefoxPortable\FirefoxPortable.exe, will run as spected.

3.- On only x64 PEs not having SysWOW64, it is required to run \FirefoxPortable\App\Firefox64\firefox.exe as we do in SMALL version.

 

alacran


  • wimb and antonino61 like this

#190 alacran

alacran

    Platinum Member

  • .script developer
  • 2572 posts
  •  
    Mexico

Posted 3 weeks ago

Forgot to comment I can also confirm SMALL and MEDIUM versions *.wim files run very fine from Ventoy

 

alacran


  • wimb likes this

#191 wimb

wimb

    Platinum Member

  • Developer
  • 3755 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 3 weeks ago

Hi alacran,

 

Thanks for sharing your set of Links as given in My_Folders.7z.

 

Thanks also for testing latest version Make_WinPE_Trusted-44.zip

 

It is a good improvement that we can have LaunchBar located on any Drive.


  • alacran likes this

#192 alacran

alacran

    Platinum Member

  • .script developer
  • 2572 posts
  •  
    Mexico

Posted 3 weeks ago

JFYI

 

I'm writing this from FireFox Portable runing in my just builded PE_10x64_US_L.wim (LARGE version 657 MB) made using Make_WinPE_Trusted-44, and I can say it works very fine.

 

Good work wimb !!!

 

Compared with my current Win10XPE_x64.wim (613 MB) it is a little bigger (44 MB), not too much considering this LARGE version has extra drivers.

 

I also noticed this build has the user files/folders located in usual place \Users\Default folder, that IMHO is the best location for them, just like in Standard OSs, and not in \Windows\System32\config\systemprofile folder, that IMHO is not the best place to locate them.

 

Only think it lacks compared with my Win10XPE_x64.wim is:

 

It is not yet capable to switch to Admin during first stages of boot, (required to run TeamViewerPortable) that is a very useful free progam.

 

My wishes for new Make_WinPE version are:

  • That all versions use same \Users\Default folder.
  • Have the optional capability to boot as Admin in the versions using MS Explorer as Shell.

alacran



#193 ericgl

ericgl

    Frequent Member

  • Expert
  • 338 posts
  •  
    Israel

Posted 2 weeks ago

*
POPULAR

wimb/alacran,

Just released - a very minimal OS, officially from Microsoft:

Info: https://docs.microso...view=windows-11

 

Win11 b22621.1 VALIDATION_OS 2022-05-06 x64 en-US
 
ISO Size: 339 MB
Interface: CLI (Command line).
Supports Win32 apps (x64 ONLY, no WoW3264 by default)
 
Looks very similar to WinPE. The WIM file is just 195MB.
Seems like a good start for a new project to add 32bit app support and Explorer shell interface.

  • gbrao, alacran and antonino61 like this

#194 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1483 posts
  •  
    Italy

Posted 2 weeks ago

mmmm, ... gonna try it out...

 

well, no dice, crashing upon reboot



#195 ericgl

ericgl

    Frequent Member

  • Expert
  • 338 posts
  •  
    Israel

Posted 2 weeks ago

antonino61,

Did you run it without modifying anything, I mean - did you just use the WIM file as it is?


  • antonino61 likes this

#196 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1483 posts
  •  
    Italy

Posted 2 weeks ago

sure. I created an empty vhd and installed it by winntsetup - never booted up (BSOD). am I missing out on something?



#197 alacran

alacran

    Platinum Member

  • .script developer
  • 2572 posts
  •  
    Mexico

Posted A week ago

 

wimb/alacran,

Just released - a very minimal OS, officially from Microsoft:

Info: https://docs.microso...view=windows-11

 

Win11 b22621.1 VALIDATION_OS 2022-05-06 x64 en-US
 
ISO Size: 339 MB
Interface: CLI (Command line).
Supports Win32 apps (x64 ONLY, no WoW3264 by default)
 
Looks very similar to WinPE. The WIM file is just 195MB.
Seems like a good start for a new project to add 32bit app support and Explorer shell interface.

 

 

Thanks for the news, I had no idea it existed.

 

As it is smaller, per sure lacks more features.

 

mmmm, ... gonna try it out...

 

well, no dice, crashing upon reboot

 

 

sure. I created an empty vhd and installed it by winntsetup - never booted up (BSOD). am I missing out on something?

 

Before testing it is required to first integrate some of the CAB files and boot it as a WIM file, not installed in a VHD yet.

It is only a very basic ValidationOS.wim and 17 CAB files en_US + the same 17 CAB files neutral lang.

 

I assume we need to rename the ValidationOS.wim to boot.wim, integrate our desired CAB pakages to be able to test it (all this to only boot in command line).

 

Latter if we want to integrate a GUI shell as WinXShell (easier task and smaller final size) or Explorer (harder task and bigger final size), it will be necessary to add all those files required for each case + the required registry entries.

 

And after all this hard work, IMHO we will end up with a boot.wim file very similar (in features and size) to the versions that Make_WinPE is already capable to build using as source a reduced version of the Winre.wim file + added files + respective registry entries (IAW the selected version).

 

alacran


  • antonino61 likes this

#198 ericgl

ericgl

    Frequent Member

  • Expert
  • 338 posts
  •  
    Israel

Posted A week ago

alacran,

 

Yes, you are right.

At least some of those CAB files (+ corresponding lang for each) must be integrated into the WIM file.

Most are necessary anyway.

 

As to the final size, with WinXShell or Explorer - I also expect roughly the same size as with WinPE.

Not sure what the differences are, if any. I haven't scrutinized the validationOS.WIM file.

 

Been busy lately dealing with a virus infection affecting many devices at my work place.

When I have some time in the following days, I will run a comparison between the two...or maybe someone here will beat me to it.


  • antonino61 likes this

#199 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1483 posts
  •  
    Italy

Posted A week ago

well if what alacrán says is the case, and if winxshell is what I have seen it is, I am dropping out of this. I am prepared, however, to use the cab files to any avail in install.wim files or vhd's, definitely not in boot.wim.







Also tagged with one or more of these keywords: winpe, wimlib, winntsetup, wim

2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users