TBWinRe won't initialize network booting from USB

User discussion and information resource forum for TeraByte Drive Image products, including TBNetManage.
Post Reply
PsychBiller
Posts: 72
Joined: Sun Aug 05, 2012 4:45 pm

TBWinRe won't initialize network booting from USB

Post by PsychBiller »

I installed version 3 of the suite and installed version 4.05. I am attempting to rebuild the bootable USB I use to perform my backups.

I duplicated the \tbwinre directory to C:\tbwinre. I've added a Drivers subfolder as usual. I ran TBWinPE in TBWinRE mode with a few tweaks (nothing exotic).

When I boot from the USB drive, the "initializing network" message stays in the upper left corner for a few minutes. It never did that in version 3. Eventually it goes away after InitScript.cmd begins running. I know the network never intializes because a net use in InitScript.cmd fails.

I think I'm missing something small but obvious.

The following is my TBLauncher.ini file from the \config subfolder:

Code: Select all

; Lines that begin with ; are comments
; Comments must exist entirely on their own lines

[Options]
; Valid modes are: WinRE, WinPE, IFW
; WinRE starts the System Recovery Options program if found, otherwise IFW
; WinPE starts IFW
; IFW starts IFW with the parameters specified by the IFWModeParameters option
Mode=WinPE

; Run WinPE initialization (wpeinit) after booting (0=disabled, 1=enabled)
; If disabled, wpeinit can be run from the File menu
RunWpeinit=0

; Run network initialization after booting (0=disabled, 1=enabled)
; If disabled, network initialization can be run from the File menu
RunNetworkInit=1
RunWiFiInit=1

; Disable Windows firewall. This is required to use multicasting.
; (0=firewall enabled, 1=firewall disabled)
DisableFirewall=0

; Run initialization programs in background (0=disabled, 1=enabled)
BackgroundInit=0

; IFW parameters for IFW mode
IFWModeParameters=

; Searches for the TBWinPE/RE boot media drive after booting (0=disabled, 1=enabled)
; If enabled, TBLauncher will search for the boot media. If found the environment
; variable %TBDrive% will be set to the drive letter. Additionally, if the media
; contains \TBData\TBLauncher.ini it will be used instead of the INI file included
; in the build (%TBDrive% can be used for program paths, if desired). If the media 
; contains \TBData\autorun.cmd it will be run automatically.
FindBootDrive=0

; Specifies the maximum number of seconds (up to 20) to search for the boot drive. 
; Applies only when FindBootDrive is enabled.
MaxSearchTime=8

; Search for updated versions of the TeraByte programs (0=disabled, 1=auto-update, 2=ask user)
; After booting, if option not disabled, TBLauncher will search the specified build paths 
; and default installation paths for the TeraByte programs (IFW, TBIView, TBIMount, TBOSDT). 
; If a newer version is found it will be used instead of the version included in the build 
; (user will be asked first if 2 specified).
; --WARNING-- It is recommended to update the boot media when you update Image for Windows.
; If you rely on this option and the drive containing the updated versions is not accessible 
; (e.g. blank, corrupted, etc.) the search will fail and you may not be able to access your 
; backups using the older version included in the build.
UpdatePrograms=0

; Enables the TBLauncher window to be transparent when closed (inactive).
; Valid values are 0 - 4, with 0 being opaque (default), 1 - 4 increasing transparency.
ClosedTransparency=0

; Creates log file (0=disabled, 1=enabled)
Log=1

; Keeps TBLauncher on top of other windows (0=disabled, 1=enabled)
; Note: It's recommended to leave this option enabled.
AlwaysOnTop=1

; Controls the following accessibility options:
; 0 = No accessibility programs run on startup
; 1 = Run Narrator
; 2 = Run OSK (On-Screen Keyboard)
; 3 = Run both Narrator and OSK
; Note: Narrator is only supported in TBWinRE based on Windows 10 1703 or later.
AccessibilityOpts=0

; Opens TBLauncher when mouse moves over its closed state window (0=disabled, 1=enabled)
; Note: Enabling this option will also enable AlwaysOnTop.
MouseOver=0

; Closes TBLauncher when mouse leaves its open state window (0=disabled, 1=enabled)
; Note: This option only applies when MouseOver is enabled.
MouseLeave=1

; Selects the style of the TBLauncher window
; 0 = Default
; 1 = Small (smaller closed state window)
Style=0
StyleColor=0

[Menu]
; Number of menu items to process. If the program for the item isn't found, the item is ignored.
ItemCount=6

; Maximum number of launch menu items to display.
; Valid values: 6 to 24 (default is 6)
DisplayCount=6

