Image for Linux 3.64 Bootup In Windows 11 (Dell Laptop)

Discussion in 'backup, imaging & disk mgmt' started by TheKid7, Sep 2, 2024.

  1. TheKid7

    TheKid7 Registered Member

    Dell Windows 11 Laptop:

    I tried to boot Image for Linux 3.64 but got some sort of error when Image for Linux tried to load. I then remembered that I need to turn off the Windows Secure Boot option in the BIOS. After turning off the Windows Security Boot option in the BIOS, the Image for Linux Boot disk would not boot. I temporarily gave up and turned back on Security Boot in the BIOS.

    Now I remember that you are supposed to turn off Windows 11 Fast Startup. I have not yet done this.

    What is a list of things that I need to do to be able to safely boot Image for Linux 3.64 on a Dell Windows 11 Laptop?

    Turn off Sleep, Hibernate, etc.

    When would data corruption possibly occur? The manual said something about possible data corruption.

    Is there a possibility of data corruption with what I have done so far?

    Thanks in Advance.
     
  2. Brian K

    Brian K Imaging Specialist

  3. TheKid7

    TheKid7 Registered Member

    Thanks.

    I just purchased the version 4 upgrade and downloaded the IFL version 4.X zip file. It may be several days before I give it a try.

    So is IFL 4.X fully compatible with Windows 11 Secure Boot being turned on?

    If you Only Cold Image the Windows 11 System Partition, do any of those other things in Windows 11 need to be turned off for the correct Imaging to be done without risk of data corruption? Sleep, Hibernate, Fast Boot, etc.

    Thanks in Advance.
     
  4. Brian K

    Brian K Imaging Specialist

    IFL 4.x works fine with with the Secure Boot signatures that were recently changed by Microsoft.

    You should disable Fast Startup to prevent the quasi hibernation that can cause data corruption if you write data to the "hibernated" disk. Ordinary hibernation and Sleep are OK.

    Fast Boot in the BIOS is quite separate from Fast Startup and doesn't cause data corruption. As it only reduces Boot Time by a fraction of a second in my computers, I turn it off too as the Fast Boot can skip some hardware initialization. In one of my computers, one NVMe M.2 drive isn't initialized and isn't seen in Windows if Fast Boot is ON.
     
  5. Brian K

    Brian K Imaging Specialist

    IFL 3.64 will boot if you temporarily disable Secure Boot. It does still work. But temporarily turning Secure Boot off isn't ideal.
     
    Last edited: Sep 2, 2024
  6. TheKid7

    TheKid7 Registered Member

    With or without Secure Boot Disabled IFL 3.64 would not boot. It had the same error in both cases but I forgot to write down the error. Fast Startup/Fast Boot were not turned off.
     
  7. Brian K

    Brian K Imaging Specialist

    I tried IFL 3.64 today in two computers. It booted if Secure boot was disabled.
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice