E2B v1.88m Beta now available

I hope to release v1.88m as 1.88 Full Release version in a few days.
Please try it and let me know if you find any problems.

Changes from 1.87 are:

• Add Server 2012 R2 Std Eval Product Key file
• Update of Wincontig
• Update SDI executables
• Can now use .isofira or .isofira01 for Strelec WinPE ISOs
• MAKE_THIS_DRIVE_CONTIGUOUS.cmd now only works on the USB root (\) folder and all folders under \_ISO. Any user folders under the root (e.g. disk backups, applications, etc.) will not be made contiguous when the script is run.
• MAKE_E2B_USB_DRIVE.cmd can now be run from your E2B USB drive to make a new E2B drive.
• Later version of grub4dos 0.4.6a
• New jpeg-based default purple background for 2017
• Some changes to QRUN.g4b
• Spanish language updated and a few other language files improved
• Pi_pixel_x86_Persistent.mnu sample mnu file added for PIXEL iso, 
• Gandalf sample .mnu files added, 
• Boot_Recovery_WIM.mnu sample menu added (boot from any systems winre.wim)
• Fix for case where grub4dos 0.4.5c tries to load jpg as wallpaper (jpg not supported by 0.4.5c),

Download is available from the Alternate Download Areas.

Read more: http://www.easy2boot.com/download/e2b-version-history/

How to fix 'BSOD: STOP 0x000000A5 - not fully ACPI compliant' issues

If you are trying to boot to a Windows payload that is based on BartPE, Windows XP, 2003 or Vista, you may occasionally see this BSOD screen when booting to these types of payloads on some systems:

ACPI  0x000000A5 BSOD!

Often the simple fix is to press the F7 key repeatedly just as it starts to boot to PE. This F7 trick worked a treat when I tried to boot to PCUnlocker and Active Password Changer (via MediCat and a large .imgPTN file) on my Lenovo IdeaPad 300 notebook!

In many cases, you will see a text message to press F6 - this is your cue to go crazy on the F7 key!

Gotcha!
Before you do this however, you need to check the BIOS settings to see if there is any 'special' setting for the Fn function keys if you have a notebook. For instance, on my Lenovo IdeaPad 300, there is a 'HotKey Mode' in the Configuration page of the BIOS Settings menu. If this setting is Enabled (which is the default!), then you have to press Fn+F7 in order for the keyboard to generate the F7 scan code.

Other incantations to try
If no end of hammering the F7 (or Fn+F7) key seems to work for you, here are some other things to try which has apparently worked for other people:

• Check the BIOS settings, set USB to USB 2.0.
• Set all BIOS OS compatible settings to Legacy and XP/Win7 and not Win8/10 or UEFI. 
• Reset the BIOS settings to default and then try the above BIOS settings.  
• If you have an LPT option in the BIOS for a parallel printer port, try it set to LPT=Enabled as well as ACPI & PnP=Enabled and APM=Disabled.
• Try disabling ACPI in the BIOS.
• Try changing any CPU options in the BIOS (Safe Execution, VxD, etc.).
• You can also try an older version of the BIOS (newer versions may have been made compatible for Win8/10 only).
• If you have ever added extra RAM to the system, restore the memory to it's original configuration and size (and test the memory with a memory test program - the problem may be due to bad or mismatched memory!).

P.S. MediCat can be used on E2B if you convert it to a FAT32 .imgPTN file. It does contain illegal copies of some software though, so make sure you hold licences for any software it contains!

E2B 1.88l (with bugfix for previous 1.88 versions)

Flaming Floe has reported a problem when installing Win7 from an ISO with the latest v1.88k version. The AutoUnattend.xml file is not correctly cleared and so appears corrupt when Windows Setup loads it. This bug will probably affect most Windows Install ISO runs, but not all systems will show the symptoms and some will appear to work (and others will give an Unattend error).

After investigation, is seems that there is a bug in the new 2016-12-24 version of grub4dos (\grldr) that is used in v1.88k.

E2B v1.88l now uses a previous version of grub4dos (2016-12-23) which I think is OK.

I have reported the bug here.

Tips for making files contiguous on your E2B drive

Unless your E2B USB drive has become almost full at one stage in it's life after formatting it, the \MAKE_THIS_DRIVE_CONTIGUOUS.cmd script should run WinContig fairly quickly and without any problems. Obviously, having a fast USB 3.0 E2B drive helps though!

Here are a few tips:

