New way to make a multiboot device with no third party tools

I've posted one or two previous attempts at making a bootable disk to allow for the installation of multiple versions of Windows. I've come up with a new approach that I think is way better than previous attempts.

This solution consists of a set of 3 batch files and requires no third-party tools. Only the Windows ADK and Windows PE add-on are needed.

In my case, I have a thumbdrive with several different version of Windows 10, the original Windows 11 as well as 22H2, a Macrium Reflect recovery disk, a Windows Recovery disk, and a Veritas System Recovery boot disk.

Simply grab the ZIP file and review the Readme.txt for instructions.

Superb method and delivery.
Only thing I could possibly think to add would be links for the ADK and PE, in the readme.


I was very near the bottom of the readme and I thought... yeah, but how to "reset" the USB stick.
Sure enough, that's covered too.

Thanks for the feedback, much appreciated.

You are right of course, I should update that to provide more details on each file.

The startnet.cmd is a file that Windows PE runs automatically. By default, it contains only a single line that runs "wpeinit". However, I make use of that file to do the main job of reconfiguring the disk.

So, here is the workflow...

Run the batch file called Create_Disk.bat". That file will create the bootable disk and deploy Windows PE to it. It also modifies Windows PE by injecting a replacement "startnet.cmd" file into it. When that batch file is done, the user copies any ISO images that they may want to boot into the "ISO Images" folder on the disk.

The next step is to boot the disk. When booting from the disk, it is Windows PE that is being run (just as would happen when booting from Windows installation media). However, because we replaced the startnet.cmd file, Windows PE starts to run our version of that file. The job of that modified startnet.cmd file is to display a list of available ISO images to the user. The user selects a file and the startnet.cmd then performs a backup of the current configuration and then turns the disk into a bootdisk for the selected image.

If you now reboot the disk again, it will boot the selected image.

Finally, to return the disk to the state it was in before you selected an image from the disk, you would simply run the Restore_Disk.bat file.

The key to this was when I realized that Windows PE loads entirely into memory using a RAMdisk. Since it is running entirely out of a RAMdisk, I'm free to re-write the contents of the disk even while WinPE is running.

I simply thought that it was a fun little exercise to see what could be done without any third-party tools.

Might it be possible for the startnet.cmd file to not only boot the computer but then to run the Restore_Disk.bat file automatically after booting is completed?
That would make this impressive USB fully automatic in use. The only maintenance required would be replacing ISOs when updated ones are available.

All the best,
Denis

Next up ofc... will be the GUI.

Something like RUFUS maybe.

Run the program , point it to the USB, then ask if you want to update the ISOs or just add ISOs, then click "Create".
If you want to update the ISO(s), you will just point it at the newer ISO.
It will then delete the older one and add the newer one, you just pointed it at.
You will probably have to pad each ISO added so there's room for the updated ISO, if it happens to be larger.
Ofc it will auto download the latest ADK and PE .

And then like @Try3 said... after you boot from it and pick the ISO, it will auto-reset for the next time. :)




I know... it's a lot of work, But don't worry. Ten years from now you'll be wasting away the days in Margaritaville, living off the proceeds of the worlds greatest bootable media creation tool. You'll need a catchy name for it. Something like...

Boot-o-matic or Wonderboot or Easy-Boot... etc.

And a logo ofc...









Get @badrobot or @kado897 to do the logo. :)

Denis, I was thinking about but not sure how I would implement that. After all, the end result is that you have a disk that runs whatever image you selected. It runs 100% unmodified so as not to interfere in any way whatsoever with that image.

But, you can easily recover the disk back to its previous state even while booted from the disk itself.

As an example, suppose you have chosen to boot a Windows 11 installation disk. Once you get to the first static screen (where Windows is asking what language, keyboard, etc. to use), press SHIFT + F10 to open a command prompt and run the Restore-Disk.bat file.

As before, Windows setup loads entirely in a RAMdisk (not the files that it copied to HDD, but the entirety of the executable code) so that allows one to rewrite the disk even while Windows setup is running.

Ghot said:

Next up ofc... will be the GUI.

Something like RUFUS maybe.

Run the program , point it to the USB, then ask if you want to update the ISOs or just add ISOs, then click "Create".
Ofc it will auto download the latest ADK and PE .

And then like @Try3 said... after you boot from it and pick the ISO, it will auto-reset for the next time. :)

Click to expand...

LOL. I'm working on it. I already have the foundation working and I know exactly how to proceed. I'm only struggling with how to revert the disk back to the original state because I don't want to interfere with the native code of the Windows / Win PE / Win RE boot media.