Project World => Win10PE SE HomePage => Topic started by: JohnB175 on January 10, 2017, 03:04:48 PM
I've recently moved from Win7PESE with multi-wim to Win10PESE. I added the \downloads\OtherOSY\Multi-WIM\multi-wim - plugin and added my old Win7PESE wims for legacy purposes. I noticed I cannot added the Menu Options on the first screen that comes up which I think is a grub4dos screen. I have to select WIN10PESE and then that brings up another menu where I can select my old wims. When configuring the plugin if I select Grub4dos-menu from the multi-wim plugin it tells me it's only available for Windows7 SP0/SP1. I noticed on my old Win7PESE I have multiple BOOTMGR's in the root of the flash drive (BOOTMGR1, BOOTMGR2, etc.) and in the menu.lst they were listed like this:
title Win7PESE with Acronis Echo
title Win7PE_SE with Acronis 2013
I must be missing something. Any help would be greatly appreciated.
You can only boot multipe Win7PE directly from Grub4DOS.
All higher version can not used these patched bootmgr and therefor all use the same BCD menu.
I've recently moved from Win7PESE with multi-wim to Win10PESE. I added the \downloads\OtherOSY\Multi-WIM\multi-wim - plugin
As a General Rule,
If you do not see a plugin from A project but not other B,
If plugin not available at \Downloads\
plugin not tested or designed for B project.
You can probably do it the reverse way.
Starting from Win7pese to add then win10pe wims files.
Or you should be able to do it manually by copying yours patched win7 (6.1.7601) BOOTMGR1,2,.. in your Win10PESE build
and also BC1,2 (copied from win7 or maybe just win10 BCD renamed).
It should allow to mix between win10 EFI and windows 7 bootmgr
To test, Let us know :thumbsup:
ChrisR, I did exactly what you suggested and it worked for Grub4DOS. On another note, under OtherOSY\Multi-WIM if I picked WinBCD-Menu rather than Gru4DOS-Menu and build the project, it doesn't give me any time to select the from the BCD menu. I even changed the timeout to 15 seconds under Multi-WIM but it just immediately starts booting Win10PESE. Is there something I am missing? Thanks again for all the help.
Can you check if you have bootmenupolicy legacy writen in BCD
bcdedit /store xxx\Target\Win10PESE\Boot\bcd
bcdedit /store xxx\Target\Win10PESE\efi\microsoft\boot\bcd