IFW v4.00 asking for Name/Key on TBWinRE WIM for Reboot

[Mr.X]

When I did upgrade from 3.64 to 4.00:

1. I ran setup file terabyte_drive_image_backup_and_restore_suite_en_gui_v4.exe then quickly moved forward thru the installer and can't recall if it asked for the new key (I don't inserted the new key).
2. Case "Create/Update TBWinRE WIM used for Reboot " was checked by default and I left it like that.
3. I can't recall if the installer really updated the wim.
4. On Windows, I launched IFW and asked for the new key V4
5. Inserted the new key and now IFW opens without asking.
6. Just for curiosity I restart the machine to enter RE
7. It launched but when I ran IFW it asked for the new key.
8. Again in Windows I rebuilt TBWinRE using IFW utility, despite it said the wim didn't need to be updated.
9. Restarted computer once again to get into RE
10. IFW asked for the new key once again.

That's pretty much it.

Look at this video
https://streamable.com/0ire40



Some extra details I've observed:

There are two ini files in X:\Program Files\TeraByte Drive Image Backup and Restore Suite\

ifw_IFWWinRE.ini

Code: Select all

[OPTIONS]
Simple=0
PHYLockUseReg=0
Bold=0

[PHYLock_OPTIONS]
UseVSS=1

[BACKUP_DEFAULTS]
UseMetaData=1
CreateHash=1
PostValidate=0x3

[RESTORE_DEFAULTS]
PostValidate=0x2
PreValidate=0x1
RFT=1
WriteMBR=1
UseMetaData=1

[LICENSE]
User=First Last
ProductKey=AAAA-BBBB-CCCC-DDDD-EEEE-FFFF
KeyVer=4

and

ifw.ini

Code: Select all

[Options]
Simple=0
PHYLockUseReg=0
[PHYLock_Options]
UseVSS=1

[OldNavyGuy]

Check the license file "LicenseV4.ini" in C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\tbwinre

[Mr.X]

There's no such file there.

[TeraByte Support(PP)]

If you have the option enabled to skip the license step in Builder, disable it and make sure what it has is correct for V4. Otherwise, open the TBWinPE.ini file and verify what it has in the [License] section. If you have used the "Modify the installed WinRE" build in addition to the IFW WinRE (IFW reboot) build, you may need to update that build also. Booting to the normal WinRE is not exactly the same as booting to IFW WinRE mode.

(The LicenseV4.ini file is used by the TBWinRE.cmd script. Builder saves the info it uses in its INI file.)

[TeraByte Support(PP)]

Regarding your #3, you can check Builder's log and see if it built the WIM. It should have aborted due to the missing license.

I would add that when using the "Create/Update TBWinRE WIM used for Reboot" option during the installation, if the license is not provided and is not already saved there is no way to include it in the build. This should only be an issue on the switch from V3 to V4 -- once the license is entered it should be good for later builds.

[Mr.X]

I want to start afresh and install v4. If I uninstall using the provided uninstaller, will everything including RE from TeraByte for reboot will be removed?
Will this procedure fix my issue? I'm working on Windows 11.

[TeraByte Support(PP)]

I don't think there is any reason to uninstall and reinstall, but you can if you want. The existing WinRE will remain as will the files in the install folder unless you select to remove everything. I wouldn't recommend this as you would also lose your WinRE backups.

Did you do a normal "Modify the installed WinRE build"? I think that should fix the license issue with the normal WinRE boots.

The IFW WinRE build is normally only used when booted into directly from IFW. You can test it from the command line, though.

[Mr.X]

Did you do a normal "Modify the installed WinRE build"? I think that should fix the license issue with the normal WinRE boots.

I don't know where's that option. Provide more info please.

[TeraByte Support(PP)]

Run TBWinPE/RE Builder normally:
1. From IFW, click the Utilities menu and select the "Create Image for Windows Boot Media" item.
2. Builder will start and show the Welcome screen. Click Next.
3. Select TBWinRE. Click Next.
4. If the License step is shown, make sure that looks correct and then click Next.
5. Build requirements will be checked.
6. On the next step (Build Type), select the "Modify the installed Windows Recovery Environment (WinRE)" option. Click Next.
7. The Summary screen is shown. Click Next.
8. Click Start to create the build.

[Mr.X]

Yes, those steps above solved my issue. Thanks a lot.