Hello @Brian K, Most definitely. They responded to me in less than an hour and a fix was released in less than 12 hours. It is hard to get any better than that. I am also leaning towards only using BootNow in Windows, for the time being at least. I am not going to try to use BootNow anywhere but Windows as I do not think it is necessary for me. I have Windows also as default in BIU but with a five second delay. I did some imaging testing with the four ways I have available on my system. Background information: 38.5 GB of data to back up from 7 partitions. Encryption is used with "Enhanced Speed - A" All metadata and hash files are also being created for future changes only backups and restores. Final image size is 19.4 GB (plus 263 MB for metadata and hash files equals 19.7 GB total). Results: IFU in BIU: 14:27 IFL partition: 2:04 TBWinRE partition: 5:00 IFW in live Windows: 2:53 My thoughts: IFU in BIU is not going to be used as it is extremely slow. I was very surprised that using the TBWinRE partition was slower than using IFW on a live Windows session. I probably will not use this for imaging (but maybe an occasional restore). That leaves IFW and IFL. I can almost boot into my IFL partition, do an image, and be back in Windows faster than using IFW. It looks like my IFL partition will get the most work. At the moment, I am seriously considering it as my main go to for both backups and restores.
Kent, Interesting numbers and they parallel mine. IFL is the fastest and IFU is the slowest. TeraByte Support told me the IFU speed depends on your "variety" of UEFI. Customized by the MB manufacturer. I use IFL for all my restores.
If anyone desires BootNow in IFL to boot an Item called win10... You have to use the 64-bit IFL version. You need 64-bit IFL in order to access EFI Vars on x64 UEFI. 32-bit Linux can't access UEFI x64. Copy the Linux bootnowu file to the scripts folder Copy this script to the scripts folder
Hello, @Brian K, Thanks for that information. Another post that I will bookmark for probable future use. I have decided to try to implement BootNow as much as possible whether I use it fully in all scenarios or not. That way I have the option in case it is needed.
Hello, @A28lemane: Sorry for the late response but as I am new to BIU, i can not give you a definitive answer. I can tell you, however, the way that I understand it. I think that you need to have a Windows UEFI secure boot system in order to use BIU since BIU installs to the Windows EFI system partition. I could be wrong as during the install process you have the option to install to a different location. Your best choice would be to ask over on the TeraByte Unlimited User Community Forums or to email and ask TeraByte support directly (support(AT) terabyteunlimited(DOT)com). @Brian K: Let's see if I understand this correctly. "Direct Boot" can be used to bypass the default boot screen (in my case by repeatedly pressing F12 when booting) to boot from say a recovery flash drive (like an IFW or IFL rescue/recovery flash drive). Instead of doing the pressing of F12 when booting to get the default boot screen then selecting the flash drive to boot from, I can just click "Direct Boot" on the BIU boot screen...
Hello @Brian K, I assume that getting rid of grub altogether is not possible from web searches that I have done and the fact that you had me hide it instead of removing it. I only ask because grub has updated twice already and each time that it does, I have to re-activate BIU. It is no big deal, just a minor annoyance.
Hello @Brian K, Yes, in the Update Manager (I think that is what it was called as I am not in Mint at the moment). Give me a few minutes and I will check...
Hello @Brian K, On 7/9, the following five grub related packages updated: grub-efi-amd64 2.02-2ubuntu8.1 grub-efi-amd64-bin 2.02-2ubuntu8.1 grub2-common 2.02-2ubuntu8.1 grub-common 2.02-2ubuntu8.1 grub-efi-amd64-signed 1.93.1+2.02-2ubuntu8.1 And on 7/13, the following grub related package updated: grub-efi-amd64-signed 1.93.2+2.02-2ubuntu8.1 On both occasions, I had to re-activate BIU. Although I am not sure what caused me having to re-activate BIU, I assumed that since it happened at the same time that grub updated causing me to boot back to Mint each time (not to the BIU boot screen), that grub was the cause.
I just checked a Cinnamon install that had never been updated and it also showed... grub-install (GRUB) 2.02-2ubuntu8
Hello @Brian K, Mine shows: grub-install (GRUB) 2.02-2ubuntu8.1 The original version before the two updates was: grub-install (GRUB) 2.02-2ubuntu8 The same as yours...
Hello @Brian K, Have you changed your update servers from the default? I remember something about changing them could speed up your downloads. I left mine as whatever the defaults are. That could be the difference...
Kent, Can you try this? In Win10, run TBEXPLO (TeraByte Explorer). If the text is too small, click the icon at the top left of the Title Bar, click Properties and make the Font 20. File Explorer Mount/Unmount a drive path identifier EFI system partition Mount drive without locking press Enter on EFI I have these folders Boot BootIt Microsoft a series of Microsoft.xxx a series of ubuntu.yyy Do you have an ubuntu folder without a number? Just curious.
Hello @Brian K, As far as I know, I have not done anything on the EFI partition... The date on the Dell.001 directory is the date of the last time Dell updated the BIOS/firmware so maybe something to do with that?
Hello @Brian K, No, it is: \EFI\Microsoft.001\Boot\bootmgfw.efi A couple of observations: TBEXPLO shows the directory: Microsoft "BIU > Edit Boot File" shows the directory: Microsoft.001 You can see the discrepancy. The Dell.001 directory contains only one file "Dell.001\BIOS\Recovery\BIOS_CUR.RCV", nothing else... I believe that Dell.001 has to do with updating the BIOS/Firmware and a way to recover to the same or a previous version if the need arises. And a question: In "BIU > Edit Boot File", both Windows and Mint boot the EFI partition while IFL and TBWinRE both boot their own partition. Is this correct?
My brain must be still rocking from the boat. The Microsoft folder is the Windows representative of Microsoft.001. All OK. Yes.
