SWITCH_E2B v1.0.4 available (compatible with FlashBoot)

It was reported to me that SWITCH_E2B did not work on E2B USB flash drives that had been formatted using FlashBoot, so I have now made version 1.0.3 available for those of you that use FlashBoot with E2B. If you use FlashBoot, you can update your E2B drives and your MPI installation ( the MPI .\csm\e2b folder) with the new version of SWITCH_E2B.exe.

Update: v1.0.3 only worked if the volume name was kept as 'FLASBOOT'.
v1.0.4 should now work with any volume name.

If you often find yourself needing to USB boot from older systems a lot (e.g. repair shop), you should check out FlashBoot!

E2B drives prepared using FlashBoot should boot on a wider variety of systems, especially older systems with early (buggy) USB BIOSes that try to boot USB drives as a floppy disk or USB ZIP drive instead of as a hard disk.

If a BIOS boots from a USB Flash drive as a floppy/ZIP drive instead of a hard disk, this causes grub4dos to fail to boot. If you use RMPrepUSB\RMPartUSB to format the USB drive, it adds a second small hidden partition and this often helps to avoid the 'boot as floppy' problem - but not always!

If you prepare your USB Flash drive with FlashBoot, you may find that it will boot on some of these older systems that would not boot from a 'normal' E2B drive.

However, there are some drawbacks to using a drive that has been formatted with FlashBoot:

1. You have to format the USB drive as FAT32 with FlashBoot (NTFS is not supported). So this limits your maximum file size to 4GB. FlashBoot is not limited to creating 32GB partitions however and will work with both large USB hard disks and removable flash drives.
2. You cannot reboot to the CSM Menu once you switch into any .imgPTN partition image. You can boot to the E2B menu, switch to a .imgPTN menu and then run the CSM Menu, however you cannot reboot to the CSM menu (a fresh boot) because the code in the MBR is specific to FlashBoot and it expects a partition to be present which contains FlashBoot boot code and not the 'normal' .imgPTN image partition that has been switched in.

FlashBoot is a commercial product (25 Euros), but you can try it for free for a limited period and see if it works on your 'difficult' old systems before you buy the full version.

P.S. You can also try out the Emergency Boot CD (EBCD) .ISO download too!

E2B v1.75 now released

v1.75 is also available on the two Alternate Download sites.

Google Drive download area

OneDrive download area

E2B v1.75BetaH available with Windows Server 2016 support + bugfixes

In E2B v1.75BetaH I have added a new \_ISO\WINDOWS\SVR2016 folder for the upcoming Server 2016 release. It uses the 'Win8 install' grub4dos batch file and so allows you to specify a Product Key or XML file in the same way as for Win8 ISOs.

Please test it out and feed back any comments (steve at easy2boot dot com), as I intend to make this the new v1.75 release version soon.

Trouble with Windows 10 Threshold 2 ISOs and E2B?

A few weeks ago I downloaded an MSDN Windows 10 Threshold 2 preview of Enterprise and found that when the blue console (LOADISO) window ran (booting from a Removable E2B USB drive and using the .ISO file), ImDisk did not mount the ISO as drive Y:. This was repeatable but only that ISO gave a problem.

I reported this issue to Olof (the author of ImDisk), but a few days later when I tried to reproduce the problem I found that it worked OK and could not reproduce the problem!

A few days ago, an E2B user reported to me that he had MSDN and Retail versions of the latest Win10 Threshold 2 released ISOs and had encountered the same problem with all the new ISOs (older ISOs worked OK) using E2B v1.74.

I suspected that perhaps a different version of WinPE was being used in his ISOs (maybe because they were MSDN versions?) and updated ImDisk on E2B (v.1.75BetaC).

However, the same user then reported that the ISOs were now magically working with E2B v1.74 when he retested them!  A clear case of Deja Vu!

If you find a similar issue, please comment on this blog or contact me. There is something weird going on, but I am not sure where?

MPI Tool Kit 0.056 available for Windows 10 Threshold 2 systems