[Menu_Item_1]
Name=Image for Windows
Path=%ProgramFiles%\TeraByte Drive Image Backup and Restore Suite\imagew.exe
WorkingDir=
Parameters=
Icon=0

[Menu_Item_2]
Name=TBI View
Path=%ProgramFiles%\TeraByte Drive Image Backup and Restore Suite\TBIView\tbiview.exe
WorkingDir=
Parameters=
Icon=0

[Menu_Item_3]
Name=TBI Mount
Path=%ProgramFiles%\TeraByte Drive Image Backup and Restore Suite\TBIView\tbimount.exe
WorkingDir=
Parameters=
Icon=0

[Menu_Item_4]
Name=Notepad
Path=%SystemRoot%\System32\notepad.exe
WorkingDir=
Parameters=
Icon=0

[Menu_Item_5]
Name=Command Prompt
Path=%SystemRoot%\System32\cmd.exe
WorkingDir=
Parameters=
Icon=0

[Menu_Item_6]
Name=Task Manager
Path=%SystemRoot%\System32\taskmgr.exe
WorkingDir=
Parameters=
Icon=0
TeraByte Support(PP)
Posts: 1740
Joined: Fri Aug 12, 2011 12:51 am

Re: TBWinRe won't initialize network booting from USB

Post by TeraByte Support(PP) »

Are you using WiFi? If not, you could disable initializing that and see if it helps.

Was your other build including any network drivers? If the option isn't enabled for the build, you could try that (in Builder: Settings | Build Options, Add installed network drivers) and rebuild.
PsychBiller
Posts: 72
Joined: Sun Aug 05, 2012 4:45 pm

Re: TBWinRe won't initialize network booting from USB

Post by PsychBiller »

WiFi isn't initializing either. When I attempt to initialize it after booting from the USB, it fails because no WiFi interface is present.

I have included both Ethernet and WiFi drivers.

I created the USB on one system and am using it on a different one, so I am not including installed drivers.
TeraByte Support(PP)
Posts: 1740
Joined: Fri Aug 12, 2011 12:51 am

Re: TBWinRe won't initialize network booting from USB

Post by TeraByte Support(PP) »

Are the drivers getting added to the build successfully? You can check Builder's log to see if it shows success for them. Note that even if they get added successfully, it doesn't mean they'll actually work when booted.

Are these the same drivers you used before that worked okay? Same Windows versions/architectures? Same WinRE versions/architectures? Different versions may have different drivers included or different support for added drivers. I've seen cases where a specific version works and it's not the installed version.

Is it possible to try a build on the other system?

If you need to test out different drivers, you can try loading them manually after booting. This can be done using TBLauncher (Tools | Load driver...) or drvload from the Command Prompt.
PsychBiller
Posts: 72
Joined: Sun Aug 05, 2012 4:45 pm

Re: TBWinRe won't initialize network booting from USB

Post by PsychBiller »

Yes, the drivers are being added correctly. They are the same drivers that I used with version 3 on the same system. Same Windows 10 version on the building system and the target usage system. Failure occurred on another target system. Build log is below.

I don't know where to find the drivers using the Load driver menu item in TBLauncher.

Code: Select all

