Use Ventoy to boot WinPE ISOs such as c't Emergency Windows 2021 ISO (aka 'ctNotWin', 'ctNotFall' etc.)

Easy2Boot and agFM can boot WinPE-based ISOs easily, however many of these ISOs require access to files on the 'DVD' drive once they have booted to WinPE.

Since these files are inside the ISO file on the USB drive, these extra utilities cannot be found by the miniWindows environment and you may find some Desktop and StartMenu items missing!

E2B and agFM can make this work however by using that fact that most WinPE's are built using WinBuilder which typically contain this extra startup code. When a WinPE made by WinBuilder boots, it looks for a volume containing a .ini file in the root (e.g. \WIN10PESE.ini) which specifies the path of an ISO file. WinPE will then find that ISO file and auto-mount it as a virtual DVD drive so that WinPE can now access the files within the ISO.

WIN10PESE.ini

[IsoInfo]
IsoName=/_ISO/MAINMENU/Win10XPE_x64.ISO

E2B and agFM will modify these .ini files before booting the ISO (that is one reason why a write-enabled USB drive is required). The ISO filename should not contain spaces because some versions of WinBuilder cannot cope with spaces in filenames.

However, this only works if the WinPE contains this special WinBuilder startup code which looks for the special WinBuilder .ini file.

E2B and agFM also modify the \AutoUnattend.xml file in the root of the E2B USB drive - this file is automatically run if the ISO is a Windows Install ISO (but it is not usually run by WinPE ISOs).

c't Emergency ISO

