Quote from SteveSi on 2024-05-12, 9:33 AM

v1.A3 2024-05-12 - bugfix - if boot to agFM and Partition 1 has a XML or INI file in the root due to a .imgPTN file being swapped it, agFM permanently altered some of those files. This permanently changes the imgPTN image file contents. Now it only cleans these files if Partition 1 contains E2B files.

 

When E2B (legacy) or agFM (legacy or UEFI) first boots, it cleans out the contents of various .xml files and .ini in the root of Partition 1. This is done because immediately after booting to agFM, the user could then run Ventoy and then a Windows ISO which may use the xml file left in the root of Partition 1 (and Ventoy does not clean the XML files).

This is because, E2B and agFM will create these in some circumstances so that they are detected and used by Windows Install ISOs or WinPE ISOs. They are therefore cleaned (contain harmless contents or empty) so that if you run Windows Setup or WinPE with no xml/ini choice, the files will be ignored.

However, these Partition 1 files are cleaned even after the user has switched in a .imgPTN23 file containing it's own \autounattend.xml file!

e.g.

1. User selects .imgPTN23 Windows Install image (or WinPE image)
2. Partition 1 now contains user's Windows image
3. User boots AGAIN to agFM - agFM will wipe/clean the xml file in the root of partition 1
4. User boots AGAIN to Windows in Partition 1 - because the original xml file has been cleaned in step 3, the Windows Install is not automated. Also the .imgPTN23 file has been permanently altered.

The new version of agFM checks that Partition 1 contains E2B before cleaning the xml/ini files.

Please download and update to this latest version by running "\e2b\Update agFM\Download and update agFM_v2.cmd" from Partition 2 of your E2B USB drive.