Rebuild TBWinRE Utility

[bbearren]

When using the "Create/Update TBWinRE WIM used for Reboot" option of the Utilities, it updates fine, but when rebooting into TBWinRE, it asks for credentials. If I use the tbwinre.cmd in an elevated Command Prompt, it updates and no longer asks for credentials when booting into TBWinRE. I was expecting a fix in 4.02, but that didn't happen.

[TeraByte Support(PP)]

Do you know which Builder version created the previous TBWinRE build? For example, the previous build was created with Builder v1.38 (using IFW V3 license) and the new build was created with v1.40 (using IFW V4 license).

I assume by "rebooting into TBWinRE" you mean that it was a normal boot into WinRE and not a reboot from IFW and that you're using the IFW WinRE build type (not IFW BootWIM).

A build modifying the installed WinRE with the TBWinRE.cmd script would be similar to doing the same build type in Builder. Did you try that before doing the script build? That would be the recommended method since it handles more things.

[bbearren]

The IFW home screen has a "Utilities" button. Click that button, and one of the options is "Create/Update TBWinRE WIM used for Reboot". I used this in v4.01 to update to v4.02. While it did rebuild TBWinRE, when I use Advanced startup in Settings > Windows Update and boot into the Windows Recovery Environment with IFW, I am asked for the IFW credentials before being able to use IFW.

I boot back into Windows, open an elevated Command Prompt, navigate to H:\Program Files\TeraByte Drive Image\tbwinre\TBWinRE.cmd and run it, selecting the "Rebuild" option, it updates TBWinRE without asking for credentials. In other words, the Utility for updating directly from IFW asks for credentials when launched, updating using TBWinRE.cmd incorporates IFW into the Windows Recovery Environment without asking for credentials, and works just fine.

Will this bug be fixed in an upcoming version release? It has not happened before v4.00. I had the same issue when attempting to update from v4.00 to v4.01.

[TeraByte Support(PP)]

Thanks for the additional information. I'll run some tests and see if anything shows up.

Since you're seeing this on multiple updates that are 4.x to 4.x, have you verified that the V4 license used by Builder is correct? The license is saved in the TBWinPE.ini file, [License] section, Name-V4 & Key-V4 values. For example:

Code: Select all

[License]
Name-V4=
Key-V4=

If unsure, you could delete them and save the file and it will re-import on the next run. TBWinPE.ini can be opened from Builder's Settings, General tab, "Edit TBWinPE.ini" link at bottom (note that saving changes may be blocked due to permissions if the file is opened directly from Windows File Explorer).

[bbearren]

I checked the LicenseV4.ini file, and it has the correct license key and user. I also noted that the LicenseV3.ini file was also in the folder. Could that, in some way, be contributing to the issue?

[TeraByte Support(PP)]

The LicenseV4.ini and LicenseV3.ini files are used by the TBWinRE.cmd script. The license used by Builder is in the TBWinPE.ini file (as shown in the previous post).

In testing, a license import issue was found when only command line (unattended) builds were being created. This has been fixed in the next version. This may be what was causing your issue, but it could also be that the saved license is invalid.