1. Never download from the internet directly onto your E2B USB drive. This can cause the file to be heavily fragmented (even if you have lots of contiguous free space on it). You will find it best to always download files onto one of your internal drives first and then copy the file to your E2B USB drive. That way you also have a backup too!
2. Do not use 'special' fast-copy programs like robocopy or TeraCopy, etc. to copy files to your E2B USB drive. These often open multiple threads which results in fragmented files. This just means WinContig will then have to defragment them on the USB drive and so it just takes much longer overall!
3. Only start one copy session at a time. You can select multiple files and then drag-and-drop them onto the E2B drive, but don't start another copy session until the first one has finished. Not only can this cause file fragmentation, but it often takes longer too when copying to a USB drive.
4. You can only defragment a file if there is enough free space on the USB drive to hold a second copy of it. A 6GB file will require at least 6GB of free space (in a single chunk).
5. If your E2B USB drive has become nearly full at one stage and WinContig is not able to defragment a large file even though there is enough free space for the defragmented file, try using Defraggler - Action - Advanced - Defrag Freespace. This will consolidate the free clusters into one nice run. However, you should first delete any large fragmented files before you run it. This action can also fragment some files that were previously unfragmented, so the next run of WinContig will need to defragment them again. Then try adding your large file(s) again and finally run WinContig again. Defraggler will also show you a nice map of the used clusters and fragmented files (Analyze). You can also right-click on any single file in Explorer and use the Defraggler option to 'Defragment' it.
6. If using an 8GB NTFS E2B drive, it may not be able to hold a contiguous 4GB+ file. This is because the directory table ($MFT) will be at the 3GB position on the drive and so a 4GB+ file may have to be split if other files are also present. See here for more details and a way to work around this issue (or you could just buy a bigger USB drive!).
7. Finally, don't buy USB 2.0 drives. A USB 3.0/3.1 drive should always be faster, even on a 2.0 USB port and they are backwards compatible. I highly recommend the SanDisk Extreme USB 3.0 range.

If you have any other tips, leave a comment below.

P.S. As chi zhang says in the comments below, if you have a nearly full USB drive which is quite slow, it is often faster to just remake the USB drive again - then all the files will be contiguous because the drive will be reformatted. See here for more details.

Which is best, the SanDisk Extreme Pro or the cheaper SanDisk Extreme (you may be surprised!)?

Hurray! My new SanDisk Extreme Pro USB 3.0 128GB flash drive just came this morning.

Extreme Pro 128GB $70

Extreme 128GB $60

I have now run a few tests on it and compared it directly with the SanDisk Extreme USB 3.0 64GB flash drive.

I tested the Pro using Crystal DiskMark and then filled to entire drive with junk data and then repeated the test. This ensured that the flash controller had to perform a read-erase-write cycle on every write when running any further tests. However, there was no difference between benchmarks after I had filled it with junk data and then re-formatted it. This indicates that the USB controller always does a read-erase-write cycle on every write (so not an SSD controller).

The Crystal DiskMark results are shown below:

Find and boot to a Windows recovery.wim file (e.g. winre.wim)

Alex had a problem...

Often a Windows system cannot boot (not even to the recovery mode), but the recovery partition on that system will contain the correct WinRE.wim file that can be used to repair that OS.

He wanted to be able to boot to Easy2Boot and then boot to the WinRE.wim recovery file that was on the internal hard disk. That way, he could be sure he was using the correct version of the recovery .wim file for that system. Also, his E2B drive did not need to contain all of the possible Windows install ISO versions that there are in the world!

E2B can directly boot to an NT6 .wim file; you just need to specify the full path of the .wim file.

The problem is that different Windows systems keep the .wim file in different folders.

To further compound the issue, on his Windows 7 systems, the directory name often varied on different systems, e.g.

/Recovery/398cea27-6312-11e6-a670-10604b8d82a9/WinRe.wim

You need to be an experienced techie to make an E2B USB drive, don't you?

Watch this video by young Marcus for your answer (and give him a 'like' too)!

Add the recent Gandalf PE builds to E2B

The latest Gandalf PE builds from WindowsMatters.com are (at the time of writing):

Gandalf’s Win10PE x64 Redstone build 14393 version 11-10-2016

Gandalf’s Win10PE x86 Redstone build 14393 version 11-07-2016

Using a partition image (UEFI+MBR)

You can add these to your E2B drive is to convert each ISO to a .imgPTN file using the MPI_FAT32 shortcut provided by the MPI Tool Kit. It should then MBR or UEFI-boot.

For the x64 ISO you will need to increase the suggested size to 5100MB.

For the x86 ISO you will need to increase the suggested size to 4300MB.

