The Forum has now moved to www.easy2boot.xyz/forum/
E2B Users Forum (deprecated - do not use!)
If you would like help from me (Steve Si) or other E2B users, or would like to offer help and advice to others, please post in this forum.Alternatively, post on the Easy2Boot discussion page on reboot.pro here - register and subscribe to any threads that interest you or post a new topic.You can use the E2B Live Chat Help pop-up icon on this site (you must enable pop-ups in your browser and disable Privacy Badger to see the Live Help pop-up) - if I am online, I will respond within a minute or so (if I am away from my desk, leave your email address and I will email you). For 1-to-1 email communication, use the Contact Me form and I will reply via email.
Acronis on USB
I tried to convert it to run with E2B but with no success it always fail at boot"boot error"
-Convert the complete key using MPI (FAT32). Fails.
-Try to boot directly from an image .img created with DD utility under Linux. Fails
-Try to convert the DD image .img with MPI into imgPTN. Fails
PS:I cannot recreate anymore the USB stick or an .iso
Any hints are welcome
Create Menu Item to run VHDX on PTN3
Any help would be appreciated.
Re: Create Menu Item to run VHDX on PTN3
Did you look at 'Boot Windows from VHD.mnu' ?
Just edit the full path for ISOC.
Windows 10 pro no key xml
Re: Windows 10 pro no key xml
If your system has an OEM Pro key embedded, it will be a retail\OEM key, so make sure you don't use a Volume Licence Pro generic key in the XML file. Try VK7JG-NPHTM-C97JM-9MPGT-3V66T.
Even if you use the wrong key, you can use the Activation Troubleshoot button and it should then activate.
Select Windows Start > Settings > Update & Security > Activation , and then select Troubleshoot.
SDI_CHOCO includes a script which will force the system to activate if it contains a valid key (it must be added into the .cmd script).
New Launcher utility in E2B v2.07 Beta
linux fmt_ntfs.sh install script takes forever
If I use the fmt.sh-script, everything works fine and I can use the stick right afterwards. Though if I use the ntfs-version (because I'd like to have persistence files > 4 GB), the script is stuck at "Please wait - flushing write cache and unmounting drive..." (the final unmounting after the data has been copied to the drive) for ~30 minutes.
According to my disk manager and the output of lsblk the drive is unmounted right after the script reaches that point, but if I plug out the stick at that point (meaning before the umount command exits after half an hour), it is unusable (probably in an inconsistent state).
Is this a bug or supposed behaviour (syncing the write-cache) ? If second one - why does it take that long while only copying around 90 MiB of data ? (I tried two computers, 3 different USB ports and 2 different thumbdrives, same behaviour in every possible combination)
Regardless of this issue: Thanks for offering Easy2Boot! Your E-Books where very helpful too, for understanding the mechanics of booting (e.g. technical differences of Legacy vs. UEFI boot).
Re: linux fmt_ntfs.sh install script takes forever
You can try the commands individually by typing them into the cmd shell.
Maybe try putting a pause before the sync command would fix it (allow time for filesystem to finish previous writes?).
Maybe its a ntfs-3g issue?
Wrtiing files and then issuing a sync command shouldn't cause an issue normally (though I am not experienced much with Linux)???
Re: Re: linux fmt_ntfs.sh install script takes forever
I typed the commands one by one by hand into the terminal, and 3 times I tried it, I had the same results, whereas once it unmounted "incredible fast" (something like 3 min).
Therefore I edited the fmt_ntfs.sh-script (added "sleep 5" between every pair of existing commands) and sadly that hadn't any effect.
After that I tried your script on an external HDD, which surprisingly worked flawlessly, no matter how often I tried. Aren't HDDs supposed to be much worse regarding small file writes ?? I'm kind of confused right now.
Re: Re: Re: linux fmt_ntfs.sh install script takes forever
The DPMS version can be incredibly slow to install on slow flash drives as there are 1000's of small driver files. Even on some USB 3 'fast' USB drives like the Lexar USB 3 it can take 20 minutes. Linux will cache the file writes which is why the sync is needed. Get a SanDisk Extreme Pro USB 3 or 3.1 drive!
Re: Re: Re: Re: linux fmt_ntfs.sh install script takes forever
I'll download the non-DPMS-version again and report back, after I tried again with that one.
PS: I deliberately evaded Lexar USB Thumbdrives thanks to your warning, ignoring their seemingly good price-performance ratio.
Re: Re: Re: Re: linux fmt_ntfs.sh install script takes forever
On the other hand the folders do contain the folder "_ISO/e2b/grub/DPMS/", but that folder doesn't contain thousands of files, so I guess its not the one you mentioned.
I tried the install script again and had the same result as before (as expected since it is the same folder).
Issues booting easy2boot on older computers
Re: Issues booting easy2boot on older computers
Get eBook #1 for more info on BIOSes.
Don't set first boot device as USB! Set internal HDD as first boot device and use BIOS hotkey (F8/F9/F10/F11/F12/ESC/DEL ???) to select USB drive as boot device.
Always ensure E2B USB drive has two primary MBR partitions (or more).
Check it boots OK using QEMU_Menu_Test.cmd.
Nothing showing except .isomem in the e2b/agfm boot menu.
Re: Nothing showing except .isomem in the e2b/agfm boot menu.
E2B USB drives should contain a max. of 3 Primary MBR partitions.
Re: Re: Nothing showing except .isomem in the e2b/agfm boot menu.
Re: Re: Re: Nothing showing except .isomem in the e2b/agfm boot menu.
Re: Re: Re: Re: Nothing showing except .isomem in the e2b/agfm boot menu.
Re: Re: Re: Re: Re: Nothing showing except .isomem in the e2b/agfm boot menu.
P.S. Windows Setup has been intentionally limited by Microsoft so that if you UEFI-boot, it will only install to a GPT disk - if you Legacy\BIOS boot then it will only install to an MBR boot disk. Microsoft has limited it in this way because it is easier for them to support - if Legacy BIOS Windows boot then boot disk is MBR, if UEFI Windows boot then the boot disk has GPT partitions.
5 engines (f.ex. Avg, Avast) detected PUP/malware. Download from here: https://www.fosshub.com/Easy2Boot.html?dwl=Easy2Boot_v2.05.exe
P.S. A PUP is not a virus!
Easy2boot with 3rd partition for backups
Re: Easy2boot with 3rd partition for backups
WinXP installer calls for optical disk
There is an optical drive in the system, but I get the prompt even when I disconnect it. How do I get past it?
Oh, and I should mention that the prompt makes the PC completely unresponsive, so I cant just click 'continue'.
Re: WinXP installer calls for optical disk
Re: IsVolOnDrive error
Re: Re: IsVolOnDrive error
Anyway, the important thing is that temporarily turning off drive stream makes the error message go away. Also, the error may be harmless; the creation process seems to finish successfully. But since the time consuming next step is copying 30GB onto the key, it's nice to not have any error messages at the start.
Re: Re: Re: IsVolOnDrive error
Re: Re: Re: Re: IsVolOnDrive error
Can you tell me where I can insert ventoy.json?
ptn1: \ventoy\ventoy.json is the correct location.
Re: Re: ventoy.json
I think your answer refers to a drive created with Ventoy2Disk.exe
I try to insert the ventoy.json in the combination E2B + agFM + Ventoy in the right place so that it works. UEFI boot agFM > Ventoy > F5: Check plugin json configuration.
Plugin json file /ventoy/ventoy.json does not exist.
In the Ventoy documentation I will not find anything about the combination E2B + agFM + Ventoy.
Re: Re: Re: ventoy.json
The \ventoy folder does not exist - you have to create it and create the ventoy.json file too.
Ebook title suggestions
This is Suggestion of new ebook title from naive person:
1) spy USB
2) creating forensics USB
3) Automating tasks with USB
Re: Ebook title suggestions
4) Artificial intelligence with USB
Error while making E2B drive
Every time I try to make an E2B drive, I get this error message:
In case the link does not work, the error message says 'File creation error - The system cannot find the path specified'. I have tried to use thumb drives from a few different makers, so I am fairly certain that it is not just a defective drive.
Have you got any idea what I am doing wrong?
Re: Error while making E2B drive
Do you have a \_ISO folder on the USB drive?
There should be an Easy2Boot folder on your PC Desktop - try copying the contents of that folder to the USB drive.
Re: Re: Error while making E2B drive
Is there any other reason why this error could occur?
Re: Re: Re: Error while making E2B drive
Since 100,000 people use E2B and you can watch 100's of videos on people installing E2B, your system obviously has something installed which is blocking writes.
Re: Re: Re: Re: Error while making E2B drive
I can't wait to get started using this wonderful tool, thank you for your work.
Re: Re: Re: Re: Re: Error while making E2B drive
cannot boot to ventoy
error 13: Invalid or unsupported executable format
Re: cannot boot to ventoy
What sizes are the 1st and 2nd partition of the E2B USB drive?
Did you test using \QEMU_MENU_TEST.cmd? If that works and a real system does not, then maybe you have a large 1st partition and a BIOS with the 128GiB bug?
Try latest agFM (run Update_E2B_USB_drive.cmd).
E2B+agFM now supports Ventoy
You can now add Ventoy to the second partition (using the Add_Ventoy.cmd batch file) and so can MBR-boot and UEFI64-boot to Ventoy.
Also, because you can Secure UEFI64-boot to agFM first, you can then load Ventoy from a Secure Boot.
eBook #4 has also been updated.
great idea, good video , but
I used Ubuntu sticks before. Worked fine. Although I am a newbee in Linux. The basic idea first is, to have a portable office. Email, wp, ss independent from PC.
Now with uefi, nothings works. Afters hours of searching and trying, I found your page. Worked through the video. Now on legacy everything is fine. Then trying the same stick on uefi and everything is different: The menu, the structure... and the main thing: there isn't a persistent LINUX at all. Ubuntu, yes, but only temp os. Any idea how to fix it?
Re: great idea, good video , but
You can have persistence with a Ubuntu ISO. You need to create a persistence file and rename the Ubuntu ISO file extension to .isopersist. See eBook #4 if you need more help. You can have multiple ISOs with multiple persistence files.
Re: Website Clarity
I can't see much about 'partitioning' in that page - only about preparing a .imgPTN partition image.
If you are interested in Win7 install from ISO using UEFI64, then the easiest way now is:
1. Prepare a E2B USB drive + agFM using the download.
2. Add your Windows 7 64-bit ISO to \_ISO\WINDOWS\WIN7 folder
3. UEFI64-boot to the E2B USB drive - select the Win7 ISO file - select the 'Windows ISO' option and boot to Win7 Setup.
Note that Win7 does not support USB 3 or newer USB chipsets however and will only work with older systems (unless you add drivers to the ISO file).
eBooks with full details and Exercises to follow are available ;-)
Unable to format USB
Re: Unable to format USB
Re: Re: Unable to format USB
Re: Re: Re: Unable to format USB
2. Install E2B to 128GB USB drive
If 1 passes and 2 fails, then clearly the 128GB drive is faulty. If 1 fails, then clearly something is blocking writes to the USB drive.
filed. I use this version and it works: https://www.soft-go.com/get/WSCC-Portable-Edition_71264.html
E2B booted using Plop but GRUB4DOS USB 2.0 drivers doesn't install
Apparently, using Plop made the USB boot successfully to the boot menu, and the entries work except the Hiren's Boot CD because all menu entries lead to "No device found." So I've discovered an option called "Install fast GRUB4DOS USB 2.0 drivers," and the description says to install it if I have booted to USB using Plop or if the USB is bigger than 137GB. My stick is only 8GB.
As soon as I clicked on that option, it fails to install, saying "Error 81. No USB device found. USB drive enumeration failed. Try to restart." It would get stuck there. The problem is that I have inserted the stick, so it should detect that.
What should I do to ensure that the GRUB4DOS USB 2.0 drivers install successfully?
Re: E2B booted using Plop but GRUB4DOS USB 2.0 drivers doesn't install
Some BIOSes will recognise larger USB drives as USB HDD type if they have two primary partitions.
P.S. Try also Ventoy which does not need a write-enabled drive?
Re: Re: E2B booted using Plop but GRUB4DOS USB 2.0 drivers doesn't install
Force iso to be fragged for testing
Re: Force iso to be fragged for testing
Another way to get fragmented files is to directly download ISOs from the internet onto your USB drive - always download the ISO to your internal disk first and then copy the ISO to the USB drive. Downloading a file will usually cause the file to be highly fragmented!
Re: Re: Force iso to be fragged for testing
Re: Re: Re: Force iso to be fragged for testing
If that doesn't work then you need to ensure you have plenty of free space on the first partition (to make a 3GB file contiguous you will need approx 4GB of free space) - or buy a bigger USB drive.
You can use the Windows program defraggler.exe to make individual files contiguous (right-click on the file) and this can often work when MAKE_THIS_DRIVE_CONTIGUOUS.cmd fails to work because it does not have enough free CONTIGUOUS space on the drive. Anyone who makes a fresh E2B drive and then copies files to it will have no problems with non-contiguous files - all the files will be contiguous. You only get non-contiguous files once you start DELETING files - e.g. if you have 100GB partition, once you copy 100GB of files to the partition (even if you deleted some of the files at some point), then you will start to get fragmented files.
Re: Re: Re: Re: Force iso to be fragged for testing
copy /b big.iso + small.txt big_fragmented.iso
small.txt should just be any file of a few bytes in size. The ISO should still be bootable too.
WinContig can be run from the command line, so you could run it after the xcopy has finished to check. Typically, linux ISOs should be contiguous and simple Windows ISOs do not need to be contiguous.
Surface Book 3
Re: Surface Book 3
If still problems, replace the EFI file as detailed on the a1ive grub2 File Manager page on this site.
Re: Re: Surface Book 3
Thanks for the reply. I replaced the Files as described. I even did it manually. The version of E2B is 2.04 and agfm is 1.55. Still being blocked although secure boot is off.
Re: Re: Re: Surface Book 3
Advanced Device Security
This option lets you disable ports and features you don’t want anyone to use.
The current setting appears in bold. Select Advanced Device Security and select the option you want:
Note: Selecting Side USB disables the ability to boot from a USB device. The USB port remains enabled in Windows.
Could that be the issue?
Re: Re: Re: Re: Surface Book 3
Re: Re: Re: Re: Re: Surface Book 3
Re: Re: Re: Re: Re: Re: Surface Book 3
Also found this: https://nkdagility.com/blog/microsoft-surface-3-unable-boot-usb/
Apparently you may need to use a volume name of BOOTME for the 2nd? partition?
I presume that the issue you describe is ONLY found on your Surface Book 3?
Re: Re: Re: Re: Re: Re: Re: Surface Book 3
Specific boot order for Surface Book 3 needed ??
Re: Re: Re: Re: Re: Re: Re: Re: Surface Book 3
Re: Re: Re: Re: Re: Re: Re: Re: Re: Surface Book 3
"The Kaspersky shim \efi\boot\bootx64.efi may be blacklisted by the BIOS. First do a Windows 10 Update to ensure it has latest KB updates.
Read more: https://www.easy2boot.com/forum/"
Do You mean the actual Windows 10 Updates or BIOS Updates? How would the missing Windows 10 Update have any influence over something, that happens before system boot?
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Surface Book 3
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Surface Book 3
Yeah I just realized this today as a Surface Book 2 was doing a firmware update :) I'll try this with the updates. thanks for the input.
iso windows 7 x64 bits pro efi
error: failed to boot vdisk ..
using map ..
error: failed to boot vdisk ..
failed: press a key to continue
What I want is to launch that iso of w7x64 professional from efi, and be able to repair equipment
from command line to recover boot boot ...
Re: iso windows 7 x64 bits pro efi
The standard Microsoft Windows 7 ISO does not contain the standard \EFI\BOOT\BOOTX64.EFI boot file which is required to boot from non-CD media like hard drives and USB drives.
You can either find a Win8/10 ISO, extract the file from it using 7zip and then add the file into the Win7 ISO using a utility like PowerISO or ISOBuster, or make a .imgPTN23 file from the ISO using the MPI Tool Kit. This will usually add-in the file for you, but if it does not, you can add it in yourself.
Re: Re: iso windows 7 x64 bits pro efi
I have even added boot.wim and install.wim of that iso in another iso that yes is efi booteable (the one that fails me is udf booteable), to see if it succeeded but when booting it gives me error file: \ winedows \ system32 \ boot \ winload.efi
missing or corrupt
The problem is that I have an iso w7 that does boot with efi, but when it repairs it tells me that it is not the installed version of windows
And the iso that if you let me repair let me repair in legacy, but in efi it gives me those errors ...
Can you convert a bootable iso udf to bootable efi ??
Or some other possibility?
Where would be the tools to create an imgptn ???
Thank you so much for your help
Re: Re: Re: iso windows 7 x64 bits pro efi
Either you are using the 32-bit version which does not support UEFI or you are not using an official Microsoft Win7 64-bit ISO.
To use a .imgPTN file, see the MPI Tool Kit page.
P.S. Note that Win7 UEFI 64bit is not supported by Virtual Box - you must test using a real system. I tried an official Win7 MS ISO using agFM and UEFI64 and it boots OK.
Also note that Windows 7 ISOs do not contain modern USB drivers and so will only work on older USB 2 systems.
A standard MS Win7 ISO boots OK from agFM via UEFI64 on my old systems.
Re: Re: Re: Re: iso windows 7 x64 bits pro efi
Regarding imptn, I have carried out tests, but I must have done something wrong, I have transformed the iso to imptn, but it has "transformed the pendrive", to an iso windows 7 and I have had to generate it again.
I've been looking for a long time for an official iso windows 7 professional x64 svpk1, in Spanish or multilanguage, and I can't find it, much less updated ...
As for the usb 3.1, I integrate them into the iso and reassemble it, and so I can install windows 7 on eighth and ninth generation coffee lake equipment, which is my goal for example (hp 800 g4 sff), and thus be able to generate a sysprep for other computers.
All the tests I'm doing, adding the iso in the windows 7 folder of the usb e2b ..., against a physical computer with windows 7 with usbs 3.1.
How is starting from agfm ???, I don't understand?
All my objective is to get the iso with windows 7 that I have svpk 1 professional, allow me at work, to recover a corrupt boot and regenerate the boot boot from the command line, booting the iso from uefi of the pendrive with e2b, with legacy works correctly, but with efi I still can't get it ...
Could you pass me a link to an official iso windows 7 professional x64 bit Spanish (or at least multi-brand?) Since I can't find it ...
Again a thousand thanks for the help and answers
Re: Re: Re: Re: Re: iso windows 7 x64 bits pro efi
x17-58868.iso is the Spanish Win 7 SP1 x64 I think.
.imgPTN files are partition images. If you switch one in, it replaces the first partition. You should use an extensions of .imgPTN23 if you are using agFM. To switch back in the original E2B partition, boot to the second agFM partition using the BIOS Boot Selection menu and 'Restore E2B partitions'.
Re: Re: Re: Re: Re: Re: iso windows 7 x64 bits pro efi
Nothing, I give up for now, all the isos that I have tried, combining boot.win, install win, in legacy they work for me, but in efi, either they are not the same that I have installed on the computers or it gives the error reported in the message above, when loading the vim into efi ...
Re: Re: Re: Re: Re: Re: Re: iso windows 7 x64 bits pro efi
Re: Re: Re: Re: Re: Re: Re: Re: iso windows 7 x64 bits pro efi
You could put or generate an xml, in w7, or w10, to only repair
no installation just repair to access command line options to recover a boot sector?
I have got a usb, which sends us special hp and I want to try to integrate the usb 3.1 into it, but I would need an xml, in which it allows only repair, could it be done?
Re: Re: Re: Re: Re: Re: Re: Re: Re: iso windows 7 x64 bits pro efi
And the version that I have and if it is compatible to repair, even putting the file \ EFI \ BOOT \ BOOTX64.EFI
from a windows 10 iso, when i boot with the first efi option (boot iso (partnew / easyboot) .isodef)
it gives me an error failed to vdisk
using map ...
error failed to boot disk
press a key to continue
and with that image in legacy if it allows me to get to repair equipment and load recovery options
boot, command line, etc ...
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: iso windows 7 x64 bits pro efi
And the one that I have downloaded that does load the vdi, but it does not allow me to access to repair equipment because it is not compatible, it marks the ultra iso as (bootable efi)
Could I convert an iso from udf bootable to efi bootable with some software ???
PS: The image you have given me of the link and marks me as bootable efi does not have the file \ EFI \ BOOT \ BOOTX64.EFI
And it starts correctly with the first option of efi
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: iso windows 7 x64 bits pro efi
If you MBR boot you can only repair an OS that legacy boots. if you UEFI-boot, you can only repair a disk that UEFI boots and has GPT partitions.
Why not boot to WinPE shell and run Diskpart and check the disk - DISKPART - LIST DISK - SEL DISK 0 - LIST PART - LIST VOL - DETAIL DISK- EXIT
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: iso windows 7 x64 bits pro efi
I will confirm it tomorrow, it may be that I was trying to recover using uefi, an operating system that has a mbr partition and as you say, and we would close this question ...
Thank you very much for your patience and help again.
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: iso windows 7 x64 bits pro efi
The question, that I would stay now is if there is any iso from w7, that uefi can be installed ...
Thanks for your help and patience
How do I make a imgPTN file out of Pop! OS?
But something went wrong with symbolic links, it just fails to create symbolic link every time.
Re: How do I make a imgPTN file out of Pop! OS?
You can use IsoBuster to extract the contents to a folder and then drag-and-drop the folder onto the MPI_FAT32 Desktop shortcut to make a .imgPTN23 file. You can also try 7Zip (right-click on the ISO in Explorer and choose 7Zip - # instead of the default 7Zip entry).
PopOS ISO UEFI64-boots fine directly from the ISO file if you UEFI-boot to agFM.
Otherwise, make a blank PopOS.imgPTN file and PopOS. file and install a full PopOS onto them so you can boot a full PopOS.
Look on https://rmprepusb.blogspot.com/p/easy2boot-useful-blogs.html for 'full install' blog articles for hints.
how to shutdown from live-cd
I need this ubuntu version because it's better compatible withe the built-in microphone of my laptop. I boot by UEFI due to agFM. But i see that shutdown feature always fail. It hangs on umounting isodevice which always fail. So I need to hold down power button.
Re: how to shutdown from live-cd
Select ISO - select .isodef entry - get Ubuntu menu - press e for edit - add noeject before the quiet word - press F10 to boot.
Because it is LiveCD boot, switching off will do not harm anyway.
Re: Re: how to shutdown from live-cd
Re: Re: Re: how to shutdown from live-cd
See sample mnu files for Linux Ubuntu+persistence
Re: Re: Re: Re: how to shutdown from live-cd
Re: Re: Re: Re: Re: how to shutdown from live-cd
Re: Re: Re: Re: Re: Re: how to shutdown from live-cd
I will send you a snapshot by email
PLEASE USE THE NEW FORUM at www.easy2boot.xyz
Recommended for Easy2Boot (fastest flash drive!)
SanDisk Extreme SDCZ880-128G-G46
Fastest USB 3!
See Blog post