Windows 8 and 8.1 Forums


Windows PE 5.x boot problem

  1. #11


    Posts : 2,690
    Windows 3.1 > Windows 10


    Yes using ADK you can create bootable WinPE media - to boot either UEFI or BIOS..
    You created a dual boot PE using both the 32bit and 64Bit boot.wim(s)

    You added a second Boot.wim to your winpe... HOW??

    Better yet - just create a x86 winpe version and a x64 winpe version - your problem solved..

      My System SpecsSystem Spec

  2. #12


    My complete procedure is:

    Code:
    md "<Windows_PE_Path>"
    md "<Windows_PE_Path>\x32-x64\Media"
    md "<Windows_PE_Path>\ISO"
    copype x86 "<Windows_PE_Path>\x32"
    copype amd64 "<Windows_PE_Path>\x64"
    MakeWinPEMedia /ISO "<Windows_PE_Path>\x32" "<Windows_PE_Path>\ISO\Windows_PE_x32.iso"
    MakeWinPEMedia /ISO "<Windows_PE_Path>\x64" "<Windows_PE_Path>\ISO\Windows_PE_x64.iso"
    robocopy "<Windows_PE_Path>\x32\fwfiles" "<Windows_PE_Path>\Boot_files"
    rd "<Windows_PE_Path>\x32" /s /q
    rd "<Windows_PE_Path>\x64" /s /q
    powershell Mount-DiskImage -ImagePath "<Windows_PE_Path>\ISO\Windows_PE_x32.iso"
    powershell Get-DiskImage -ImagePath "<Windows_PE_Path>\ISO\Windows_PE_x32.iso" ^| Get-Volume
    robocopy <Drive_Letter>:\ "<Windows_PE_Path>\x32-x64\Media" /e /a-:R
    powershell Dismount-DiskImage -ImagePath "<Windows_PE_Path>\ISO\Windows_PE_x32.iso"
    ren "<Windows_PE_Path>\x32-x64\Media\sources\boot.wim" boot_x32.wim
    powershell Mount-DiskImage -ImagePath "<Windows_PE_Path>\ISO\Windows_PE_x64.iso"
    powershell Get-DiskImage -ImagePath "<Windows_PE_Path>\ISO\Windows_PE_x64.iso" ^| Get-Volume
    robocopy "<Drive_Letter>:\sources" "<Windows_PE_Path>\x32-x64\Media\sources" boot.wim
    powershell Dismount-DiskImage -ImagePath "<Windows_PE_Path>\ISO\Windows_PE_x64.iso"
    ren "<Windows_PE_Path>\x32-x64\Media\sources\boot.wim" boot_x64.wim
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set {default} description "<Windows_PE_x32_name>"
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /copy {default} /d "Windows_PE_x64_name>"
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /v
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set <Windows_PE_x32_ID> device ramdisk=[boot]\sources\boot_x32.wim,<Windows_PE_x32_ID>
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set <Windows_PE_x32_ID> osdevice ramdisk=[boot]\sources\boot_x32.wim,<Windows_PE_x32_ID>
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set <Windows_PE_x64_ID> device ramdisk=[boot]\sources\boot_x64.wim,<Windows_PE_x32_ID>
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set <Windows_PE_x64_ID> osdevice ramdisk=[boot]\sources\boot_x64.wim,<Windows_PE_x32_ID>
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set {bootmgr} displaybootmenu true
    robocopy "<Windows_PE_Path>\Boot_files" "<Windows_PE_Path>\x32-64\fwfile"
    MakeWinPEMedia /iso "<Windows_PE_Path>\x32-x64" "<Windows_PE_Path>\ISO\Windows_PE_x32-x64.iso"
    isoburn /Q <Drive_Letter>: "<Windows_PE_Path>\ISO\Windows_PE_x32-x64.iso"
    Where am I wrong?

    Thanks

    Bye
      My System SpecsSystem Spec

  3. #13


    Posts : 5,360
    7/8/ubuntu/Linux Deepin


    Code:
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set <Windows_PE_x32_ID> device ramdisk=[boot]\sources\boot_x32.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set <Windows_PE_x32_ID> osdevice ramdisk=[boot]\sources\boot_x32.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set <Windows_PE_x64_ID> device ramdisk=[boot]\sources\boot_x64.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set <Windows_PE_x64_ID> osdevice ramdisk=[boot]\sources\boot_x64.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
      My System SpecsSystem Spec

  4. #14


    Posts : 2,690
    Windows 3.1 > Windows 10


    Quote Originally Posted by SIW2 View Post
    Code:
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set <Windows_PE_x32_ID> device ramdisk=[boot]\sources\boot_x32.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set <Windows_PE_x32_ID> osdevice ramdisk=[boot]\sources\boot_x32.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set <Windows_PE_x64_ID> device ramdisk=[boot]\sources\boot_x64.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set <Windows_PE_x64_ID> osdevice ramdisk=[boot]\sources\boot_x64.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
    Does he not also have to add the BCD entries into the EFI BCD ??
    As the BCD store he is working with is used only for legacy boot.. So he also needs to add the EFI BCD Store entries

    Code:
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\efi\microsoft\boot\bcd" /set {default} description "<Windows_PE_x32_name>"
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\efi\microsoft\boot\bcd" /copy {default} /d "Windows_PE_x64_name>"
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\efi\microsoft\boot\bcd" /v
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\efi\microsoft\boot\bcd" /set <Windows_PE_x32_ID> device ramdisk=[boot]\sources\boot_x32.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\efi\microsoft\boot\bcd" /set <Windows_PE_x32_ID> osdevice ramdisk=[boot]\sources\boot_x32.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\efi\microsoft\boot\bcd" /set <Windows_PE_x64_ID> device ramdisk=[boot]\sources\boot_x64.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\efi\microsoft\boot\bcd" /set <Windows_PE_x64_ID> osdevice ramdisk=[boot]\sources\boot_x64.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\efi\microsoft\boot\bcd" /set {bootmgr} displaybootmenu true
      My System SpecsSystem Spec

  5. #15


    If I modify the two files bcd in this way:

    Code:
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set {default} description "<Windows_PE_x32_name>"
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /copy {default} /d "Windows_PE_x64_name>"
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /v
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set <Windows_PE_x32_ID> device "ramdisk=[boot]\sources\boot_x32.wim,<Windows_PE_x32_ID>"
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set <Windows_PE_x32_ID> osdevice "ramdisk=[boot]\sources\boot_x32.wim,<Windows_PE_x32_ID>"
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set <Windows_PE_x64_ID> device "ramdisk=[boot]\sources\boot_x64.wim,<Windows_PE_x32_ID>"
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set <Windows_PE_x64_ID> osdevice "ramdisk=[boot]\sources\boot_x64.wim,<Windows_PE_x32_ID>"
    bcdedit /store "<Windows_PE_Path>\x32-x64\Media\Boot\BCD" /set {bootmgr} displaybootmenu true
    bcdedit /store <Windows_PE_Path>\x32-x64\Media\efi\microsoft\boot\bcd /set {default} description "<Windows_PE_x32_name>"
    bcdedit /store <Windows_PE_Path>\x32-x64\Media\efi\microsoft\boot\bcd /copy {default} /d "Windows_PE_x64_name>"
    bcdedit /store <Windows_PE_Path>\x32-x64\Media\efi\microsoft\boot\bcd /v
    bcdedit /store <Windows_PE_Path>\x32-x64\Media\efi\microsoft\boot\bcd /set <Windows_PE_x32_ID> device "ramdisk=[boot]\sources\boot_x32.wim,<Windows_PE_x32_ID>"
    bcdedit /store <Windows_PE_Path>\x32-x64\Media\efi\microsoft\boot\bcd /set <Windows_PE_x32_ID> osdevice "ramdisk=[boot]\sources\boot_x32.wim,<Windows_PE_x32_ID>"
    bcdedit /store <Windows_PE_Path>\x32-x64\Media\efi\microsoft\boot\bcd /set <Windows_PE_x64_ID> device "ramdisk=[boot]\sources\boot_x64.wim,<Windows_PE_x32_ID>"
    bcdedit /store <Windows_PE_Path>\x32-x64\Media\efi\microsoft\boot\bcd /set <Windows_PE_x64_ID> osdevice "ramdisk=[boot]\sources\boot_x64.wim,<Windows_PE_x32_ID>"
    bcdedit /store <Windows_PE_Path>\x32-x64\Media\efi\microsoft\boot\bcd /set {bootmgr} displaybootmenu true
    I would not have problems to boot the CD from any computer. Right?
      My System SpecsSystem Spec

  6. #16


    Posts : 2,690
    Windows 3.1 > Windows 10


    Add Quotes " " to the efi command lines..

    But I am pretty sure that will modify both the Bootmgr and Bootmgr.efi files..

    the only other issue you may need to adjust for is within this folder > EFI\BOOT
    Attachment 61227
      My System SpecsSystem Spec

  7. #17


    Quote Originally Posted by KYHI View Post

    But I am pretty sure that will modify both the Bootmgr and Bootmgr.efi files.
    Sorry, but if I run the above procedure, the Bootmgr and Bootmgr.efi files are changed automatically or not? If not, how do I change them?

    Thanks

    Bye
      My System SpecsSystem Spec

  8. #18


    Posts : 2,690
    Windows 3.1 > Windows 10


    They are changed by your command line process.. If your coding and files are correct - the entries should be correct..

    You are booting x86 and x64 in two different formats Legacy and EFI = 4 total BCD entries
      My System SpecsSystem Spec

  9. #19


    Since the <Windows_PE_Path>\x32-x64\Media\Boot\BCD and <Windows_PE_Path>\x32-x64\Media\EFI\microsoft\boot\BCD files seem to be identical, once I changed appropriately the first file, I could use the command robocopy to copy the first file on the second?

    Thanks

    Bye
      My System SpecsSystem Spec

  10. #20


    Posts : 2,690
    Windows 3.1 > Windows 10


    NO.. the BCD's refer to different files..

    Legacy BCD
    Code:
    Windows Boot Manager
    --------------------
    identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
    description             Windows Boot Manager
    locale                  en-US
    inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
    default                 {7619dcc9-fafe-11d9-b411-000476eba25f}
    displayorder            {7619dcc9-fafe-11d9-b411-000476eba25f}
                            {7f1c81f8-f40d-11e4-8302-0c8bfd4c841a}
    toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}
    timeout                 30
    displaybootmenu         Yes
    
    Windows Boot Loader
    -------------------
    identifier              {7619dcc9-fafe-11d9-b411-000476eba25f}
    device                  ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
    path                    \windows\system32\boot\winload.exe
    description             WinPE x32
    locale                  en-US
    inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    osdevice                ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
    systemroot              \windows
    bootmenupolicy          Standard
    detecthal               Yes
    winpe                   Yes
    ems                     No
    
    Windows Boot Loader
    -------------------
    identifier              {7f1c81f8-f40d-11e4-8302-0c8bfd4c841a}
    device                  ramdisk=[boot]\sources\bootx64.wim,{7e04c8f8-f40d-11e4-8302-0c8bfd4c841a}
    path                    \Windows\System32\Boot\winload.exe
    description             WinPE x64
    locale                  en-US
    osdevice                ramdisk=[boot]\sources\bootx64.wim,{7e04c8f8-f40d-11e4-8302-0c8bfd4c841a}
    systemroot              \Windows
    detecthal               Yes
    winpe                   Yes
    EFI BCD
    Code:
    Windows Boot Manager
    --------------------
    identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
    description             Windows Boot Manager
    locale                  en-US
    inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
    default                 {7619dcc9-fafe-11d9-b411-000476eba25f}
    displayorder            {7619dcc9-fafe-11d9-b411-000476eba25f}
                            {b7d84287-f40d-11e4-8302-0c8bfd4c841a}
    toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}
    timeout                 30
    displaybootmenu         Yes
    
    Windows Boot Loader
    -------------------
    identifier              {7619dcc9-fafe-11d9-b411-000476eba25f}
    device                  ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
    path                    \windows\system32\boot\winload.efi
    description             WinPE x86
    locale                  en-US
    inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    osdevice                ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
    systemroot              \windows
    bootmenupolicy          Standard
    detecthal               Yes
    winpe                   Yes
    ems                     No
    
    Windows Boot Loader
    -------------------
    identifier              {b7d84287-f40d-11e4-8302-0c8bfd4c841a}
    device                  ramdisk=[boot]\sources\bootx64.wim,{b6cf8eed-f40d-11e4-8302-0c8bfd4c841a}
    path                    \Windows\System32\Boot\winload.efi
    description             WinPE x64
    locale                  en-US
    osdevice                ramdisk=[boot]\sources\bootx64.wim,{b6cf8eed-f40d-11e4-8302-0c8bfd4c841a}
    systemroot              \Windows
    detecthal               Yes
    winpe                   Yes
    Last edited by KYHI; 06 May 2015 at 11:41.
      My System SpecsSystem Spec

