IFL without boot disk (Windows) - Destroys UEFI boot entry?
Posted: Tue Jun 07, 2022 8:10 am
Hi,
I'm using this how to: https://www.terabyteunlimited.com/de/ho ... -bootfile/
and downloaded the latest ifl_setup.zip from it
Using: TBOSDTS 2.10 Pro
IFL no net 3.52 (created a registered .iso with it)
I've used this procedure for my PC since years...
Now I've assembled a new one (Intel B660 MSI Mainboard, i5-12400, etc.)
Installed Windows 10. Everything runs fine so far.
Prepared a no net IFL USB stick, booted from it, made a backup of the first SSD (where the OS resides) and stored the file on the second SSD.
Both SSDs are the same (WD_BLACK SN770 NVMe 500 GB)
Backuping and restoring are working fine when using this no net IFL USB stick.
I've now used the setupifl.bat method to be able to just invoke the whole procedure by a single command from inside the OS.
No error messages from it but when I invoke the run_ifl.bat
IFL will never be started after the reset but instead (there are no other boot devices attached) the system goes into the BIOS screen
The reason is: The UEFI entry that was present before (which started Windows 10), doesn't exist anymore!
F11 is the hotkey to get the boot menu after a reset and when I use it with the IFL USB stick attached the USB stick is the only entry in the UEFI menu.
Restoring the image via the IFL USB stick will bring everything back to normal (glad that I did make a manual backup via IFL before)...
Fast Startup is disabled on Windows 10...
Any ideas at all, why the bootfile.exe call to the .bin file in the run_ifl.bat seems to remove / destroy the UEFI boot entry?
I'm using this how to: https://www.terabyteunlimited.com/de/ho ... -bootfile/
and downloaded the latest ifl_setup.zip from it
Using: TBOSDTS 2.10 Pro
IFL no net 3.52 (created a registered .iso with it)
I've used this procedure for my PC since years...
Now I've assembled a new one (Intel B660 MSI Mainboard, i5-12400, etc.)
Installed Windows 10. Everything runs fine so far.
Prepared a no net IFL USB stick, booted from it, made a backup of the first SSD (where the OS resides) and stored the file on the second SSD.
Both SSDs are the same (WD_BLACK SN770 NVMe 500 GB)
Backuping and restoring are working fine when using this no net IFL USB stick.
I've now used the setupifl.bat method to be able to just invoke the whole procedure by a single command from inside the OS.
No error messages from it but when I invoke the run_ifl.bat
IFL will never be started after the reset but instead (there are no other boot devices attached) the system goes into the BIOS screen
The reason is: The UEFI entry that was present before (which started Windows 10), doesn't exist anymore!
F11 is the hotkey to get the boot menu after a reset and when I use it with the IFL USB stick attached the USB stick is the only entry in the UEFI menu.
Restoring the image via the IFL USB stick will bring everything back to normal (glad that I did make a manual backup via IFL before)...
Fast Startup is disabled on Windows 10...
Any ideas at all, why the bootfile.exe call to the .bin file in the run_ifl.bat seems to remove / destroy the UEFI boot entry?