If you dont find bootx64.efi, you can use bootmgfw.efi which is in install.wim on your dvd (sources folder). Use 7zip to extract this file from the wim file and rename it to bootx64.efi
2/Files you need in your tftp root
-get in your tftp root put bootx64.efi (from 1) -create a SOURCES folder put boot.wim in there (from 5) -create a BOOT folder put boot.sdi in there (from 3) put bcd in there (from 2) / applies for Win8 -create a EFI/MICROSOFT/BOOT folder put bcd in there (from 2) / applies for Win7 put the FONT folder in there (from 4)
You should end up with the following : =>ROOT -bootx64.efi ==>SOURCES ==boot.wim ==>BOOT ==boot.sdi ==bcd (for win8) ==>EFI/MICROSOFT/BOOT ==bcd (for win7) ===>FONTS ===*.ttf
3/Things you need to do on your boot.wim
Add the following winpeshl.ini (create it with notepad) file in your boot.wim (system32), making it a « cheap » winpe.
To modify your boot.wim, you can either mount/change/commit it with DISM (from the command line), or with CloneDisk or else modify it with wimlib : wimlib-imagex update boot.wim 1 --command="add CustomWinpeshl.ini \Windows\System32\winpeshl.ini"
The UEFI + PXE boot process will be the following : –pxe->bootx64.efi (from windows install dvd)->bcd (pointing to winload.efi)->boot.wim (x64 only)
as opposed to a legacy bios computer : –pxe->pxeboot.n12 (from windows install dvd)-> bootmgr.exe -> bcd (pointing to winload.exe) -> boot.wim
Site note : you can use option dhcp 252 to decide which BCD file to load. Can be handy when you want to switch from a UEFI computer to a legacy BIOS computer : efi\microsoft\boot or boot\bcd
side note : you can check if you booted on uefi with the following reg query HKLM\System\CurrentControlSet\Control /v PEFirmwareType Will output 0x1 for bios, 0x2 for uefi.
Cheers, Erwan
Note that the following would aso work : PXE-> IPXE.efi ->MS Bootx64.efi ->BCD (winload.efi) ->Boot.wim (x64).
Ipxe script #!ipxe #change with you dhcp or proxydhcp server set next-server 192.168.1.11 set filename boot/x64/bootmgfw.efi chain tftp://${next-server}/${filename}
And changes to apply to your BCD : bcdedit.exe /store my.bcd /set {bootmgr} nointegritychecks yes
Мы используем файлы cookie на нашем веб-сайте, запоминая ваши предпочтения и повторные посещения. Нажимая «Принять», вы соглашаетесь на использование ВСЕХ файлов cookie.
This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
cookielawinfo-checbox-analytics
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checbox-functional
11 months
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checbox-others
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-necessary
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-performance
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
viewed_cookie_policy
11 months
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Апр 4 2017
Boot WINPE over PXE on a UEFI computer
Here below some drafts notes on how to boot WINPE on a UEFI computers.
взято тут
1/Files you need from your windows x64 dvd
-\efi\boot\bootx64.efi file (1)
-\efi\boot\bcd file (2)
-\efi\boot\boot.sdi file (3)
-\efi\microsoft\boot\fonts folder (4)
-\sources\boot.wim (5)
If you dont find bootx64.efi, you can use bootmgfw.efi which is in install.wim on your dvd (sources folder).
Use 7zip to extract this file from the wim file and rename it to bootx64.efi
2/Files you need in your tftp root
-get in your tftp root
put bootx64.efi (from 1)
-create a SOURCES folder
put boot.wim in there (from 5)
-create a BOOT folder
put boot.sdi in there (from 3)
put bcd in there (from 2) / applies for Win8
-create a EFI/MICROSOFT/BOOT folder
put bcd in there (from 2) / applies for Win7
put the FONT folder in there (from 4)
You should end up with the following :
=>ROOT
-bootx64.efi
==>SOURCES
==boot.wim
==>BOOT
==boot.sdi
==bcd (for win8)
==>EFI/MICROSOFT/BOOT
==bcd (for win7)
===>FONTS
===*.ttf
3/Things you need to do on your boot.wim
Add the following winpeshl.ini (create it with notepad) file in your boot.wim (system32), making it a « cheap » winpe.
To modify your boot.wim, you can either mount/change/commit it with DISM (from the command line), or with CloneDisk or else modify it with wimlib :
wimlib-imagex update boot.wim 1 --command="add CustomWinpeshl.ini \Windows\System32\winpeshl.ini"
[LaunchApps] %SYSTEMDRIVE%\Windows\system32\startnet.cmd
%SYSTEMDRIVE%\windows\system32\cmd.exe
4/Things you need to do in your PXE Server :
Set bootx64.efi as the bootp filename.
The UEFI + PXE boot process will be the following :
–pxe->bootx64.efi (from windows install dvd)->bcd (pointing to winload.efi)->boot.wim (x64 only)
as opposed to a legacy bios computer :
–pxe->pxeboot.n12 (from windows install dvd)-> bootmgr.exe -> bcd (pointing to winload.exe) -> boot.wim
Site note : you can use option dhcp 252 to decide which BCD file to load.
Can be handy when you want to switch from a UEFI computer to a legacy BIOS computer : efi\microsoft\boot or boot\bcd
side note : you can check if you booted on uefi with the following
reg query HKLM\System\CurrentControlSet\Control /v PEFirmwareType
Will output 0x1 for bios, 0x2 for uefi.Cheers,
Erwan
Note that the following would aso work : PXE-> IPXE.efi ->MS Bootx64.efi ->BCD (winload.efi) ->Boot.wim (x64).
Ipxe script
#!ipxe
#change with you dhcp or proxydhcp server
set next-server 192.168.1.11
set filename boot/x64/bootmgfw.efi
chain tftp://${next-server}/${filename}
And changes to apply to your BCD :
bcdedit.exe /store my.bcd /set {bootmgr} nointegritychecks yes
Поделиться:
By serg • uefi 0