Common problems with payload files

XP Install description of Setup stages and errors here.

Always check the list of tested payload files for any special instructions here.

Always use a filename with no spaces and no special characters if you are having problems.

For some common problems with Windows installations, see here (links to useful TeraByte KnowledgeBase articles).
 

  • HELP! After booting to xxxx (e.g. a linux ISO), I can no longer boot from my laptop/PC! - This is not an uncommon experience! To fix it, disconnect the power cord (switching it off is NOT good enough!). If you have a laptop\notebook then also remove the large Lithium battery pack. Wait 30 seconds. Now re-connect the power (and the laptop battery). All should be well.
     
  • Windows cannot read the setting from the unattend answer file (Win8/10) - You need to specify a 5x5 Product Key. This is normally prompted for by Easy2Boot. Check the AutoUnattend.xml file on the USB Flash drive and compare it with the xml file and product key that was selected. Make sure the xml syntax is correct and balanced.
     
  • Windows cannot find the Microsoft Software License Terms (Win8/10) - The product key used was of the wrong type. e.g. for Win8.1 Enterprise 90-day Eval use 76FKW-8NR3K-QDH4P-3C87F-JHTTW, for Win10 Enterprise use VTNMT-2FMYP-QCY43-QR9VK-WTVCK. These keys should already be available in the 'list of keys' option provided by E2B.

  • No images are available - Win8 Product key that was used, was for a different SKU (e.g. Enterprise Product Key used with a non-Enterprise ISO) and the Install.wim did not contain that version. Use the correct Product Key.

  • Blank screen after Windows loads - If the Windows ISO boots and you see the MS logo but then the screen goes blank (but hard disk activity continues as shown by the HDD LED) AND it only happens on one particular model of system (or one version of BIOS), then this indicates a buggy BIOS. Check to see if there is a BIOS update available from the Manufacturer. Alternatively, rename the .ISO file to .ISOE0   (E followed by the number ZERO).

  • The product key entered does not match any of the Windows images available for installation. Enter a different product key. (Win8) You probably have an OEM system which came with a Windows 8 Product Key embedded in the BIOS. The Product Key in the BIOS does not match the version of Win8 you are trying to install (e.g. OEM vs Retail). Either use the original OEM Win8 ISO or specify the Windows 8 Product Key that you want to use in a E2B file (see Windows 8 section for instructions).

  • No graphics display from linux-based ISO - If a text-mode boot works but a graphics-mode boot does not, this is usually due to an incompatible graphics driver in the linux kernel. Try a different system or a Virtual Machine to check that it works OK on a more 'compatible' system.

  • One large ISO file is not working correctly - If you copied a large ISO file to the USB drive but it is not working as expected, then it may be corrupt. Check it's CRC32 hash value on the system hard drive against the CRC32 value of the file on the USB drive.
    Tips: hold down SHIFT+Ctrl keys when selecting the ISO in E2B to get it to report the CRC32 value before it runs the ISO. RMPrepUSB - Ctrl+C will report the MD5/CRC32/SHA1 value of a file).
    Note that E2B may alter some bytes in some ISO files (e.g. Windows Install ISOs and .isomacpup files) once the ISO has been run, so the CRC32 value of these files on the E2B drive may be different after booting from them with E2B.

  • Unable to see USB drives once booted from E2B to a Win XP/7 OS - go into BIOS and check USB XHCI setting - change from 'Smart Auto' or 'Enabled' to just 'Auto'. XP\Win7 do not have USB 3.0 drivers, so use USB 2.0 port or see here.

  • Unable to find a medium containing a live filesystem - Make sure the linux ISO is contiguous and use an extension of .iso not .isomem. Check for a .mnu file for your ISO (see \_ISO\docs\Sample mnu Files folder).

  • Cannot find squashfs - as above.

  • Some ISOs run almost instantly and others display a [32M/384M] style counter and take ages to run - Because the file is not contiguous, E2B is forced to load the whole ISO into memory (and it may not then boot correctly either!) - to fix, just run RMPrepUSB - Ctrl+F2 to run WinContig (or use the Make_Drive_Contiguous.cmd file in the root of the E2B drive) and make all files on the drive contiguous. If you have named the ISO file extension as .isomem then it will always load into memory and be slow to load!
    Note: making files contiguous is NOT the same as defragging the drive (which may actually fragment the files even more!).

  • Hirens/DLC boots to Mini Win7 but does not show all Desktop icons or work fully - use .isowinvH or .isomem file extension - some ISOs like Hirens Boot CD and DLC need to be extracted (in most cases the \HBCD or \DLC folder is needed in the root of the USB drive) - check this site for instructions - just make your own .mnu file with the correct grub4dos menu code - or - ask someone to make you a .mnu file! Alternatively, once in the Win7 Desktop, find the ISO file, right-click on it and select ImDisk from the options, choose 'CD-ROM' as the type and then mount the ISO. Now you can run \HBCD.cmd from the mounted ISO file. See the FAQ section for more help with Hirens.
    For Hirens 9.6 and earlier versions see Tutorial 116.
     XP\Win7 do not have USB 3.0 drivers, so use USB 2.0 port or see here.

  • DLC Hirens.isowinvH works for Mini XP, but Mini 7 does not display all Desktop icons - use .isomem OR .isoHW OR extract the \DLC1 folder from the iso and place in root of USB drive at \DLC1. Copy the \HBCD or \DLC or \DLC1 folder from the ISO file to the root of the USB drive. For best compatibility if using an E2B USB HDD drive, convert the ISO to a FAT32 .imgPTN file.
     XP\Win7 do not have USB 3.0 drivers, so use USB 2.0 port or see here.

  • Hirens Mini Win 7 reports a 'Julia.iso' error with 12.Hiren.s.Boot.CD.15.2.isowinv -  the extension should be .isowinvH not .isowinv. Also try the .isoHW or .isomem extension.
     XP\Win7 do not have USB 3.0 drivers, so use USB 2.0 port or see here.

  • Hirens Win7 HBCDMenu icon does not work (not populated) -  Use .isomem file extension OR .isowinvH. If that still does not work, use 7Zip to unpack the Hirens ISO to the root if the E2B drive.  XP\Win7 do not have USB 3.0 drivers, so use USB 2.0 port or see here.

  • Ophcrack - no tables found - you have to extract the \tables folder from the ISO (or download them) - the \tables folder must be in the root of the USB drive.

  • ERD50/MSDaRT 5 for XP ISO crashes - rename the file extension to .isomemwinv or .isomemf01 or use the ERD5_DPMS.mnu if SATA/RADI system

  • BartPE XP ISO crashes - rename the file extension to .isomemwinv or try .isofira01

  • ERDCommander 2005/2007/MSDart 5.0  ISO crashes - rename the file extension to .isomemwinv or .isomemF01  or use the ERD5_DPMS.mnu if booting from a SATA/RAID system.

  • Hirens 15.1 ISO - XP does not show all Desktop icons and Program Launcher is empty - rename the .iso file to .isomem or .isowinvH or .isoHW

  • Hirens Linux menu entries do not fully load linux - Ensure all files are contiguous (RMPrepUSB - Ctrl+F2). 

  • Embedded XP Install ISO can't find source CD on 2nd boot - if you re-name the iso as an XP ISO and move it, it may work (e.g. \_ISO\Windows\XP\XPHOMESP2.ISO) - if not, extract the whole iso contents to the root of the USB drive and rename the ISO to xxxxx.isowinv and place it in \_ISO\MainMenu folder. Only the files in the root and the \i386 folder may be required, but test with all extracted files as a first attempt. See POS2009_ReadMe.txt in the docs folder for an example of an embedded XP install ISO. You can also try the XP Install using the WinPE method here.

  • Kaspersky ISO boots but I cannot get past accepting the licence page - try typing ALT+TAB and then press A - or  press 1 (don't use the number pad as it may not work).

  • Kaspersky 10.0 ISO runs and downloads the updates, but the next time I use it on another system, I have to download the updates all over again - Create an empty folder on the root of the Easy2Boot USB drive called \Kaspersky Rescue Disk 10.0 - before you next boot to KAV-rescue on a system, ensure that the Kaspersky Rescue Disk 10.0 folder on that system's internal hard disk is NOT present (otherwise updates will go onto the internal hard disk).