0.056 is the same as 0.055 but has the new version of ImDisk.
If you are using Windows 10 Threshold 2, you will need to download this and run .\ImDisk\imdiskinst.exe to install the new version of ImDisk to make the MakePartImage scripts work again.

New ImDisk version for new Windows 10 release now available

Olof has released a new version of ImDisk.

I will update the MPI Tool Kit in a day or so. Meanwhile you can install the new ImDisk and then check that MPI works on the new 'Threshold 2' version of Windows 10.

MakePartImage problems with Windows 10?

If you are using Windows 10 and now suddenly find that you get an error when running MakePartImage (MPI) and cannot create .imgPTN files any more, it is probably because Windows Update has updated you to the latest version of Windows 10!

The original Win10 version is 10240, but the new (large) update called Threshold 2 is Version 1511 Build 10586. You can check your version by using the [Windows+R] key chord and run WinVer.exe.

You can update to the new version or download an ISO from here. Microsoft will soon enable the auto-update to Threshold 2 on all systems.

Olof is working on a new version of ImDisk to fix this issue and I will release a new version of the MPI Tool Kit when the new ImDisk becomes available.

Update: New ImDisk version for Win10 1511 from Olof here.

Easy2Boot v1.75 Beta B available

• .imgPTN files now supported in all \_ISO\WINDOWS\xxxx folders (except XP)
• new .isoBF file extension supported (permanently patches an ISO to remove the bootfix.bin file and so suppress the 'Press a key to boot from CD\DVD' message)
• new .vhdgrldr file extension supported (boots a vhd file which uses a grub4dos menu or PBR boot code)

For info on the two new file extensions, see this page.

The main change is that if you have converted a Windows Install ISO to a .imgPTN file, you can now add these to the \_ISO\WINDOWS\xxxx folders and they will be listed in the appropriate Windows sub-menu alongside any ISOs you may also have present. You do not need to have any Windows Install .ISO files present if you don't use them.

The only exception is that XP Install .imgPTN files are not supported and so should not be added to the \_ISO\WINDOWS\XP folder (they will not be listed in the Windows Install menu). If you have any XP Install .imgPTN files, you should add them to a 'normal' menu folder - e.g. \_ISO\MAINMENU or \_ISO\WIN.

You can use a .txt file for .imgPTN menu entries in these folder in the same way as you can for normal folders.

You can now place your .imgPTN Windows Install files in the \_ISO\WINDOWS folders as well as .ISO files

Add Win-UFO (Ultimate Forensic Outflow) to your toolkit

The Win-UFO download is a single .exe file which asks you which location to install to when you first run it. Actually it does NOT install anything to Windows, it merely extracts files to the designated location. There is a PDF manual file to download and which I suggest you study first before using Win-UFO and some YouTube videos.

 Win-UFO is now associated with CAINE.

E2B v1.74 released (fixes the firadisk.cmd copy bug with XP ISO installs)

It seems I made a typo in the grub4dos batch file \_ISO\e2b\grub\DPMS\DPMS2.g4b in E2B v1.73 which means that when you try to install from an XP ISO, you will get a 'cannot copy firadisk.cmd' error reported at the start of the file-copy phase in text-mode Setup and need to 'Skip' the file.
This is fixed in v1.74.
Thanks to watsupson for reporting it!

Windows Defender is deleting SWITCH_E2B.exe!

BEWARE: The latest definitions update for Windows Defender seems to think SWITCH_E2B.exe is a malicious file and promptly deletes it!
VirusTotal does not find any problems with it and, of course, it is not malicious!
You may find that this file has suddenly disappeared, now you know why!
Thanks to Steven L for pointing this out!

New Gandalf WinPE, XP SP3 install ISO and Dreams Boot CD 2015

This post covers:

• New Gandalf Windows 10 64-bit WinPE ISO
• Windows XP 'Gold 2016' install ISO
• Dreams Boot CD 2015 (DLCD) ISO

FYI - new Kaspersky Ransomware decryptor software