Tips: If you want as small a .imgPTN file as possible, extract the contents of the ISO to an empty folder on your desktop and then drag-and-drop the folder onto the MPI_FAT32 shortcut.
Use a file extension of .imgPTNauto so that it goes directly to the CSM menu and also add a timeout 3 line to the \menu.lst file inside the image.

Direct MBR-boot from ISOs (MBR only)

E2B v1.90 and later supports direct booting of WinBuilder-based ISOs.

1. Ensure the .ISO file has no spaces in the file name

2. Keep the file extension as .ISO (do not use any other extension)

3. (optional) If you want to suppress the QRUN suggestion prompt, ensure the filename ends with the letter q or Q - e.g. Gandalfx64_q.iso.

Animated Flags for E2B available

I have uploaded an Animated_Flags.zip file to the Alternate Downloads - Other files folders.

UK wavy flag at top-right

Add Raspberry Raspbian\Pi Pixel x86 with persistence to E2B

The PIXEL ISO (Debian+PIXEL for Intel x86 CPUs) will boot if you copy the ISO to your E2B drive. It is designed to run on old, low-spec systems and be easy to use.

However, to be able to use the persistence option, you need to create a pixel-rw ext4 file and then create a persistence.conf file within it.

Here is the .mnu file for it.

E2B v1.88h/i available

Previously the \MAKE_E2B_USB_DRIVE (run as admin).cmd file was deleted from the E2B USB drive when a new one was made, in order to prevent the user from formatting his/her E2B drive.

I have now modified the script so that it checks for the case where the source drive has also been selected by the user as the target drive.

This means that if you or a friend wants a copy of your E2B USB drive, you can simply run the \MAKE_E2B_USB_DRIVE (run as admin).cmd file from your E2B drive and make an identical copy (complete with all payload files) onto another USB drive.

You will also need to copy any of your own user folders in the root of the source E2B drive to the target drive afterwards. For instance \MyFolder would not be copied to the target drive, only the \_ISO folder is copied.

Check the Alternate Download Areas for the new version.

Note: v1.88h had a bug in MAKE_E2B_USB_DRIVE.cmd. Please use v1.88i.

If copying a E2B Removable Flash drive to a USB hard  drive , you should remove the NOHELPER variable from within the \_ISO\MyE2B.cfg file on the USB HDD or else Windows Install ISOs when used with an E2B WinHelper Flash drive will not work!

E2B v1.88g Beta available

Changes from 1.87 are:
Changes from previous Beta version 1.88e are in bold

• Add Server 2012 R2 Std Eval Product Key file
• Update of Wincontig
• Update SDI executables
• Can now use .isofira or .isofira01 for Strelec WinPE ISOs
• MAKE_THIS_DRIVE_CONTIGUOUS.cmd now only works on the USB root (\) folder and all folders under \_ISO. Any user folders under the root (e.g. disk backups, applications, etc.) will not be made contiguous when the script is run.
• Latest version of grub4dos 0.4.6a
• New jpeg-based default purple background for 2017 - should load faster.
• Some changes to QRUN.g4b and language files.
• New version of SWITCH_E2B.exe 1.0.13 (small bugfix)
• Improved Spanish language files (thanks DW!)

The v1.88g Beta Download is available from the Alternate Download Areas.

SanDisk Extreme PRO CZ88 128GB USB 3.0 for $71 from Amazon.com (USA)

 I have just ordered one of these for $71 from here as the price has just been reduced (£67 in the UK).

SanDisk Extreme Pro 128GB

I have not tested one yet, but I am hoping it will prove to be slightly faster than the SanDisk Extreme USB 3.0 flash drive ($58) which I highly recommend for normal E2B use.

SanDisk Extreme 128GB

See also 'Beware of this (fast) USB 3.0 drive!'

E2B v1.88e Beta is now available

Changes from 1.87 are:

• Add Server 2012 R2 Std Eval Product Key file
• Update of Wincontig
• Update SDI executables
• Can now use .isofira or .isofira01 for Strelec WinPE ISOs
• MAKE_THIS_DRIVE_CONTIGUOUS.cmd now only works on the USB root (\) folder and all folders under \_ISO. Any user folders under the root (e.g. disk backups, applications, etc.) will not be made contiguous when the script is run.
• Latest version of grub4dos 0.4.6a
• New jpeg-based default purple background for 2017 (see screenshot below). 
• Some changes to QRUN.g4b and language files.

Download is available from the Alternate Download Areas.

Please update your E2B drives and let me know if you spot a problem or have a comment. This is considered a 'release candidate' for 1.88.

Foolish IT - 20% off sale now on!

The guys at Foolish IT have a 20% sale on all their products at the moment (if you are quick).