2025-06-22 19:05:18 - Program exiting with code 0
2025-06-22 19:05:20 - ---------------------------------------------------------------------------
2025-06-22 19:05:20 - TBWinPE/RE Builder v1.43 [x86,0x2]
2025-06-22 19:05:20 - Initializing
2025-06-22 19:05:20 - Windows version: Windows 10 Pro [10.0.19045.5854 22H2, AMD64]
2025-06-22 19:05:20 - Checking for required build files
2025-06-22 19:05:20 - Initialization complete
2025-06-22 19:05:49 - WIM details (Installed WinRE): \\?\Volume{e1776c5e-4c13-42bb-8a2e-42104e98acdf}\Recovery\WindowsRE\Winre.wim
2025-06-22 19:05:50 -   | WinRE [WIM], Architecture: x64, Version: 10.0.19041, Service Pack: build 5728, level 0
2025-06-22 19:06:08 - Verifying build requirements (TBWinRE)
2025-06-22 19:06:08 - Image for Windows 4.05 found: C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite
2025-06-22 19:06:08 - TBIView 4.63 found: C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TBIView
2025-06-22 19:06:08 - TBIMount 1.26.1 found: C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TBIView
2025-06-22 19:06:08 - TBOSDT 3.02 found (Professional for BootIt version): C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TeraByte OSD Tool Suite Pro
2025-06-22 19:06:08 -   | Warning: BootIt license key not found or appears invalid. Without a valid key, TBOSDT will run in Professional mode.
2025-06-22 19:06:08 - Build source: Windows 10 Pro [10.0.19045] WinRE
2025-06-22 19:06:08 - Locating WinRE image
2025-06-22 19:06:09 - WinRE located (Winre.wim, active): \\?\Volume{e1776c5e-4c13-42bb-8a2e-42104e98acdf}\Recovery\WindowsRE (0,0,0x1F,0x7F,0xF) (0x0)
2025-06-22 19:06:09 - Version of installed WinRE: 10.0.19041, Architecture: x64, Service Pack: build 5728, level 0
2025-06-22 19:06:10 - Version of backup WinRE: 10.0.19041, Architecture: x64, Service Pack: build 5728, level 0
2025-06-22 19:06:10 - Backup copy of winre.wim found
2025-06-22 19:06:11 - Verification complete
2025-06-22 19:06:21 - Creating TBWinRE build
2025-06-22 19:06:21 - Build ID: {0FF8C54E-F47B-4A58-8758-CBD178394111}
2025-06-22 19:06:21 - Build path: C:\tbwinre
2025-06-22 19:06:21 - Initializing DISM (1,0)
2025-06-22 19:06:21 - DISM initialized (A)
2025-06-22 19:06:21 - Copying WinRE image
2025-06-22 19:06:22 - Mounting WinRE image
2025-06-22 19:06:51 - WinRE image file architecture: x64 [10.0.19041.5728] (AC:7)
2025-06-22 19:06:51 - Exporting Wi-Fi profile files
2025-06-22 19:06:51 -   | Exporting: Wi-Fi-Profile1.xml
2025-06-22 19:06:51 -   | Profile: ABCDE (exported)
2025-06-22 19:06:51 -   | Exporting: Wi-Fi-Profile2.xml
2025-06-22 19:06:51 -   | Profile: BCDEF (exported)
2025-06-22 19:06:51 -   | Exporting: Wi-Fi-Profile3.xml
2025-06-22 19:06:51 -   | Profile: CDEFG (exported)
2025-06-22 19:06:51 -   | Exporting: Wi-Fi-Profile4.xml
2025-06-22 19:06:51 -   | Profile: DEFGH (exported)
2025-06-22 19:06:52 - Configuring WinRE
2025-06-22 19:06:52 - Info: DEFAULT hive loaded manually (0x2) (0x0)
2025-06-22 19:06:52 - Info: SYSTEM hive loaded manually (0x2) (0x0)
2025-06-22 19:06:52 - Adding TBLauncher [1.40]
2025-06-22 19:06:53 - Adding Image for Windows [4.05]
2025-06-22 19:06:54 - Adding TBIView [4.63]
2025-06-22 19:06:54 - Adding TBIMount [1.26.1]
2025-06-22 19:06:56 - Adding TeraByte OSD Tool Suite (Pro for BootIt) [3.02]
2025-06-22 19:06:57 -   | BootIt license key not found
2025-06-22 19:06:57 - Finalizing build
2025-06-22 19:06:58 - Copying booting files (0,3)
2025-06-22 19:06:59 - Adding drivers
2025-06-22 19:07:26 -   | Success: C:\tbwinre\Drivers\Latitude 7350\Ethernet\rtu52cx22x64sta.INF
2025-06-22 19:07:26 -   | Success: C:\tbwinre\Drivers\Latitude 7350\Ethernet\rtu53cx22x64sta.INF
2025-06-22 19:07:26 -   | Success: C:\tbwinre\Drivers\Latitude 7350\Ethernet\rtu55cx22x64sta.INF
2025-06-22 19:07:26 -   | Success: C:\tbwinre\Drivers\Latitude 7350\Ethernet\rtu56cx22x64sta.INF
2025-06-22 19:07:26 -   | Success: C:\tbwinre\Drivers\Latitude 7350\Ethernet\rtu57cx22x64sta.INF
2025-06-22 19:07:26 -   | Success: C:\tbwinre\Drivers\Latitude 7350\Ethernet\rtump64x64sta.INF
2025-06-22 19:07:26 -   | Success: C:\tbwinre\Drivers\Latitude 7350\WiFi\Netwtw08.INF
2025-06-22 19:07:26 -   | Success: C:\tbwinre\Drivers\Latitude 7350\WiFi\Netwtw6e.INF
2025-06-22 19:07:26 -   | Success: C:\tbwinre\Drivers\Latitude 7420\Ethernet\rtu52cx22x64sta.INF
2025-06-22 19:07:26 -   | Success: C:\tbwinre\Drivers\Latitude 7420\Ethernet\rtu53cx22x64sta.INF
2025-06-22 19:07:26 -   | Success: C:\tbwinre\Drivers\Latitude 7420\Ethernet\rtu55cx22x64sta.INF
2025-06-22 19:07:26 -   | Success: C:\tbwinre\Drivers\Latitude 7420\Ethernet\rtu56cx22x64sta.INF
2025-06-22 19:07:26 -   | Success: C:\tbwinre\Drivers\Latitude 7420\Ethernet\rtu57cx22x64sta.INF
2025-06-22 19:07:26 -   | Success: C:\tbwinre\Drivers\Latitude 7420\WiFi\Netwtw08.INF
2025-06-22 19:07:26 -   | Success: C:\tbwinre\Drivers\Latitude 7420\WiFi\Netwtw6e.INF
2025-06-22 19:07:26 -   | Success: C:\tbwinre\Drivers\OptiPlex 7090\Ethernet\e1d.inf
2025-06-22 19:07:26 -   | Success: C:\tbwinre\Drivers\OptiPlex 7090\WiFi\Netwtw08.INF
2025-06-22 19:07:26 -   | Success: C:\tbwinre\Drivers\OptiPlex 7090\WiFi\Netwtw6e.INF
2025-06-22 19:07:26 - Saving WinRE image
2025-06-22 19:07:45 - Unmounting WinRE image
2025-06-22 19:08:01 - Creating CD/UFD/ISO file layout
2025-06-22 19:08:02 - Build process completed successfully
2025-06-22 19:17:48 - Program exiting with code 0
Last edited by PsychBiller on Sun Jun 22, 2025 11:56 pm, edited 1 time in total.
PsychBiller
Posts: 72
Joined: Sun Aug 05, 2012 4:45 pm