Unfortunately, some WinPE ISOs do not contain this special startup code (e.g. c't Emergency Windows 2021). There are a number of ways around this:

agFM v1.66 released

Changes from v1.65 are:

• F3 now also shows winre.wim Boot to Windows Recovery entries if a Recovery folder is present.
• F10 hotkey will reload agFM without rebooting
• Search hotkey is changed from Ctrl+Shift+F which did not work in MBR\Legacy mode to Ctrl+F
• New Ctrl-F search function searches current level and one folder down only. User can search for any extension or use a hotkey. e.g. Ctrl+F P will list all .imgPTN* files in current directory and level below current directory.
• F5 now uses grubfm built-in code (/boot/grubfm/f5.sh no longer used).
• Bugfix for dd command where -c exceeds 63555.
• Ability to use Ctrl+F as menu hotkey (but not all Ctrl+ letters can be used!).
• The menuentry command now supports --help_msg option which can display help text in a themed menu (but is buggy, so I recommend you don't use it in your menus!).
• The e2b.sh and map.sh files now use map -f to map as the first device when in efi mode.
• Add_Ventoy.cmd changed to work with latest e2b for Ventoy 1.0.29.zip download.
• Update_to_latest_Ventoy_version.cmd file will now automatically add 'Ventoy for Easy2Boot' to the USB drive. The current E2B version of 'Ventoy for E2B' will be downloaded from the E2B server.
• Latest grubfm build (2020-12-01).
• /e2b/loadfm file added. 
• /ventoy/Sample Ventoy config files folder added (contains sample files which user can add to ptn1). Copy to \ventoy folder on ptn1 will allow you to boot agFM or E2B from the Ventoy menu
• SAMPLE_slack theme fm.txt updated for Ctrl+F text display on menu.
• SAMPLE_slack theme fm.txt now supports timeout countdown so it can be used for startup menu with F1-F6 icons and timeout counter
• Improved SAMPLE_startup_menu.txt - now can have more than 10 entries and define a different icon and hotkey for each menu entry.

Now when a user runs Make_E2B.exe, they will be asked if they want to add agFM and Ventoy to partition 2. Both will be fetched from the E2B server. Currently Ventoy is the special 'Ventoy for Easy2Boot' v1.0.29 which is not blocked to run on an E2B USB drive.

agFM v1.66Beta12 available (and how to MBR-boot the grubfm.iso from grub2)

agFM Beta12

agFM Beta10 adds a new F10 hotkey function (new hidden feature).

If you press F10 in a grubfm menu, then it will completely reload grub2.

You may find this useful if you run an ISO or some other payload file and grubfm loses the gfxmenu system and just displays a black-and-white text menu. If you then press F10 then the whole agFM boot file will be reloaded thus saving you having to reboot. Since some servers can take 5 minutes to reboot, you might find this useful.

The actual code is compiled within agFM (in global.sh), but if you are interested, you can add a menuentry to your own menu system as shown below:

Latest agFM v1.66 Beta7 available (release candidate)

 Please test latest version 1.66 Beta7 as I hope to make it the new release version in a day or so.

See OneDrive - Latest Betas folder for the download.

Please don't just wait for it to be released before trying it. It is easy to test it by simply extracting the files to the 2nd partition. If you want to go back to the old v1.65 then simply click on \e2b\Update agFM\Download and update agFM_v2.cmd.

Changes from v1.65 are:

Latest agFM v1.66Beta5 available

 Todays version in 'Latest Betas' will automatically download and add 'Ventoy for Easy2boot' when you double-click the \e2b\Update agFM\Update_to_latest_Ventoy_version.cmd file.

The current version is Ventoy v1.0.29 but is slightly modified to run on E2B.

See the Ventoy page on the E2B site for details and a suggested ventoy.json file...

Ptn1: \ventoy\ventoy.json

{

        "control_uefi": [

        { "VTOY_DEFAULT_MENU_MODE": "1" },

        { "VTOY_FILT_DOT_UNDERSCORE_FILE": "0" },

        { "VTOY_DEFAULT_SEARCH_ROOT": "/_ISO" },

        { "VTOY_MENU_TIMEOUT": "5" },

        { "VTOY_DEFAULT_IMAGE": "/_ISO/LINUX/ubuntu-18.10-desktop-amd64.iso" }

    ],

"control_legacy": [

        { "VTOY_DEFAULT_MENU_MODE": "1" },

        { "VTOY_FILT_DOT_UNDERSCORE_FILE": "0" },

        { "VTOY_DEFAULT_SEARCH_ROOT": "/_ISO" },

        { "VTOY_MENU_TIMEOUT": "10" },

        { "VTOY_DEFAULT_IMAGE": "/_ISO/LINUX/linuxmint-20-cinnamon-64bit.iso" }

    ]

}

Black Friday is still on! 25% discount on Kon-Boot, cheap Samsung SSDs and more...

If you often need to gain access to a customers Windows account (local or online account) or MAC OS account but don't know the account password, then Kon-Boot is the quickest and simplest way to gain access (MBR or UEFI).

Today you can get 25% off KonBoot by using this link,

Kon-Boot can now work on larger USB drives as well as small USB Flash drives, so you can install Kon-Boot onto any USB drive and then add E2B to the same drive. More details here.

P.S. Black Friday Samsung 860 500GB SSD #ad on offer at Amazon for 47% off (over 60% off 2TB version!).  If your laptop does not have an SSD hard drive, this will be the best saving you've ever made as you won't have to buy a new laptop for another few years at least! Why not give them as Christmas present and help your family upgrade their own laptops over the Christmas holidays?

Hurry! 128GB SanDisk Extreme Pro (#ad) USB 3 Flash drive for only £30 !!! One of the fastest flash drives you can get - ideal for E2B!

Note: This is the superfast PRO version, not the slow, budget GO version (which is not recommended!).

Check out the SD card discounts too...

Ventoy for Easy2Boot v1.0.29

I have updated the test version of Ventoy v1.0.29 for E2B and also I added the core.img into the .zip file itself.

This now makes it easier to add Ventoy to an E2B USB drive.

Latest Betas are here as usual.

1. Update to latest agFM E2B UEFI File manager v1.66Beta4 (extract contents onto partition 2) (note that there was a bug in Beta3!)
2. Download the latest e2b_ventoy-1.0.29-windows.zip file
3. Drag-and-drop the new e2b_ventoy-1.0.29-windows.zip onto the Ptn2:\e2b\Update agFM\Add_Ventoy.cmd file

The new Add_Ventoy.cmd will automatically update/add Ventoy to partition 2 and add the correct core.img file.

I have also added and updated the compile instructions for Ventoy.

How to patch and recompile Ventoy

I do not intend to continually patch and recompile Ventoy every few days so that it can be added to E2B, however if you want to know how I made my own version, I have written up some notes here.

My knowledge of C is limited and I am not very experienced with Linux, so please correct me if any of the instructions are wrong or maybe inaccurate!

I have also slightly modified the wallpaper in my new version of Ventoy_1.0.29_windows.zip now to make it obvious that it is not the official Ventoy version - can you tell?

Ventoy 1.0.29 for E2B available

 I have recompiled Ventoy 1.0.29 so that it runs on E2B.

You can obtain the patched version from here.

Drag-and-drop the zip file onto the \e2b\Update e2b\Add_Ventoy.cmd file.

After installing it using that .cmd file, you will need to download the v1.0.29 patched version of core.img from here and overwrite the \ventoy\core.img file with this new version - otherwise MBR-booting will be blocked.

I have not changed its appearance, so please don't report any problems to the Ventoy forum unless you can reproduce the same issue on a genuine Ventoy USB drive!

The MBR version appears to say 'Unofficial Ventoy' but the UEFI version does not display that text message.

This version is temporary and for Beta testing only. I do not intend to maintain a forked version of Ventoy for E2B.

Latest Ventoy v1.0.28 will not work with E2B!

 LongPanda (the developer of Ventoy) has changed Ventoy so that it will only work on MBR-partitioned disks if that disk was prepared using the official Ventoy tools. The second partition must be exactly 65536  sectors long now.

Recently, I received some special error reports, which finally proved to be the cause of the non-standard Ventoy environment. Especially use Ventoy in a single partition environment.
Although Ventoy displays Unofficial's label information, users will not care and will still think it is a Ventoy problem. Ventoy has been an overall design from the beginning, and has not considered integration into other bootloader or partition environments. Ventoy's verification and subsequent development of new features will not consider this non-standard usage. Therefore, I decided to prohibit the use of Ventoy in a non-standard environment and no longer accept requests for deregulation. Of course, this is just the default behavior of Ventoy. Ventoy is still 100% open source. If you want to apply Ventoy in your own environment, you can fork a branch and modify the source code implementation.

 

This means that v1.0.28 (and all future versions?) will not run from an E2B drive.

If you would like to be able to continue to add Ventoy to E2B, please feel free to contact LongPanda and request that he changes his mind!

See here for more details of this recent change.

For now you need to use 1.0.27 (see here for details).

For the changes in Ventoy which check the partitions for validity - see the new code here (starting line 509).

If you wish, you can run the newer versions of Ventoy using MBR-booting only by using an older version of core.img, however UEFI-booting to Ventoy will still be blocked.

Footnote (2021): I have now recompiled Ventoy as 'Ventoy for Easy2Boot' with the restrictive code removed. Also, you can easily convert an E2B USB drive into an official Ventoy USB drive (original unmodified Ventoy) by making three different image files of 'official' Ventoy from the latest build of Ventoy and 'switching' one of them into Partition 2 (uses Ventoy grub2 boot code too).