For IT Technicians look at their d7ii software.

• Provides quick automation with profile switching and execution for different repair scenarios
• Keep work logs automatically, or quickly build a custom work report with logged actions and templates
• Extremely customizable configurations enable personalization of tech workflow to your preferences
• Provides techs with a consistent procedure, ensuring quality performance increases
• New techs get ‘on the job training’ to your guidelines, while handling 80-90% of the bench work like a seasoned pro!
• Bottom Line:  Increase technician productivity and efficiency, save time and dramatically increase revenue!

Their latest video about the d7ii Support Online tool is here and they have a channel on YouTube here too.

For their crypto-prevention malware solution (they were the original pioneers of the honey-pot method) check out their CryptoPrevent product (there is a free version too!).

They also have some other free software which you can download here.

E2B v1.88d Beta available

Marco has kindly made some changes to WinContig which allows me to now make the MAKE_THIS_DRIVE_CONTIGUOUS.cmd script just operate on files in the root of the drive and then it runs on files under the \_ISO folder (so WinContig runs twice).

This means that WinContig does not attempt to make any files in the user's own folders contiguous.

The E2B 1.88d Beta is available from the Alternate Download Areas.

Note: WinContig.exe is a Beta version.

P.S. If you are wondering about v1.88c, it only lasted a few minutes, I decided it was better to do it this way!

Tip: If you only want to make files in the root contiguous, or files under \_ISO contiguous, you can simply copy one of the .cmd scripts from the \_ISO\docs\WINCONTIG folder to the root of your E2B drive.

E2B 1.88b Beta available

Morozko37 has reported that the Strelec WinPE ISOs should work with .isofira or .isofira01 file extensions, but don't (it does not load the ISO as a virtual CD).

This seems to be due to some missing lines in the QRUN.g4b code.

The additional lines have been added in v1.88b and so you can now use the file extension of .isofira01 with Strelec or other similar WinPE ISO builds that include the firadisk driver.

E2B v.1.88a Beta available

E2B v1.88a Beta changes:

• Add Server 2012 R2 Std Eval Product Key file
• Add \MAKE_ISO_FOLDER_CONTIGUOUS.cmd (works on \_ISO and below only)
• Update to Wincontig v2.1.0.0
• Update SDI executables

The 90-day evaluation Server 2012 R2 Standard installation-only Product Key has been added to the \_ISO\WINDOWS\SVR2012 folder.

If you have added your own portable applications, etc, to the E2B drive, when you run MAKE_THIS_DRIVE_CONTIGUOUS.cmd it will make all files on the E2B drive contiguous including all of your own files. I have now added \MAKE_ISO_FOLDER_CONTIGUOUS.cmd which will only make files below the \_ISO folder contiguous. 

This means that if you have persistent files (casper-rw, ubuntu-rw, etc.) in the root of the E2B USB drive, you will also need to make these contiguous. To do this either:

1. Move the persistent files from the root folder to the same folder as it's payload+.mnu file and then modify each .mnu file, e.g.

was:

set PF=/ubuntu-rw

change to:

set PF=$HOME$/ubuntu-rw

Now you can use \MAKE_ISO_FOLDER_CONTIGUOUS.cmd because all the E2B payload files will be below \_ISO.

OR

2. Run \_ISO\docs\WINCONTIG\WinContig.exe and manually select the file(s) you want to make contiguous.

OR

3. Run \MAKE_THIS_DRIVE_CONTIGUOUS.cmd as before.

Merry Christmas!

Steve

Add the SystemRescueCD + persistence (MBR and UEFI) to E2B

The SystemRescueCD contains several useful features:

Description: 

SystemRescueCd is a Linux system rescue disk available as a bootable CD-ROM or USB stick for administrating or repairing your system and data after a crash. It aims to provide an easy way to carry out admin tasks on your computer, such as creating and editing the hard disk partitions. 

It comes with a lot of linux software such as system tools (parted, partimage, fstools, ...) and basic tools (editors, midnight commander, network tools). It can be used for both Linux and windows computers, and on desktops as well as servers. This rescue system requires no installation as it can be booted from a CD/DVD drive or USB stick, but it can be installed on the hard disk if you wish. The kernel supports all important file systems (ext2/ext3/ext4, reiserfs, btrfs, xfs, jfs, vfat, ntfs), as well as network filesystems (samba and nfs).

It can be used with E2B for MBR-booting just by adding the ISO file (no persistence, no danger of the .iso file getting infected or corrupted).

The current (2019) version is version 6 and is based on Arch Linux (see end of article for details)...

27 new E2B wallpapers by 'DW' available

