Jump to content











Photo
- - - - -

Multiboot on Windows 10 install media


  • Please log in to reply
9 replies to this topic

#1 Franz Ferdinand II.

Franz Ferdinand II.

    Newbie

  • Members
  • 24 posts
  •  
    Macedonia

Posted 11 April 2021 - 01:52 PM

Hello, I have a quick question. I have writtten W10 install ISO to flash drive. It boots well as standalone install media, but I want to add several live recoveries. I have copied all respective .WIM images to the flashdrive, then located Microsoft boot configs at

 

\boot\bcd
\efi\microsoft\boot\bcd

 

and added all WIMs as other boot options to both.

Also I updated the boot menu to not use metro and always wait 30s for user input. These settings should result in showing DOS boot menu before the core loads, but surprisingly the media continues to boot to install UI without any interaction. Is the menu blocked in install image, or did I make the edits to wrong places?



#2 wimb

wimb

    Platinum Member

  • Developer
  • 3756 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 12 April 2021 - 09:29 AM

You need to modify BCD entry as to have BootMenuPolicy value Legacy instead of Standard

 

You can use BOOTICE to Edit BCD in Professional mode and Add New element BootMenuPolicy with value Legacy

 

Or you can use UEFI_MULTI - Add Boot Image 10XPE WIM file so that BootMenuPolicy gets value Legacy

 

You can boot to PE WIM files this way for booting from RAMDISK, but you cannot boot your install.wim files this way.

 

Your WIM files are of type install.wim and not PE boot.wim

 

Your WIM files can be used by WinNTSetup Or VHD_WIMBOOT Offline to Install WIM



#3 Franz Ferdinand II.

Franz Ferdinand II.

    Newbie

  • Members
  • 24 posts
  •  
    Macedonia

Posted 12 April 2021 - 01:43 PM

