TeraByte Product Release Thread

Alright, I think I stop here until I hear from TeraByte's support. I don't want to be messing with more files or configurations.

Recap:
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.

That's pretty much it.

 

Interesting, but I don't know what it means.

My TBWinPE.ini has registration data...

Code:

[License]
Name=
Key=
BIBMName=xxx
BIBMKey=yyy
Name-V3=xxx
Key-V3=yyy
BIUName=xxx
BIUKey=yyy
Name-V4=xxx
Key-V4=yyy

The first 2 lines have no data. This is the TBWinPE.ini that is used in my D:\drive to make a TBWinRE UFD. I copy the UFD partition to a SSD and I can boot this partition with BIU. The original TBWinPE.ini in the C:\ drive is 2 years old. "C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\tbwinre" Not used. I would have copied it to the D:\ drive 2 years ago but I didn't edit the file. I didn't add the registration info. Here is the relevant section of the 2 years old file.

Code:

[License]
Name=
Key=
BIBMName=
BIBMKey=
Name-V3=xxx
Key-V3=yyy

The first 4 lines have no data.

For what it's worth, you are booting the RE partition and I'm booting a UFD.

 

Of course, I've always been writing about that. Fwiw I've never mentioned I'm using a UFD.

 

I just used this folder, "C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\tbwinre" to make a UFD. This is a different computer.

TBWinPE.ini was 2.5 years old.

Code:

[License]
Name=
Key=
BIBMName=
BIBMKey=
Name-V3=
Key-V3=

During the build I was asked for BIU and BIBM rego but the IFW v4.00 rego field was filled in automatically. Not by me.

Before restarting I checked TBWinPE.ini in that folder. It had today's date and the rego data was...

Code:

[License]
Name=
Key=
BIBMName=xxx
BIBMKey=yyy
Name-V3=
Key-V3=
BIUName=xxx
BIUKey=yyy
Name-V4=xxx
Key-V4=yyy

TBWinRE UFD was booted and IFW was registered. This is certainly weird.

 

My bad assumption as I only use a UFD.

 

I just used Create/Update TBWinRE WIM used for Reboot. The OS partition was restored. No problems. Rego information wasn't requested.

 

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?

 

I thought of doing that yesterday. Unfortunately, you will need the original Microsoft winre.wim. Do you have an image of the RE partition prior to the first TBWinRE build? If not, just uninstall and reinstall TeraByte Drive Image Backup and Restore Suite. Then try a rebuild and create a UFD.

 

This license stuff for version 4 is getting confusing.

I just noticed that TBWinPE.ini located in:
%ProgramFiles(x86)%\TeraByte Drive Image Backup and Restore Suite\tbwinre
has both V3 and V4 licenses. Should I remove the old V3 licenses? The BIUKey is also the old V3 one and BIBMKey is empty.

[License]
Name=
Key=
BIBMName=
BIBMKey=
Name-V3=xxxxx xxxxx
Key-V3=xxxx-xxxx-xxxx-xxxx-xxxx-xxxx
BIUName=xxxxx xxxxx
BIUKey=xxxx-xxxx-xxxx-xxxx-xxxx-xxxx
Name-V4=xxxxx xxxxx
Key-V4=xxxx-xxxx-xxxx-xxxx-xxxx-xxxx

 

I've left all my old numbers in place. For you, I'd enter BIBM and correct BIU numbers.

My BIBM are the old numbers, but it works.

 

I assume that the BootIt Collection Key still works in both BIBM and BIU fields.

I've just been thinking that maybe Drive Image Suite looks for the V3 key if I've upgraded. I don't know how that would work if I had done a clean installation.

Do you know what the top two blank lines are?
Name=
Key=

 

Alright, the following steps given by TeraByte's Support solved my problem.

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.

https://www.terabyteunlimited.com/ucf/viewtopic.php?p=23596#p23596

Now IFW run from RE does not ask for Name/Key.

Btw, now those ini files, fiw.ini and ifw_IFWWinRE.ini located in X:\Program Files\TeraByte Drive Image Backup and Restore Suite\ are both identical in their contents:

Code:

[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=Name
ProductKey=AAAA-BBBB-CCCC-DDDD-EEEE-FFFF
KeyVer=4

Thanks @Brian K @n8chavez for your kind help.

 

My TBWinRE build has the following in my TBWinPE.ini license section, which is different to what's in the TBWinPE.ini in: %ProgramFiles(x86)%\TeraByte Drive Image Backup and Restore Suite\tbwinre

[License]
Name=
Key=
BIBMName=
BIBMKey=
Name-V3=xxxxx xxxxx
Key-V3=xxxx-xxxx-xxxx-xxxx-xxxx-xxxx
Name-V4=xxxxx xxxxx
Key-V4=xxxx-xxxx-xxxx-xxxx-xxxx-xxxx

When I do a build, it must be getting edited.

 

I have encountered another problem since upgrading to v4.00. I get an error trying to unmount the WinPE image when creating a TBWinPE Recovery Environment. I've never seen this before.



This is another additional TBWinPE.ini entry that I didn't have before, but I don't think it's the problem. I tried removing it and building without it, but I get the same result.
[IFWWinRE]
UseIFWBootWIM=0
AddInstalledDrivers=1

Another thought could be that I upgraded to Windows 11 version 24H2 build 26100.712 Windows Insider Release Preview.

 

Hadron, regarding your mount error. I see it frequently if I have forgotten to close all Windows Explorer windows. Close them and click Retry.

 

No idea.

 

Mr.X,

That's good news.

 

I don't use File Explorer and haven't done in years. I'm a Directory Opus user. But I looked for anything that may be open causing it, but couldn't find anything. I even tried reboots. I'll look into it again tomorrow. I might even check on a non 24H2 computer.

 

Just close all apps while the build is proceeding. Let me know the outcome.

I always get the error if the folder isn't closed.

 

I'm sure is Directory Opus which its handlers accessing the drive interfere with the process. I've seen this behavior with other file explorers, with the exception of Explorer++. Just close all instances.

 

Interesting. I just tried Explorer++ with the TBWinRE build. There was no error with Explorer++ still open.

 

Yeah great software Explorer++

 

One thing I noticed in Explorer++ when run in TBWinRE. It can't read .txt files. Can you read them?

 

Do you mean double click to open them and read the contents?
If so, do you get this error? "An attempt was made to reference a token that does not exist"

 

Yes.