Kaspersky have recovered the full list of over 14,000 encryption keys used by the criminals responsible for CoinVault and Bitcryptor ransomware. They have now updated their decryptor utility to include all of these keys. This means that if a system has been encrypted and held to ransom using this type of encryption, you should now be able to decrypt your drive! The 'How-to' guide is here.

However, it apparently does not work against CryptoWall 3.0 ransomware.

Inateck FE2007 - is this the ideal Hard Disk USB 3.0 drive caddy for your Easy2Boot USB drive?

If you follow this blog, you may have read that I was not entirely happy with the Inateck FE200 drive caddy that I purchased a few months ago (previous blog post here),

After some email correspondence from Inateck, they sent me the FE2007 for evaluation.

Add UberStudent to Easy2Boot

The UberStudent ISO, uberstudent-4.1-xfce-64bit.iso does not seem to boot just as an .ISO file.
If you have a removable E2B USB drive, it will boot OK if you use the .ISOPE01 file extension (you can also use a fixed-disk E2B USB drive + an E2B WinHelper USB drive).

However, if you convert the ISO file to a FAT32 .imgPTN file it boots OK from both fixed and removable types of USB drive and you can install from it too.

E2B v1.73 released

v1.73 is now on the two Alternate Download Areas.
I will update the MPI Tool Pack with the new Switch_E2B.exe and also update the downloads on the main www.easy2boot.com website in a few days.
I have changed SWITCH_E2B.exe to version 1.0.0 and added a Help button (no change in functionality).
Please let me know if you spot a problem!

E2B v1.73 Beta G

Beta G has the new \grldr grub4dos 0.4.6a version which fixes the previous issue #84 bug that was in E2B v1.73 Beta E. non-ANSI characters should now appear correctly (e.g. ú or é).

full v1.73 Beta version history here.

Add antiX 15 with persistence to Easy2Boot

The sample .mnu file Antix_13.2_Persistent.mnu shows you how to set up root or home persistence, but not both.

Here is a brief outline of how I made a root+home persistent antiX 15 installation on my Easy2Boot NTFS USB HDD

E2B v1.73 BetaE/F (RC) version available

v1.73 Beta E is now considered a 'Release Candidate' RC version.

For a full history of v1.73 Betas, see the previous blog post here.

Unless any bugs are found, this will be the v1.73 full release version in a few days.

Please, let me know if you find any problems (steve at easy2boot dot com).

I will also upload a new version of the MPI Tool Kit which has Switch_E2B added.

Bug in BetaE!

Fabien reported a bug he noticed with french accented (i.e. UTF-8) characters in v1.73BetaE (displays a space or graphics character before each non-ANSI character) - it turns out to be a bug in the new grub4dos 0.4.6a version.  v1.73BetaF uses the previous grub4dos version (\grldr).
This bug is noticeable if you set a language in your MyE2B.cfg file, but you don't see the problem if you use the 'Change language' .mnu file!

Switch_E2B v0.1.58 Beta available (please do not use v0.1.56)

v0.1.56 had code added to restore LBA1 (the backup MBR that is copied there when you install grub4dos). This can lead to problems, so please don't use v0.1.56

The algorithm was:
If E2B backup sector 30 was invalid and sector 60 was invalid and the file MBR.BIN contained invalid contents, then use LBA1 if it has valid contents.

However, if you accidentally clicked on the 'Restore E2B partitions' button and had a grub4dos drive selected which was not an E2B USB drive, it would restore LBA1 automatically. This is usually OK as long as you did not re-partition the drive since the time that you installed grub4dos to the MBR on that drive. If however, you did install grub4dos onto the drive and then re-partitioned the drive, the LBA1 grub4dos backup would no longer be valid and Switch_E2B would write the old MBR sector to the MBR, thus losing your new partitions!

Thanks to DevaDev for reporting this when he tried it on a non-E2B USB drive!

v0.1.58 now just informs you if LBA1 is a valid MBR, but it does not restore it for you, in case you are using Switch_E2B on a non-E2B drive by mistake