Make files contiguous
Some types of payload files need to be contiguous in order to work correctly (this applies to all types of E2B USB drives – Removable UFD or Fixed-disk). E2B will warn you if they are not contiguous when you try to boot from them, but they may still boot correctly.
- Linux ISOs, linux persistence files (e.g. \ubuntu-rw) and .imgPTN* files must be contiguous.
Most Windows Install and WinPE ISOs, .WIM and .VHD files do not need to be contiguous.
Download tip: NEVER download files directly from the internet straight onto your E2B USB drive. A downloaded file can be highly fragmented and this will cause your E2B drive to become fragmented also. Always download a file to your system disk first and then copy the file to your E2B USB drive.E2B can also boot some linux ISOs that it recognises by name, without needing them to be contiguous (via ISOBOOT). If an .ISO file is below 500MB (default limit) and is not contiguous, then E2B will try to copy the contents to a contiguous file (\_ISO\CONTIG.ISO) first so that it can be booted successfully. This can be quite slow – it is much faster if you just make the ISO contiguous!
After you copy a file onto a freshly-formatted partition, the file will usually be contiguous. However, as the partition becomes full and as files are deleted and replaced, when a file is copied on, it may be spread across 2 or more different areas of the partition and so will be fragmented.
To avoid any ‘not contiguous’ error messages from E2B or agFM, double-click on the:
file on the E2B USB drive to run WinContig and make all E2B files in \ and under \_ISO on the USB drive contiguous – OR – run RMPrepUSB – CTRL+F2 to run WinContig on the whole drive instead.
Note: Ventoy does not require files to be contiguous or the drive to be write-enabled.
Tip: You can copy the *.cmd files from \_ISO\docs\WINCONTIG to the root of the E2B USB drive if you wish. Then you can double-click on any one of them to run them.
- \MAKE_THIS_DRIVE_CONTIGUOUS.cmd (works on \_ISO and files in \ – i.e. runs WinContig twice)
Files that do not need to be contiguous
Windows Install ISOs, .VHDor .WIM files do not usually need to be contiguous (unless heavily fragmented), and you can just ignore the warning if WinContig cannot make them contiguous. Also, WinPE .ISO files do not normally need to be contiguous. Test them using E2B and simply press ENTER until they boot. If they boot successfully, you can give the filename a NCQ suffix (e.g. Win10PESE_x64ncq.iso) and this will suppress any E2B ‘not contiguous’ warnings (E2B v1.98+).
Problems making a large file contiguous (‘Defraggler’)
WinContig needs a large amount of contiguous free space which may not always be available once a drive has been filled (even if you then delete some files). There may be loads of free space on the drive, but the free area needs to be in a large, contiguous single block. You may be able to make an individual file contiguous by using Defraggler (Explorer – right-click on file).
Use Defraggler to consolidate all the free space on a drive
Defraggler can consolidate all the free space on a USB drive which is exactly what you need once the drive becomes fragmented (use Action – Advanced – defrag free space), but that action can make some contiguous files become non-contiguous, so run WinContig afterwards. If you have a slow USB 2.0 drive, it is often quicker to reformat the drive by re-installing E2B using the Windows GUI and then copy back all the payload files.