Re: TBWinRe won't initialize network booting from USB

Post by PsychBiller »

I also just noticed that the partitions on the hard drive are not being assigned drive letters when booting from TBWinRe. This is just all so weird.
TeraByte Support(PP)
Posts: 1740
Joined: Fri Aug 12, 2011 12:51 am

Re: TBWinRe won't initialize network booting from USB

Post by TeraByte Support(PP) »

Are the partitions set to not be assigned a letter? When booting from the boot media, the drives will be assigned whatever WinPE/RE does by default. On some system drives, there may only be the Windows partition that gets assigned a letter. If you need to assign a letter to an unassigned partition you can do this from TBLauncher.

For testing the drivers, the folder you would look in is just where the drivers are that you want to try. For example, if you didn't include any drivers in the build and then wanted to test them separately, you could copy the Drivers folder to the UFD and then browse down it when loading a driver (you select the .inf file for the driver you want). Or you could browse and select drivers on the booted system (those in the \Windows\System32\DriverStore\FileRepository, for example).
PsychBiller
Posts: 72
Joined: Sun Aug 05, 2012 4:45 pm

Re: TBWinRe won't initialize network booting from USB

Post by PsychBiller »

The target system where i will use TBWinRe always had a drive letter assigned with version 3. I definitely want a deive letter. The target system has just a main C:.

I just want v4 to build the USB like v3 did. Ive compared INI files and can’t find the differences. Why is v4 not building the USB the same way and making this exponentially more difficukt?

Should I take this offline through the support email and send you all the INI files and folder structures? At this point, version 4 is unusable.
TeraByte Support(PP)
Posts: 1740
Joined: Fri Aug 12, 2011 12:51 am

Re: TBWinRe won't initialize network booting from USB

Post by TeraByte Support(PP) »

Emailing support and attaching the additional files/info may be helpful. You can answer the following questions in the email.

Do you still have your V3 USB drive that works on the system? Do you still have the build log for it? How long ago was it created? It may have used a different WinRE version that what you're using now. It's not uncommon for some versions to break things. If you have the build log, that would be good to send. If you have the USB drive, you could send the TBWinRE.txt file in the \TBData folder of the drive. If you can tell which version was used and you still have that WinRE WIM backup available, you could try a build using it as the source and see if it works.

I can't think of any changes that would affect drive letter assignments. Those are automatically handled by WinPE/RE when booting up. Is the USB drive getting a letter assignment?

I'm also curious if a build on the target system would work properly or if it would have the same issues. There are some WinRE builds that don't work well on other systems and some are specially configured for their system (i.e. not a base WinRE build).

Regarding the drivers, I have noticed that sometimes if there are many different versions being included that the one that works may be more likely to not be used (assuming only one works).
PsychBiller
Posts: 72
Joined: Sun Aug 05, 2012 4:45 pm

Re: TBWinRe won't initialize network booting from USB

Post by PsychBiller »

For those following this thread, I had a bad WIM. Using one of the backups worked. The drive letters not being assigned was a Windows 11 24H2 issue where a flag had to be flipped in DISKPART.
Post Reply