Well now I'm very confused. After first upgrading windows 10 to version 1607, I found that not only did IFW not function with either phylock or vss but a few oddities of the OS itself were hinky; such as the weather app crashing on launch or Office 365 not remembering my theme choices. So I reimaged using an older backup from June. From there I reupdated to 1607, copying IFW 3.00a to my flash drive. To my surprise everything that did not wrk in my earlier attemp at 1607 now functions perfectly, including IFW w/phylock!! I can't explain why that is though.
An updated version is available which may fix issues some have had with the Anniversary Update: Version 3.00b - August 9, 2016 Update signature on TBIMount and PHYLock drivers to support new installations to Windows 10 (anniversary) versions.
I am trying to create an Image for Windows Recovery Boot Disk with the new IFW 3.0b. I am getting an error telling me that "bootit bm license key not found or appears invalid". I am entering the same key I used to install ver 3.0b. The error will not let me go on. I have 6 licenses. I successfully created a boot disk for one of my desktops, but on my laptop, I am getting the error
I am not wanting to use BIBM. I didn't pay the extra 10$ to purchase it. My purchase was an upgrade since I owned ver 2.99. How can I create the IFW rescue disk without BIBM?
Guys,have a few question: 1) How do I do create IFL boot disk iso from IFW? There's no option for it. It makes a TBWinRE/TBWInPE Disc instead. Using 2.99. 2) Btw, Terabyte is better or Acronis is better? 3) I noticed that if I try to use my Windows based recovery disk for IFW to try to make a backup on a UEFI laptop (already disable UEFI feature. change to legacy etc), the mouse pointer doesn't appear. Even when I tried the touchpad, the mouse pointer does not appear. Only the keyboard works. How do I fix this? Use IFL?
Hi Lunarwolf 1. You can't. You use Makedisk in the IFL directory and create a recovery IFL medium 2. I have both. Personally I feel Terabyte is much better. 3. Just for grins, after you boot up, reboot and then see if the mouse works. It may or may not help but in some situations it's what I have to do.
1. I tried but there's no way for me to input in the IFL license. 3. I was talking about the rescue disk. No mouse pointer when I boot from rescue disk. Same issue like when I tried booting a Win7 ISO via USB to a laptop with Win 10 installed initially.
You can download the Linux gui installer in the downloads page. I have a netbook with windows 10 preinstalled. I have the same issue. I think it is driver related. Mouse pointer and touchpad didn't work in any live boot environment. Finally I had to use external usb mouse.
The new version of TBOSDT is the "Pro for BootIt" version, but it activates with the BIBM key. Without a key it will run in Pro mode (the BootIt features will be unavailable). You can ignore the warning if you don't have a BIBM key or you're not activating it. If you do have a key, you can enter it in Settings or run TBOSDT and enter it using the "Register" command. The warning existed before, but since the "Pro for BootIt" version was a separate product you'd only see it if you included it in the build and left out the key.
I had trouble creating WinRE Recovery Media. I received this message. I fixed it with the help of this TeraByte article. This is what I did to get it to work. Incidentally, Winre.wim is gone again from C:\Windows\System32\Recovery.
It wouldn't enable until I manually moved Winre.wim to C:\Windows\System32\Recovery. And it's now gone again. Is this also normal?
The not enabling part isn't normal (something was broken). If the WIM file is missing then it wouldn't enable (that part's normal). Being gone after it's enabled is normal because it moves the WIM to the installed/enabled location. You can run "reagentc /info" to see the status, though that also sometimes reports incorrect information.
