Add multiple WindowsToGo images
For WindowsToGo, you will need a fast USB 3.0 drive - I highly recommend the SanDisk Extreme or Extreme Pro flash drives or any fast USB 3.0 HDD or SSD. Beware of some other 'fast' flash drives such as the Lexar P20, etc. they can take over one hour to boot!
MBR-booting: if UEFI-booting is not required (or not supported), you need only create one large NTFS .imgPTN partition and use this as both the boot and system partitions or alternatively you can create a VHD file (see box).
UEFI-booting: we need to convert the payload to an image partition (.imgPTN) file using MakePartImage. The system partition contains the boot files in the \EFI folder and needs to be formatted as FAT32 to make it UEFI-bootable. The Windows OS files can be on a separate NTFS partition.
Note 1: E2B v.1.69+ can directly MBR-boot from fixed-type .VHD Windows 7/8/10 OS files. Just copy the Windows VHD\VHDX files (must not contain spaces in the filename) to one of the E2B menu folders such as \_ISO\MAINMENU or \_ISO\WIN and boot (the file does not even need to be contiguous). The VHD/VHDX must contain a fully installed and rebooted copy of Windows - if you boot from a VHD that contains a Setup install or Sysprep'ed OS (e.g. as made by WinNTSetup or ImageX), the setup process on the first boot will report an error because of the lack of boot files or a boot partition.For instructions on how to create Windows 7/8/10 VHDs easily, see below or read my blog posts he and rehere.
Note 2: Direct booting from a VHD in E2B requires a Windows 8.1 version of bootmgr (or similar) in \_ISO\e2b\grub\DPMS\NTBOOT.MOD folder (the Windows 10 bootmgr gives a BSOD 0xc00000bb bad BCD error!). See here for more details.Note 3: If you already have a WinToGo .imgPTN file (or any disk partition with WinToGo), you can copy it into a .VHD file - see this blog post for details.
How to add MBR-bootable WindowsToGo payloads easily (7/8/8.1/10)
Note: If the system that you boot from was previously activated for Windows 10, then Win10ToGo will be automatically activated when you boot to it (as long as the Home/Pro edition matches what was previously installed).
Instructions (VHD for MBR-booting only)
1. Make sure the E2B USB HDD drive is in the normal E2B Menu mode (not in CSM Menu mode) and you can see the \_ISO and other folders. An NTFS-formatted E2B drive will be required (not FAT32-formatted).
2. Run WinToUSB, select a Win7 Ultimate or Enterprise ISO or Win8/8.1/10 ISO and then specify a VHD on the target drive (e.g. VHD=20GB).
3. When WinToUSB has completed, boot from the USB drive - it should boot to Windows immediately (i.e. no E2B menu, no grub4dos).
4. Complete the final Windows OOBE Setup Stage as normal - you must do this before you copy or move the .VHD file.
5. If you installed to an E2B USB HDD, now re-install grub4dos to both the MBR and PBR of the E2B USB drive again using RMPrepUSB so that it will boot to grub4dos again.
- RMPrepUSB - Install grub4dos - Yes=MBR (do not update \grldr)
- RMPrepUSB - Install grub4dos - No=PBR (do not update \grldr)
Note: E2B needs the Win 8.1 file bootmgr in the \_ISO\e2b\grub\DPMS\NTBOOT.MOD folder on the Easy2Boot USB drive. Do not use the Windows 10 version of bootmgr (10-07-2015 395,268 bytes) as this gives a BSOD 0xc00000bb error! This file may have already been copied by the MAKE_E2B_USB_DRIVE (run as admin).cmd script when you first made the E2B drive. E2B will warn you if it is missing or if it is an incompatible version. If bootmgr cannot be found in the \_ISO\e2b\grub\DPMS\NTBOOT.MOD folder then \bootmgr in the root of the E2B drive will be used (if present).
Now tidy up - Delete the \boot and \EFI folders from the E2B USB drive and the \bootmgr file (if present). If you don't remove the boot files or don't move the VHD file, WinToUSB will refuse to add another OS if you run WinToUSB again to make another VHD.
E2B NTFS USB Hard Disk only (MBR+UEFI booting)
This will make a 64-bit WinToGo system from a 64-bit Windows Install ISO that will boot on both UEFI and MBR 64-bit systems.
If you use a 32-bit Windows UEFI source ISO (e.g. Windows 8.1 or 10 32-bit) then it will be bootable on 32-bit UEFI and 32/64-bit MBR systems.
- Select a 64-bit Windows Install ISO as the source (Win8/8..1/10 recommended) - I tested with Win8.1 Enterprise Evaluation version.
- Select the small ptn as the system volume The system partition is the primary partition that is used as the active EFI System boot partition
- Select the large ptn as the boot volume The Boot partition is the partition where Windows is installed. It includes a Windows directory.
- Select a 64-bit Windows \sources\Install.wim file from a mounted ISO as the source (Win8/8..1/10 recommended) - I tested with Win8.1 Enterprise Evaluation version.
- Select the small partition for the system partition
- Select the large partition for the boot partition
- Use the 'ALL' option (default) when prompted in the next step
Do not copy grldr, if prompted.
(Do NOT install grub4dos to the PBR).
If you move or copy the .imgPTN file (even on the same drive), it will no longer boot to Windows because the Disk Signature will be different. To fix this, you will need to run BootIce or bcdboot again to correct the BCD(s). Note that this also means that you cannot just copy the .imgPTN file to another E2B USB drive and expect it to work.
E2B USB Removable Flash drive - Win7 only (MBR+UEFI - not for Win8.1)
You should now see just the NTFS empty partition in Windows Explorer (if not unplug and re-connect the E2B USB drive).
- Select a 64-bit Windows Install ISO as the source (Win8 x64 recommended)
- Select the same ptn as system ptn and boot ptn
- Select a 64-bit Windows \sources\Install.wim file from a mounted ISO as the source (Win8 recommended, but not 8.1 if using a Removable USB drive!)
- Select the same USB ptn as system ptn and boot ptn
- Use the 'ALL' option (default) - select 'Do Not update the boot code' from the drop-down list.
Do NOT install grub4dos to the PBR!
If you move or copy the .imgPTN file (even on the same drive), it will no longer boot to Windows because the Disk Signature will be different. To fix this, you will need to run BootIce or bcdboot again to correct the BCD(s). Note that this also means that you cannot just copy the .imgPTN file to another E2B USB drive and expect it to work.
Rufus & WinToGo
The latest version of Rufus 2 has a WindowsToGo feature which will automatically format and make a USB WinToGo flash drive from a Windows Install ISO.
If you have made a Rufus WinToGo MBR+UEFI flash drive, you can use the contents of the NTFS partition as the Source to make a large NTFS .imgPTN file and follow steps 3a and 3b above to make the other FAT32 partition image file.
Note: If you have a Removable E2B USB flash drive, Win8.1/10 will not boot (see below).
Boot WinToGo using a VHD (recommended for Win8.1/10 + a Removable USB)
See here for how to make and boot using a VHD (MBR booting). You can boot Windows 8.1/10 from a Removable USB drive using this method (or a USB hard disk).
As an alternative, you could just have an E2B USB HDD containing lots of VHD's and just a FAT32 .imgPTN23 file for each different version.
e.g.
E2B Partition 1 - containing E2B files with WinToGo8.imgPTN23, WinToGo8.1.imgPTN23, Win7ToGo.imgPTN23, etc.
E2B Partition 2 - containing many vhds, e.g. \Win8.vhd, \Win8.1.vhd, etc.
Then load the .imgPTN23 file to get to CSM mode, configure the BCD(s) to point to the vhd file on the 2nd partition
Tip: If you have a 64-bit WinToGo .imgPTN file, add '64' to the end of the file extension and it will only appear in the E2B menu if you are running on a 64-bit system - e.g. Win81ToGo.imgPTN64.
You can also directly MBR-boot from a WindowsToGo .VHD or VHDX file with E2B v1.69+. The VHD must contain a fully pre-installed version of Windows (i.e. it should not run Setup on first boot or it will fail).
WinToGo UEFI booting from a Removable E2B USB drive
For MBR+UEFI booting of Windows To Go from a Removable drive, you can adapt the method described here. You will need to create two .imgPTN files first (e.g. 300MB FAT32 Win.imgPTN and 20GB NTFS Win) and then switch to CSM mode first.
Activation
WindowsToGo is a full installation of Windows and will require activation if you want to use it regularly. When you activate a normal Windows OS and enter a Product Key, the hardware signature is registered with Microsoft and added to the OS itself. Once activated, if you boot the same OS on a different system, it will not be activated.
For this reason, you should use a volume licence version of Windows (e.g. Windows 8 Enterprise version) if you need an activated copy of WindowsToGo or use a Trial Enterprise version (90 day) and then re-install it again when it expires. A volume licence version of Windows is not hardware-locked.
Tip: Once you have prepared the .imgPTN files, make a copy of them before you boot them for the first time. When the 90 day trial period ends, just replace the .imgPTN file with a copy of the original.
If you name the .imgPTN as .imgPTNaLBA23 the 2nd partition of your E2B drive will not be removed and so will remain accessible. You can therefore keep all your portable Windows applications, drivers and documents on the 2nd partition.
If you boot to Windows 10 To Go Home/Pro on a system that had previously contained an activated Windows 10 Home/Pro OS, then it should 'phone home' and automatically activate provided that the Edition is the same as the one that was previously activated.
Deleting WindowsToGo files
Windows may not let you delete some of the WindowsToGo files even if you have Admin rights (usually because you are not the Owner).
I recommend installing Take Ownership and also LockHunter.
Using these two Windows utilities, you can change the Ownership rights or find out what process is locking a file or folder or drive and kill it.
Copying WindowsToGo files
Windows will not allow you to easily copy a complete WindowsToGo installation as files to another folder or drive (e.g. using Xcopy or Explorer).
Windows will lock some of the WinToGo system files and it will also interpret any symbolic links (e.g. when it sees the 'My Documents' hard link in the WinToGo drive, it will start trying to copy all of your C: drive's Documents too!).
A nice way to copy all the WindowsToGo files to a different destination is to use Olof's strarc utility.
1. Switch to the .imgPTN file using \_ISO\SWITCH_E2B.exe - my E2B USB drive was now drive D: (16GB) and had the full WinToGo installation on it as flat-files (\Windows, \Program Files, etc.).
2. Delete any unwanted files (e.g. \hyberfil.sys, pagefile.sys, etc.) .
3. Create and attach a fixed VHD using Windows Disk Management console (diskmgmt.msc) - this gave me a virtual 16GB Q: drive.
4. Download strarc and extract it.
5. From an Admin Windows cmd shell, we copy all files on D: to Q: using:
strarc.exe -cjd:d:\ | strarc -xd:q:\
Note: you can safely ignore any error messages about the \System Volume Information folder.
Be sure to use the vertical bar | key as shown (Shift+)
Olof recommends this so that some files are also excluded:
strarc -c -j -e:"\System Volume Information,\Temp\,\Temporary Internet Files\,\Cache\,.tmp,pagefile.sys,hiberfil.sys,\$NtUninstall" -d:d:\ | strarc -xd:q:\
To ignore messages about 8.3 filename compatibility (I didn't see any) , use -s:8.
I first formatted Q: so it was empty of all files.
6. Detach the Q: drive in the Disk Management console and copy the VHD file to \_ISO\MAINMENU on my E2B USB drive and boot it!
If some files are locked or held open by Windows, you can try using a Volume Shadow Copy Service (VSS) utility such as ShadowSpawn to make a virtual copy and then run strarc using the new virtual drive as the source. You can also try U-Recover to create a shadow copy of a drive.
See here for how to make the WinToGo files on a USB drive (or inside a .imgPTN file) into a .VHD file.