'DW' has provided a selection of 27 different E2B background bitmaps which have a semi-transparent grey panel overlaid onto them.

The DW_themes.zip file (18MB) can be found in the Alternate Download Area - Themes folders.

Copy whatever .bmp file you fancy to your E2B drive and also the Example_MyE2B.cfg file and then load the .cfg file into the E2B_Editor.exe and save the file as \_ISO\MyE2B.cfg.

Once you have it working, you can compress the .bmp file if you wish to save space. E2B (grub4dos) understands .gz format and LZMA format (see \_ISO\docs\E2B_Utilities\LZMA folder).

cloud3.bmp

Add a full installation of Solus to E2B

Max wanted to have a full persistent installation of Solus on his E2B drive.

You can do a full installation of many linux OS's to an empty .imgPTN file following this method.
The same method is also described here for Manjaro linux.

For Solus, after I switched in the new partition images (solus.imgPTN and a 10GB solus file with no extension), I just choose to install to /  on /dev/sda3 and format it as ext4 (no swap partition). I used a 10GB solus file which left 6GB free after installing Solus.

However, when using the Solus 1.2.1 ISO to install with, the Solus installer does not offer the choice of the /dev/sda3 partition to install the grub2 boot loader. It is either \dev\sda  (the E2B USB MBR!) or nothing.

Here is how to get around this...

New RansomWare software (Cybereason RansomFree) - but there is a catch which you may not like!

This new free Cybereason RansomFree software detects ransomware using the 'honeypot' technique.