Page 2 of 6 FirstFirst 1234 ... LastLast
Windows PE 5.x boot problem
Related Threads
Windows boot order problem in Installation & Setup
I have a SSD and a HDD. I installed Windows from a flash drive, so I inserted the flash drive and restarted the computer and entered the BIOS setup. I changed the boot order so Windows would see the flash drive. The OS was successfully installed, and I went back to change the boot order. What I...
I have a very old system but it works perfectly well as a media centre. it is a 64bit system but I realised after I upgraded to windows 8 recently that windows 8 installed as a 32 bit operating system. I have been trying to perform a fresh install of windows 8 64bit but there appears to be a...
Solved Windows 8 boot problem in General Support
Well I'm back again with a problem I can't figure out. Here's my situation... Dual boot system with win 7 and 8 c drive has the MBR (uefi mb but set fully to operate under mbr) with win 7. g drive has windows 8 and boots fine under the win 7 multi-boot menu. There's also a 750MB 2nd partition...
Solved Windows 8 Boot Menu Problem. in Installation & Setup
Not sure where to post this in the forms. If this is the wrong place to submit this thread I sincerely apologize. I had been dual booting Windows 7 and Windows 8 using hard drive partition. I had one for Windows 7 and the other for Windows 8. I have since switched over to windows 8 formatted the...
Windows 8 Boot Problem in Installation & Setup
i decided windows 8 was better and i should delete windows 7(after i backed up important files) but i when i tried to format it without uninstalling windows first(that was dumb) windows 8 didnt boot.I put in the installation disc of win 8 and clicked repair.Now it boots but when i open the...
Hello all, The day the Windows 8 consumer preview came out I installed Windows 8 on a 40GB partition, dual-boot setup with my current Windows 7. Everything was peachy, until Windows 8 started to run slowly and I discovered I'd installed some incompatible programs and drivers. So I used Windows...
Problem with boot in Windows 8 in Installation & Setup
I burned Windows 8 Developer Preview 32bit to CD and created new partition. I installed on new partition and when installation finished, PC restarts and I get this screen: http://pic.mk/images/gnlPM.jpg So, I cant boot in Windows 8 - Windows 7 works great, but 8 ..... :S Any help ? Sorry...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook