Jump to content











Photo
* * * * * 1 votes

UEFI MULTI - Make Multi-Boot USB-Drive

grub4dos vhd win8 multiboot usb uefi

  • Please log in to reply
81 replies to this topic

#76 koesherbacon

koesherbacon
  • Members
  • 1 posts
  •  
    United States

Posted 21 June 2015 - 04:08 AM

This is my first post here, so I hope I'm not asking something that's been answered a hundred times before...

 

Since I'm using Windows 8.1 my current boot method is UEFI.  I stumbled upon these forums while trying to find a way to put a number of different Linux OSes, my Windows 8.1, and some Rescue Utilities onto a 32gb USB.  

 

The USB drive I ended up with at the end of the process was not recognized by my UEFI.  It was, however, recognized by the CSM but in that situation none of the OSes I put onto the USB showed up!

 

Here's what I ended up doing, maybe when you look at my steps, you'll be able to tell me what happened and how I can fix it when I try again.

 

I downloaded UEFI_MULTI_85.exe from http://reboot.pro/fi...boot-usb-drive/.  When I opened the file, it used 7zip to auto-extract everything into a \UEFI-Multi\ folder.  That part I’m pretty sure I got right.  Since it’d be really difficult to do that wrong!  From there, I read the UEFI_MULTI_Help.txt file and though I understood how to use the software.  I inserted the USB drive I wanted to use and ran UFD_Format.exe and believe everything worked perfectly find there as well.  I then had what I think is a properly formatted FAT32 USB drive.

 

I then went into the \MULTI_BOOT\Images folder.  I put all the OS and Rescue ISOs I wanted to be available:

Windows:

Windows.8.1.blah.blah.blah.iso

Linux:

antergos-2015.04.12-x86_64.iso

archlinux-2015.06.01-dual.iso

Bella-OS-2.2-64bit.iso

black-lab-linux-2015_6-x86_64.iso

black-lab-linux-Xfce4.12-x64_86.iso

bridge-xfce-2014.02-x86_64.iso

chakra-2015.03-euler-x86_64.iso

chaletos14.04.2-feb2015-light-amd64.iso

deepin_2014.3_amd64.iso

elementaryos-freya-amd64.20150411.iso

handylinux-2.1.iso

KaOS-2015.06-x86_64.iso

kubuntu-15.04-desktop-amd64.iso

MakuluLinux-8-LxFce.iso

MakuluLinux-9-Aero-x64.iso

MakuluLinux-9-XfceLite-x64.iso

manjaro-kde-0.8.13-x86_64.iso

manjaro-xfce-0.8.13-x86_64.iso

maui-0.5.1-x86_64.iso

netrunner-16-dvd-64bit.iso

netrunner-rolling-2014.09.1-dvd-64bit.iso

Pinguy_OS_14.04.2-LTS-x86-64.iso

Solus-Beta2.iso

symphonyos-15.0_amd64.iso

wattOS-R9-64.iso

Rescue:

Hiren's.BootCD.15.2.iso

PING-3.02-WithAddons.iso

ubcd535.iso

 

In total, all of the above was just under 28gb.  Luckily, the USB drive I just formatted had 29gb available.

 

I then went back to the main UEFI_MULTI folder and ran UEFI_MULTI.exe as Administrator.  I told it that my USB Boot was D: (the USB drive I just formatted) and my System Drive was C: (where Windows 8.1 is currently installed, of course).  I kept the Copy to: Boot Drive option and told it that the Source Folder was \MULTI_BOOT\Images. 

 

At this point, I might have made the error by selecting all the available options:

✔ Add G4D to Boot Manager

✔ Add XP to Boot Manager

✔ Update MBR Boot Code

✔ Add Boot Win 7/8 System

✔ Update Grub4Dos gldr

✔ Grub 2 EFI Mgr

 

Should I not have selected everything?  If not, which of those options should I select, and which should I leave alone?

 

It did its thing and everything seemed fine when it finished.  But like I said at the beginning, when I rebooted my computer the UEFI did not detect the USB and went straight to Windows 8.1.  When I switched my BIOS to CSM, it did detect the USB, but nothing was selectable except for the default options such as editing the Grub4Dos menu.

 

What can you tell me about what I might have done incorrectly?  Is there anything that obviously jumps out at you?

 

Maybe someone can walk me through this process again so the next time I will be successful attempt to make a Multi-Boot USB with the above listed OSes and Rescue ISOs.

 

Thanks a lot!

 

〜 Ev



#77 Lukys

Lukys
  • Members
  • 4 posts

Posted 04 August 2015 - 11:55 AM

Hi. How i can edit created boot menu on USB after build manually? Thanks



#78 S466531257BOSS

S466531257BOSS

    Member

  • Members
  • 33 posts
  • Location:NIEDERSACHSEN ( Lower Saxony ) , HANNOVER ( Hannoi )
  • Interests:ETC PP ...
  •  
    Germany

Posted 05 August 2015 - 08:43 AM

@koesherbacon @Lukys

 

As you stated you thought anything went fine and the ' only ' obvious problem is that Windows 8.1 boots directly in UEFI-Mode without hesitating | showing up the BootMGR-Menu displaying other options

; Have a look at the BCD-Store on the drive you created by plugging in the FlashDrive on a running Windows NT 6+ System, means from Vista upwards ( in your case most likely Windows 8.1 ) and use an administrative Command Prompt to be sure to read out the BCD of the stick by using

bcdedit /store U:\Boot\bcd /enum

: or use your already booted Windows 8.1, whereas you have to use the drive-letter of the system ; mostly

C: 

=INFO

bcdedit

: tool to manipulate the BootCode used by BootMGR

/Store

: Parameter ' Store ' followed by the path to the bcd-file you wish to read | edit

U:\Boot\BCD

: The path to the BCD-Store on your Flash-Drive

 U:

 --- Assuming you used drive-letter ' U ' ( e.g.: U for USB )

\Boot\

 --- Standard-Directory generated by ' bcdboot '-tool when using ' /f ALL ' or ' /f BIOS ' as Parameter for FirmWare-Type of Target-Partition

BCD

 --- Standard-Naming for the BCD-Store created by ' bcdboot '

 

; The ' Boot '-folder is a hidden- system- -folder so either you have to change your view-settings of Windows Explorer to show up hidden and system files or you just type the path ' <drive-letter>:\Boot\ ' ( e.g.: U:\Boot\ ) directly into the path-|adress- -bar to access the contents of it .

 /enum

 --- enumerates | lists the entries of the BCD-Store you are loading

 

; That's how you can get an insight of what really is inside , likewise to say you can check if other options have been stored by the script or not

 

; and if you you find out there are other entries , then you might wish to have a lookout for the options ' displaybootmenu' | ' displayorder ' | ' timeout '

 

= EXAM

:

Bezeichner              {bootmgr}
device                  partition=O:
description             Windows Boot Manager
locale                  de-DE
inherit                 {globalsettings}
default                 {default}
resumeobject            {7e05cdb8-3afa-11e5-975d-0022190d3ea7}
displayorder            {default}
toolsdisplayorder       {memdiag}
timeout                 30


Windows-Startladeprogramm
-------------------------
Bezeichner              {default}
device                  vhd=[O:]\_ISO\AUTO\WIRT\BMWN63SC\BMWN63SC.vhd
path                    \Windows\system32\winload.exe
description             Hyper-V Server 2012 R2 (VHD)
locale                  de-DE
inherit                 {bootloadersettings}
recoverysequence        {a1c28fef-3ab4-11e5-8124-002264cbf2c3}
recoveryenabled         Yes
allowedinmemorysettings 0x15000075
osdevice                vhd=[O:]\_ISO\AUTO\WIRT\BMWN63SC\BMWN63SC.vhd
systemroot              \Windows
resumeobject            {7e05cdb8-3afa-11e5-975d-0022190d3ea7}
nx                      OptOut
hypervisorlaunchtype    Auto

=EDIT

--- To show up the bootmenu

bcdedit /set {bootmgr} displaybootmenu yes

--- if you use ' no ' instead of ' yes ' it will not show up .

 

=EXAM

--- after EDIT

Windows-Start-Manager
---------------------
Bezeichner              {bootmgr}
device                  partition=O:
description             Windows Boot Manager
locale                  de-DE
inherit                 {globalsettings}
default                 {default}
resumeobject            {7e05cdb8-3afa-11e5-975d-0022190d3ea7}
displayorder            {default}
toolsdisplayorder       {memdiag}
timeout                 30
displaybootmenu         Yes


Windows-Startladeprogramm
-------------------------
Bezeichner              {default}
device                  vhd=[O:]\_ISO\AUTO\WIRT\BMWN63SC\BMWN63SC.vhd
path                    \Windows\system32\winload.exe
description             Hyper-V Server 2012 R2 (VHD)
locale                  de-DE
inherit                 {bootloadersettings}
recoverysequence        {a1c28fef-3ab4-11e5-8124-002264cbf2c3}
recoveryenabled         Yes
allowedinmemorysettings 0x15000075
osdevice                vhd=[O:]\_ISO\AUTO\WIRT\BMWN63SC\BMWN63SC.vhd
systemroot              \Windows
resumeobject            {7e05cdb8-3afa-11e5-975d-0022190d3ea7}
nx                      OptOut
hypervisorlaunchtype    Auto

 

=INFO

BCDEdit Command-Line Options

 