It seems to create new folders that begin with { or ~{ and other strange characters, and then fills those folders with various  'tempting' .doc,  .txt, .rtf, .xls etc. files. It then monitors them for changes and will allow you to kill any task that attempts to makes any changes to any those files.

A nice touch (or weakness?) is that the honeypot files that it creates are mostly hidden from the normal user when using Windows Explorer to view your folders.

The honeypot theory assumes that any ransomware will scan the drive and find these files before it finds your important files and then the RansomFree software will be able to warn you before too much harm is done. It did not seem to place any honeypot files on any other volume in my system however, so it seems to be only monitoring the C: drive.

See YouTube video here.

It has been tested and reviewed by Bleeping Computers also.

But here's the catch...

Add the NirLauncher utility to your E2B USB drive to launch portable NirSoft utilities + others

NirSoft make lots of very useful Windows utilities, most of which are portable.

Use the NirSoft NirLauncher to quickly select a suitable NirSoft utility.

The NirLauncher utility allows you to run any of the 200+ portable utilities from a USB drive.

New YouTube video on how to make an Unattend.xml file

E2B contains a few example Unattend.xml files which can be used with unmodified Windows ISOs and a USB Flash drive to perform a completely hands-free automated Windows install.

The video explains how to prepare your own XML file quickly with your own settings using WAFG and XMLtoE2B.

Yesterday I built an Amazon Echo 'Skill' for E2B

I was asked by my family what I wanted for Christmas recently. As I was considering buying an Amazon Echo for myself, I suggested that I could order one for them to give to me.

It arrived a few days ago and like a naughty child, I opened my XMas present early and I have since been talking to 'Alexa' - with varying degrees of success (and frustration)!

I saw a video on YouTube about how to create a 'Skill' for the Amazon Echo (equivalent of a mobile phone app) and so yesterday, I decided to have a go.

I won't describe how I did it in detail, because there are many videos and other tutorials around which tell you how to do it.

I decided to try a simple Skill for Easy2Boot: e.g.

"Alexa, ask Easy2Boot Helper how to add ubuntu"

Here is how I got on...

ChrisR WinBuilder Win10PESE 2016-12-08 available

ChrisR has been supplying WinBuilder downloads for WinPE7/8/10 for some time now.

You can use WinBuilder to make a 32-bit or 64-bit WinPE ISO complete with many tools and even add your own utilities too. Most have WoW64 support in the x64 versions so you can run 32-bit apps under 64-bit WinPE.

The WinPE 10 WinBuilder version can be downloaded from here.

RMPrepUSB Tutorial #100 shows how to use WinBuilder and can be found here.

You can build a dual-boot USB drive which will UEFI-boot using either 32-bit or 64-bit UEFI (Secure Boot and MBR) systems by following the RMPrepUSB Tutorial #127 here. Note that some UEFI-systems may not MBR-boot from such a USB drive however - they will always UEFI-boot!

If you want to boot WinBuilder-based ISOs from E2B, you will need to read this Easy2Boot page. The easiest way to boot numerous WinBuilder-based payloads is to convert each one to a .imgPTN file for both UEFI and MBR booting, however you can MBR-boot directly from each ISO if you keep the file extension as .ISO and don't use spaces in the filename (E2B v1.92+). If you see a Yellow Triangle! on the Desktop, then it didn't work correctly! Read my previous blog on how to add multiple different WinBuilder ISOs to E2B.

E2B v.1.87 is now released

Changes from v1.86 are:

• Fix typo in SDI_CHOCO which caused pause with scrolllock.exe and capslock.exe error messages. 
• Improve linux fmt.sh scripts to install grub4dos to PBR and make partition active using parted. 
• Latest grub4dos 0.4.6a. 
• Snappy updated to R513. 
• Persistent sample .mnu files added for LibreELEC and Pentoo. 
• Win10 support added to PassPass (thanks to Ner0). 
• Improved Restore File check in PPass.g4b to prevent restoring wrong file+improve search speed.
• Other small tweaks

Download page

YouTube video on PassPass for E2B

YouTube Video on the E2B_Editor now available

See http://www.easy2boot.com/configuring-e2b/e2b-editor/  (refresh the page if you don't see a video at the top of the page).

Tip: use the gear wheel speed control and set x2 if you find yourself falling asleep!

E2B v1.87e Beta available

1.87e Beta has a few more tweaks to PassPass to make it quicker when searching for Windows OS's.
I hope to release this version as 1.87 after a few days, so please report any issues if you find any.

PEPassPass for XP to Win10

PEPassPass is a Windows-executable version of PassPass written by boulcat.

If you can boot to the E2B menu (MBR-boot), then you can use the E2B PassPass version.

The 64-bit + 32-bit modified boulcat versions of PEPassPass.exe (updated by Ner0 for Win10) is now available from the Easy2Boot alternate download areas (Google drive and OneDrive).

You can add these PEPassPass files to your E2B drive (or add them inside a UEFI-bootable .imgPTN file if you want to UEFI-boot to WinPE).

You can boot from any Windows or WinPE OS on a USB drive or CD (64-bit or 32-bit OS) and run PEPassPass to patch a Windows OS so you can bypass the local user account password entry.

Under WinPE, I use SHIFT+F10 to open a command console and then run NotePad and use the File Open menu in NotePad to find and run the PEPassPass exe file using right-click.

PEPassPass is useful if your system cannot MBR boot to E2B and can only UEFI-boot.

Follow the reboot.pro discussion for more details on PEPassPass (note the first version by Ner0 had a bug).

How to directly boot to different grub4dos payloads from the Windows boot menu

I have added Tutorial 134 to the RMPrepUSB website which describes how you can add multiple grub4dos payloads to the Windows 7/8/10 boot menu.

This method is useful because the user does not see any intermediate grub4dos menu, only the bootmgr BCD menu is seen.

For instance, a Windows bootmgr menu can contain BCD entries for:

Windows 10
Memtest 86
Ubuntu Live ISO
Parted Magic ISO

When you select any of these menu options, it will immediately boot to that payload.

E2B v1.87d (PassPass improved)

I have improved the PassPass batch file a bit in v1.87d.
When you Restore the DLL file (after first backing it up), it will now check the first 512 bytes to make sure you are restoring the same file and same version.

Alternate Download Area

Add a Manjaro Live install image to E2B

The manjaro live cd ISO does not seem to support a live persistence volume (AFAIK).

However, we can add a full manjaro image (MBR boot only) to E2B so that we can boot to a fully installed OS which will be updatable and persistent just like a normal installation.

Here are the steps to add a full linux OS to an Easy2Boot USB drive.

E2B v1.87c Beta available with PassPass for XP up to Win10

Ner0 on reboot.pro has posted a way to patch Windows 10 in a similar manner to that used by Holmes.Sherlock's PassPass.

I have added some new code to the E2B version of PassPass (v1.7a) so that you can now patch Windows 10 to bypass the password entry. The new E2B version is in the Alternate Download Areas.

How to add secret, hidden menu entries to E2B

Paul wanted to prevent certain payloads from being listed in the E2B menu system so that the normal user would not be aware that they even existed.

He wanted a secret hotkey + password which would allow the hidden payloads to appear in the E2B menu system.

We can stop any file from being listed as a payload in E2B by using a .txt file and the iftitle test feature. For instance, we can test for the environment variable 'SECRET' and if it does not exist then the menu entry will not be shown...

iftitle [if exist SECRET] Windows 10 English International (32-bit)\n My Secret ISO

We can set the SECRET variable using a hotkey + password.

In the example below, if you type CTRL+F9 (in any menu) then a blank screen will appear with a password prompt.

You can then type the password SECRET  (in capital letters), and any hidden menu items will then magically appear in the E2B menus!

To make them disappear again, type CTRL+F9 again and press ENTER instead of entering the correct password or press F8 when in the Main menu to reload E2B. Or you could define a CTRL+F10 key to hide them all again more quickly (see below).

Here is how to set this up...

Pentoo ISO with persistence on E2B

The pentoo FAQ says you can use changes=/dev/sdXY kernel cheat code to specify the persistence volume. This is incorrect!
It seems that we must use aufs=/dev/sdXY for pentoo.
As pentoo is based on gentoo, we can use a similar .mnu file for persistence with pentoo.

The .mnu file is shown below:

Add LibreELEC Live to E2B (Kodi)

You can add OpenElec Live to E2B by following my previous blog here.

You can follow a similar procedure to add LibreELEC to E2B (and also have UEFI-booting) as follows:

Add CHKCPU to your E2B drive to display CPU Info

CHKCPU is available as a MD-DOS\FreeDOS compatible freeware program by Jan Steunebrink that will display details of your CPU.

I have created a FreeDOS image that will auto-run this utility and then run checkpci.exe to display the systems PCI IDs.

CHKCPU running under VBox

Over 1000 E2B USB drives are made every day!

If you use the MAKE_E2B_USB_DRIVE.cmd script to create an E2B USB drive, the script will display the latest released version of E2B, so that you can see if there is a newer version and download it.

The script finds out what the current version is, by downloading a file called LatestE2B.txt from the www.easy2boot.com website. The file contains the current latest version number and it's release date.

A nice side-effect of this is that, as the Easy2Boot websites statistics report the number of 'hits' on that file, I can see that in the last 30 days, the LatestE2B.txt file has had over 31,000 hits. So this means that the script, on average, is being run 1000 times a day - and that is not counting the people that use RMPrepUSB to make E2B drives!

Why not make an E2B drive for your friends as a Christmas present? You can design the menu background to personalise it and add some linux distros with persistence, Gandalf WinPE, Lakka + games, Kodi (Xbox Media Centre), Cub Linux (a version of Chrome), various antivirus payloads in case of emergencies, android x86 with persistence, Tails for safe browsing, a Windows10ToGO VHD file, etc. etc. Check out this blog's 'Tutorials' page for all these and many other possibilities.

E2B 1.87b Beta available

v1.87b changes from v1.86:

• Fix typo in SDI_CHOCO which caused scrolllock.exe and capslock.exe error messages. 
• Improve linux fmt.sh scripts to install grub4dos to PBR and make partition active using parted.

Download from the Alternate Download Areas as usual.

If you make your E2B USB drive under linux, I highly recommend you ensure that the E2B USB drive has two primary partitions. The second primary partition can be any size and does not need to be formatted. This is useful because some computer BIOSes will not correctly boot the E2B USB drive as a 'hard disk' without the second partition being present.

Note that you can prepare both an NTFS or FAT32 E2B USB under linux and make the files contiguous under linux using defragfs (FAT32) or udefrag (NTFS) - see the linux page here. However, to make .imgPTN files (for UEFI-booting and installing Windows from a USB HDD, etc.), you will still need a Windows system to run the MakePartImage.cmd script.

UEFI-boot to Porteus with persistence from E2B

I have added another section to my previous blog post on Porteus to show how you can UEFI-boot to Porteus with persistence.

Add the Norman Rescue and Antivirus ISO to E2B (with persistence)

The XUbuntu-based Norman Rescue Disk ISO file (English+German supported) can be downloaded and added to your E2B USB drive (you can supply any junk email address to get the download).

However, when it first boots from the ISO file, it will download over 170MB of updates and virus definitions.

MPI Tool Pack 0.070 available

I have added a new script file \e2b\RestoreE2B_32_64.cmd to this new version.

It uses 32-bit and 64-bit versions of MBRFix.exe. This means that you can boot to either a 32-bit or 64-bit version of WinPE and switch back the USB drive to the original E2B partitions. Previously, you had to use a 64-bit version of WinPE that included WoW64 support (e.g. ChrisR's WinBuilder builds) so that it could run RMPartUSB which is a 32-bit program.

e.g. Now you can...
1. Switch to .imgPTN version of WinPE
2. UEFI-boot to 64-bit WinPE
3. Run \e2b\RestoreE2B_32_64.cmd

and now access the files on your E2B volume (including WinNTSetup.exe and Windows ISOs, etc.).

It uses Diskpart to find the Physical Disk number from the drive letter and does not rely on WMI, VB script or powershell or WoW64 - see here for details.

P.S. I found some typos in E2B SDI_Choco files which caused a '\DRIVERS\scrolllock.exe not found' and '\DRIVERS\capslock.exe not found' prompt. This is now fixed in E2B v.1.87a Beta.

Restore the E2B partition under 64-bit WinPE

If you use .imgPTN partition image files to boot to WinPE, you sometimes may want to return the E2B USB drive partitions back to it's original 'E2B' state (without having to boot into CSM\MBR mode), so that you can access the files on the E2B partition whilst running WinPE.

E2B Grub2 Menu system Beta 5 available

UEFI_GRUB2_PTN2_Beta5.imgPTNLBAa23 is available from the Alternate Downloads Area - Other Files folder.

The main difference between this version and the previous version is that for UEFI-booting to grub2, it uses a 64-bit shim for Secure Booting.

Making files contiguous on an NTFS volume under linux

Recent versions of E2B contain a 32-bit version of the binary executable for 'UltraDefrag' for linux (udefrag).

This can be found in the \_ISO\docs\linux_utils folder.

You will need to use chmod to make it executable first. More details are here.

To run the 32-bit version of udefrag under Ubuntu 64-bit:

sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386
(change to _ISO/docs/linux_utils folder)
sudo chmod 777 *
sudo udefrag -om /dev/sdX1  (where sdX1 is your NTFS USB partition - e.g. /dev/sdb1)

I got the udefrag file from here (tools.zip). There is also a post here which may help.

I am afraid my linux skills are virtually non-existent, so if anyone would like to provide me with a compiled, 64-bit version of udefrag, I will add it to E2B for others to use.

Weird UEFI-boot behaviour from my Asus Z87A mainboard

I was trying to boot a UEFI grub2 payload yesterday when I discovered something odd.

I was using an IODD 2531 Hard disk enclosure fitted with an SSD. I had loaded the grub2 menu system .imgPTN file using Switch_E2B.exe so it had the grub2 .EFI boot files present.

I then connected the drive to my Lenovo IdeaPad 300 and pressed F12 to get the Boot Selection menu. A UEFI boot entry was then displayed, so I selected that option and it booted to the grub2 menu - no problem!

Next, I did the same thing but using my Asus Z87A PC. To my surprise, the BIOS refused to list the IODD 2531 as a UEFI-bootable drive! There was an MBR-bootable option for the USB drive, but there was no UEFI boot option listed. This was very strange because I had UEFI-booted in this way dozens of times before from the same PC in the same way.

When I examined the Master Boot Record using RMPrepUSB - Drive Info - 0, I found that I had these partitions:

ptn #1 : FAT32 with EFI boot files
ptn #2 : NTFS with payload files
ptn #3 : Type 0x83 ext3 partition
ptn #4 : (empty)

Now ptn #3 was not supposed to be there. It was only there because it was left over from a previous experiment and because the grub2 .imgPTN file was switched in, it left partitions 2 and 3 alone, so that both were still present.

So I deleted ptn #3 and tried it again in the Z87A PC. This time the BIOS listed a bootable UEFI option for the IODD 2531 and it could now UEFI-boot.

So it seems that the mere presence of the Type 0x83 ext3 partition prevents the Z87A firmware from detecting the USB drive as UEFI-bootable!

Weird!

Footnote:
It seems that most UEFI BIOSes do not like MBR partitions which are out of order.
If a non-zero partition type is present and the Start Sector value is lower then the previous partition table entry, then it regards the whole disk MBR as invalid.

So in the above case, the start sector of partition 3 was before the start sector of partition 2.
Changing the partition 3 type to 0x00 fixed the issue and linux could still access the ext partition.

PC Rescue ToolKit Live CD by Bertrand Goio

Rescue ToolKit by Bertrand Goio is Linux-based rescue and diagnostic - RTK-3.iso (password=live).

The author has now replaced this toolkit with the PC Rescue Tool (Italian keyboard by default).
Just add it to your E2B USB drive and check it out.
It also has 64-bit UEFI boot files and so should work if converted to a FAT32 .imgPTN file too.

Package List is here.

Add salix+persistence to E2B

Following from a request from kasep, here is how to boot salix with persistence from E2B.

Salix with Persistence (folder STEVE was created)

From various experiments, I could not get salix to recognise an ext3 persistence file when mapped to partition 3 of the E2B drive. It seems that salix specifically looks for a 'persistent' file in the root of a FAT32 or ext3 volume with a volume name of  'LIVE'.

So, we need to convert the .ISO file to a FAT32 .imgPTN file. Here is how I did it: