@tom-elliott said in Windows Embedded Standard 7 - Lost Bcedit Settings:
Create a post download script.
OK,
but in this case is not sufficient " export " and "import "the BCD Configuration ? "
https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/bcdedit-command-line-options ?
Hi,
I noted that after the backup of WES7 image, fog reset the bcdedit settings to default and EWF function of WES7 does not works fine, because after power loss failure the system restarts and Windows show the recover boot menu !
I noted that after backup a WES7 System with Fog, it’s necessary restore the BCDedit to “IgnoreShhutdownFailures” manually and configure the EWF with ewfcfg.exe command.
How I can solve this problem ?
I need tha Fog does not change the BcdEdit when saves the image !
With other software ( ghost, clonezilla etc… ), it’s necessary insert only EwfCFg.exe command into OneTimeStartup RegKey and EWF it will setted correctly.
Fog makes a change into BCD Settings !
Regards
the chipset is:
RTL8111H
with the UEFI start fog works correctly,
the problem is present only Boot Legacy
Hi I have problem with boot process with only Realtek LAN Client
Pxe initialising devices … OK
No configuring methods succedded !
It’s possible edit or change fog server to try other kernel ?
with all LAN Intel I have not problem, this is the first time !
Note: if change the Bios setting to only UEFI mode, IPXE starts correctly with GBE Realtek.
I have this problem with Legacy mode only.
Regards
Hi,
finally i start winpe 10 x64 iso image with wimboot into vmware machine and work fine with
legacy bios.
I have a problem with the vmware is set with UEFI Bios…
the start process works fine but when the wimboot has loaded and patched all files, the vmware machine restarts…
I tried the boot with a real pc and the boot end the start process corretly ( reboot the second time and starts winpe ).
There are the difference with VM Machine ?
I noted with winpe10 x64 after the boot process does not have the IP address correct ( 192.168.1.x 255.255.255.0 192.168.1.1 ) , but has a diffrent IP 256.218.111.x 255.255.0.0 )
Hi,
could you indicate how extract win10 64bit files to exec with wimboot the same start but
into UEFI BIOS ?
i tried all the steps but the systems return can’t start,
wimboot load and patch all files but when finish display:
read BOOTX64.EFI
load BOOTX64.EFI
could not start BOOTX64.EFI
could not boot BOOTX64.EFI
ok !
thanks a lot ,
it’s a different ISO build ,
I will try rebuild a new iso and test it !
Regards
winpe.iso ( windows 8.1 and 10 ) does not start with machines with UEFI Bios only,
the IPXE and the IPXE menù start correctly with the PC with Bios UEFI , but when I select the iso, after download it starts correctly ,
memdisk work fine but at the next steps return the message " file missing … )
I tried the same ISO deployed with wimboot ( with legacy bios works fine ) files but I have the same error.
it’s necessary rebuild the winpe.iso with internal changes ?
Regards
Hi,
on my systems these methods works with only Legacy BIOS.
Could you indicate how starts the same wimpe systems with pc that have only BIOS Uefi ?
Note: for windows 10 o.s. installed on PC’s with UEFI BIOS the Bios show the option “Windows BootManager option” for start from first HD
Regards
HI,
Could you indicate the correct syntax/steps to create e menu item for start Ubuntu.iso from Fog Server ?
Regards