; For sure it can be told leaner , but maybe you / another reader is tickled enough to start having some fun by directly editing via a command-line instead of avoiding it and just hoping that scripts and tools do some automagical secret stuff ; the least is comfortable , but if i am using something that i do not understand i ( for myself ) at least like to know what has happened in the end .

 

=NOTE

--- for those that have gained interest in editing via command line and especially bcdedit

: If you wish to understand what options you have available and how they are used

bcdedit /?

--- general help

bcdedit /? /store

--- displays the help-information specific to the parameter ' /store '

HOPE IT HELPS .

 

 

THANKS FOR YOUR INTEREST .

 

S466531257 BOSS

PAETH CLAUDIUSRAPHAEL


Edited by S466531257BOSS, 05 August 2015 - 08:53 AM.


#79 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13752 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 05 August 2015 - 01:38 PM

Well, on UEFI the BOOTMGR may not exist, since what is booted is bootmgfw.efi and the BCD is not in \boot\BCD but rather in \EFI\Microsoft\boot\BCD

 

Casually Misty recently published a very detailed guide/how to related to BCDediit and BCD stores:

http://reboot.pro/to...and-bcd-stores/

http://www.mistyrebo...Edit/index.html

 

:duff:

Wonko



#80 Franz Ferdinand II.

Franz Ferdinand II.
  • Members
  • 7 posts
  •  
    Macedonia

Posted 18 October 2015 - 12:27 PM

Greetings, I've come back to the tool now and need some things cleared:

If I intend build a drive booting on both BIOS and UEFI systems to :

-Win81SE

-Win 10 installation DVD

-Ubuntu ISO

-Parted Magic (and eventually other Linux-based ISOs)

-Hirens BootCD 15.2

-UBCD 5.3.5

-Paragon recovery ISO based on Win10PE

-Macrium Reflect ISO based on Win8PE

 

Where all the ISO's (except Win81SE) should be defined?

Does UEFI_MULTI give another option except grub4dos?

 

Now I tried to perform UEFI_FORMAT on empty USB stick. getting some internal app error (using default presets)

Is it OK to format using standard Windows formatting tool?



#81 wimb

wimb

    Gold Member

  • Developer
  • 2281 posts
  •  
    Netherlands

Posted 18 October 2015 - 01:34 PM

If I intend build a drive booting on both BIOS and UEFI systems to :

-Win81SE

 

Now I tried to perform UEFI_FORMAT on empty USB stick. getting some internal app error (using default presets)

Is it OK to format using standard Windows formatting tool?

 

In what OS environment did you use UFD_FORMAT.exe  and what is exactly the error that you get ?

Does it help when you Uncheck Make Boot Menu ? What type of USB-Stick did you use (is it a removable drive) ?

 

For Win81SE Builder take care in Build > CdDrive - X: Y: to Select Run ALL Programs from RAM

In UEFI_MULTI Select boot.wim file and boot.sdi file as described http://reboot.pro/to...ve/#entry168079

You use wim booting which is compatible with BIOS and UEFI BootManager menu and you don't use ISO booting.

 

Win10 Setup ISO is Not installed, but is simply copied to NTFS Drive (can be internal harddisk or second / third partition of portable USB-harddisk - advised for this purpose).

All Windows Setup ISO's can be used by WinNTSetup3 as described http://www.msfn.org/...nntsetup-v3853/

 

 

If I intend build a drive booting on both BIOS and UEFI systems to :

-Ubuntu ISO

-Parted Magic (and eventually other Linux-based ISOs)

-Hirens BootCD 15.2

-UBCD 5.3.5

-Paragon recovery ISO based on Win10PE

-Macrium Reflect ISO based on Win8PE

 

Where all the ISO's (except Win81SE) should be defined?

Does UEFI_MULTI give another option except grub4dos?

 

 

Grub4dos booting is not compatible with UEFI

In case of 8PE and 10PE it is better to use the WIM file for booting from BootManager Menu in BIOS and UEFI.

Grub2 can be used for booting Ubuntu and PartedMagic in UEFI http://reboot.pro/to...ve/#entry168079

UBCD 5.3.5 can be booted in BIOS grub4dos menu as ISO (copied by UEFI_MULTI to USB boot drive).



#82 Camiel

Camiel

    Newbie

  • Members
  • 14 posts

Posted 26 December 2015 - 07:20 AM

getting this error 

AutoIt Error

Line 7209  (File "G:\Deposit\Win_Uefi_Multi\UEFI_MULTI.exe"):
Error: Subscript used with non-Array variable.

https://imgur.com/Y2gJmrJ

 

using win7 x64 sp1

with various settings, same error

https://imgur.com/Y77X1pA

 







Also tagged with one or more of these keywords: grub4dos, vhd, win8, multiboot, usb, uefi

3 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users


    Google (1)