That worked, thanks The effective bootstore for installation media is at \efi\microsoft\boot\bcd, used bcdedit to change boot menu policy for all added entries ((to quickly add the entries I firstly used EasyBCD which probably didn't register them properly).

 

The menu now appears as expected, but it disclosed another problem. If booting to any of custom environments, the system halts as soon as the Loading files... progress bars reaches end. As the system crash identified by VirtualBox booting from this flashdrive (he default Install Windows choice still loads successfully to UI after altering the bootstore).

 

The bcd entry for my recovery now is

 

Windows Boot Loader
-------------------
identifier              {8f3a5b10-9af9-11eb-893d-54bef771218b}
device                  ramdisk=[boot]\boot\Macrium7.wim
path                    \Windows\System32\Boot\winload.exe
description             Macrium System Recovery
locale                  en-US
osdevice                ramdisk=[boot]\boot\Macrium7.wim
systemroot              \Windows
nx                      OptIn
pae                     Default
bootmenupolicy          Legacy
hypervisorlaunchtype    Off
detecthal               Yes
winpe                   Yes
sos                     No
ems                     No

 

When applied the same method for custom WIMs to bootstore on my fixed system volume earlier, all the added WIMs completed the boot process.

It seems to be specific issue for removable media, or it's different boot loader?



#4 wimb

wimb

    Platinum Member

  • Developer
  • 3756 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 12 April 2021 - 01:49 PM

You can boot to PE WIM files this way for booting from RAMDISK, but you cannot boot your install.wim files this way.

 

Your WIM files are of type install.wim and not PE boot.wim

 

Your WIM files can be used by WinNTSetup Or VHD_WIMBOOT Offline to Install WIM

 

Your WIM file is not bootable.

Your WIM file is suitable for Install of Windows



#5 Franz Ferdinand II.

Franz Ferdinand II.

    Newbie

  • Members
  • 24 posts
  •  
    Macedonia

Posted 12 April 2021 - 02:44 PM

I don't believe my WIM isn't bootable at all. The same image is confirmed to boot if registered to system bootstore.

Is there a way to convert install.wim to PE boot.wim?



#6 wimb

wimb

    Platinum Member

  • Developer
  • 3756 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 12 April 2021 - 04:24 PM

I don't believe my WIM isn't bootable at all. The same image is confirmed to boot if registered to system bootstore.

Is there a way to convert install.wim to PE boot.wim?

 

OK.

 

At the end of progress bar your WIM file does not boot.

In that case you are missing probably the needed boot.sdi file and \ or the entry to use that file.

 

Compare the working and non-working BCD entry using BOOTICE Professional mode

 

Your non-working entry is missing the GUID referring to Device objects > Device Options with SdiPath   \Boot\boot.sdi

 

Also your path is wrong. It can be omitted in case of PE and in any case for EFI should be \Windows\System32\winload.efi

 

UEFI_MULTI can make such working entry for booting WIM from RAMDISK

 

Attached File  PE_BCD_entry_2021-04-12_181606.jpg   127.41KB   0 downloads == Attached File  boot.sdi_entry_2021-04-12_181716.jpg   73.09KB   0 downloads



#7 Franz Ferdinand II.

Franz Ferdinand II.

    Newbie

  • Members
  • 24 posts
  •  
    Macedonia

Posted 13 April 2021 - 07:34 AM

Thanks, I reviewed my bootstore entry in BOOTICE, It's SdiPath was linked to [boot]\NST'boot.sdi (I guess left by EasyBCD).

Changed it to \boot\boot.sdi, not booting to UI though.

There may be yet another problem, the flahhdrive was written with UltraISO using UltraISO USB-HDD v2 MBR.

If that may prevent my recovery to load, what should I change it to?



#8 wimb

wimb

    Platinum Member

  • Developer
  • 3756 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 13 April 2021 - 07:50 AM

Thanks, I reviewed my bootstore entry in BOOTICE, It's SdiPath was linked to [boot]\NST'boot.sdi (I guess left by EasyBCD).

Changed it to \boot\boot.sdi, not booting to UI though.

There may be yet another problem, the flahhdrive was written with UltraISO using UltraISO USB-HDD v2 MBR.

If that may prevent my recovery to load, what should I change it to?

 

Please give your BCD entries for WIM file and for boot.sdi file, so that I can see if there is anything wrong.

Please give both the non-working and the working BCD entries.

 

It is unlikely that UltraISO format is the problem, since anyway you can load the WIM file to RAM and see the progress bar is running.

It is only when loaded to RAM that the WIM file does not boot ....

 

I think using UEFI_MULTI to make the BCD entry for booting WIM file from RAMDISK can solve the issue ....

 

Attached File  UEFI_MULTI_10XPE_2021-03-06_134835.jpg   80.37KB   0 downloads

 



#9 Franz Ferdinand II.

Franz Ferdinand II.

    Newbie

  • Members
  • 24 posts
  •  
    Macedonia

Posted 13 April 2021 - 10:34 AM

OK, using UEFI_MULTI I was able to make WIM entry that boots. I don't intend to backtrace what was wrong with the EasyBCD added entries. so far the initial problem is resolved.

By mistake I have checked some of the GRUB related choices in UEFI_MULTI which results to boot GRUB based bootmanager first:

 

Virtual-Box-Windows-10-13-04-2021-11-56-

 

If it already is there, am I able now to also add option for booting to hybrid syslinux image?

https://www.memtest8...mtest86-usb.zip

I was instructed that MS bootmgr isn't able to boot this, but GRUB based bootmanager might do?



#10 wimb

wimb

    Platinum Member

  • Developer
  • 3756 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 13 April 2021 - 11:36 AM

OK, using UEFI_MULTI I was able to make WIM entry that boots. I don't intend to backtrace what was wrong with the EasyBCD added entries. so far the initial problem is resolved.

By mistake I have checked some of the GRUB related choices in UEFI_MULTI which results to boot GRUB based bootmanager first:

 

Virtual-Box-Windows-10-13-04-2021-11-56-

 

If it already is there, am I able now to also add option for booting to hybrid syslinux image?

https://www.memtest8...mtest86-usb.zip

I was instructed that MS bootmgr isn't able to boot this, but GRUB based bootmanager might do?

 

OK

Good to hear that UEFI_MULTI solved your problem and that you can boot now your WIM file from RAMDISK.

 

EFI booting wth memtest86 is already supported - there is file \EFI\memtest86\BOOTX64.efi

You can easily Update the memtest86 directory using the memtest86-usb.zip download V9.0 (Build 2000) from PassMark

 

You need to edit file \grub\grub.cfg and add in the efi entry section the following entry for memtest86

	if [ -e "/efi/memtest86/bootx64.efi" ]; then
	menuentry "memtest86 - /efi/memtest86/bootx64.efi" {
	  chainloader /efi/memtest86/bootx64.efi
	}
	fi
 

Alternatively:

You can in Grub2 menu select Grub2 x64 EFI File Manager of a1ive - /efi/boot/grubfmx64.efi

In a1ive Grub2 File Manager you walk to file  \EFI\memtest86\BOOTX64.efi and launch that file

 

Attached File  13132509.png   336.15KB   0 downloads




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users