TeraByte Unlimited

When I create recovery boot disk (TBWinRE) after instaling 3.14, I get various warnings:

Warnings

PartWork for Windows
Plugin disabled
Unsupported WinRE WIM version

(I have a good screenshot, but don't know how to upload it).

If I ignore the warnings and continue, the the PC, not surprisingly, hangs when the recovery disk is booted.

It's possible the underlying problem is actually caused by a recent Windows update and doesn't really have anything to do with Terabyte suite 3.14 having been installed.

Is this on Windows 10 or 11? Any WIM version 10.0 or higher should be good for PartWork. It's possible the WIM is invalid or corrupted (Windows update does that sometimes).

Can you provide the build log?

It's Windows 11. 2026-09 Security Update (KB5124008) (26200.9445) was installed on September 9. I just discovered that 2026-09 Security Update (KB5129195) (26200.9457) was installed on September 15.

2026-09-26 10:33:20 - ---------------------------------------------------------------------------
2026-09-26 10:33:20 - TBWinPE/RE Builder v1.51 [x86,0x2]
2026-09-26 10:33:20 - Initializing
2026-09-26 10:33:20 - Windows version: Windows 11 Home [10.0.26200.9457 25H2, AMD64]
2026-09-26 10:33:20 - Checking for required build files
2026-09-26 10:33:20 - Initialization complete
2026-09-26 10:33:37 - Verifying build requirements (TBWinRE)
2026-09-26 10:33:37 - Image for Windows 4.13 found: C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite
2026-09-26 10:33:37 - TBIView 4.67 found: C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TBIView
2026-09-26 10:33:37 - TBIMount 1.27.2 found: C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TBIView
2026-09-26 10:33:37 - TBIHD 1.08.2 found: C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TBIView\tbihd
2026-09-26 10:33:37 - TBOSDT 3.11 found (Professional for BootIt version): C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TeraByte OSD Tool Suite Pro
2026-09-26 10:33:37 - | Warning: BootIt license key not found or appears invalid. Without a valid key, TBOSDT will run in Professional mode.
2026-09-26 10:33:38 - Build source: Windows 11 Home [10.0.26200] WinRE
2026-09-26 10:33:38 - Locating WinRE image
2026-09-26 10:33:39 - Warning: Unable to locate WinRE at installed location (Path: \\?\Volume{fe42bdc8-c8d7-42c1-9bca-5d51b16c727a}\Recovery\WindowsRE\Winre.wim) (0,0,0x1F,0x1F,0xD) (0x0)
2026-09-26 10:33:39 - Warning: Unable to locate WinRE at default locations.
2026-09-26 10:33:39 - Version of backup WinRE: 10.0.26100, Architecture: x64, Service Pack: build 7618, level 0
2026-09-26 10:33:39 - Backup copy of winre.wim found
2026-09-26 10:33:40 - Verification complete
2026-09-26 10:33:44 - Initializing plugins
2026-09-26 10:33:44 - | PartWork for Windows
2026-09-26 10:33:44 - | Plugin disabled
2026-09-26 10:33:44 - | Unsupported WinRE WIM version
2026-09-26 10:33:45 - Plugin initialization complete
2026-09-26 10:34:03 - Creating TBWinRE build
2026-09-26 10:34:03 - Build ID: {AB63339E-CD59-41B9-87DC-9326DD33FC18}
2026-09-26 10:34:03 - Build path: C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\tbwinre
2026-09-26 10:34:03 - Initializing DISM (1,0)
2026-09-26 10:34:03 - DISM initialized (A)
2026-09-26 10:34:04 - Copying WinRE image
2026-09-26 10:34:05 - Mounting WinRE image
2026-09-26 10:34:25 - WinRE image file architecture: x64 [10.0.26100.7618] (AC:7)
2026-09-26 10:34:26 - Configuring WinRE
2026-09-26 10:34:26 - Info: DEFAULT hive loaded manually (0x2) (0x0)
2026-09-26 10:34:26 - Info: SYSTEM hive loaded manually (0x2) (0x0)
2026-09-26 10:34:27 - Adding TBLauncher [1.44a]
2026-09-26 10:34:27 - Adding Image for Windows [4.13]
2026-09-26 10:34:28 - Adding TBIView [4.67]
2026-09-26 10:34:28 - Adding TBIMount [1.27.2]
2026-09-26 10:34:28 - Adding TBIHD [1.08.2]
2026-09-26 10:34:29 - Adding TeraByte OSD Tool Suite (Pro for BootIt) [3.11]
2026-09-26 10:34:29 - | BootIt license key not found
2026-09-26 10:34:29 - Finalizing build
2026-09-26 10:34:30 - Copying booting files (0,3)(0x1A)
2026-09-26 10:34:31 - | UEFI: Windows UEFI CA 2023 (0x1)(W-0x3F)
2026-09-26 10:34:31 - Adding drivers
2026-09-26 10:34:31 - Loading driver list
2026-09-26 10:34:35 - Updating driver list
2026-09-26 10:34:38 - Saving WinRE image
2026-09-26 10:35:00 - Unmounting WinRE image
2026-09-26 10:35:37 - Creating CD/UFD/ISO file layout
2026-09-26 10:35:38 - Build process completed successfully

The issue with the PartWork plugin has been found and the fix should be in the next update.

If PartWork isn't installed and you want to remove the warning, go into Settings, Plugins tab and select (highlight) the "PartWork for Windows" plugin. Uncheck it and also uncheck the "Always include this plugin" option for it. (Alternatively, you can right-click on the plugin and delete it.) Then click OK to save the changes.

If PartWork is installed and you want it included in the build, go into Settings, Plugins tab and select (highlight) the "PartWork for Windows" plugin. Click the Edit Plugin button to open it in Notepad. In the [TBPlugin] section at the beginning of the file, find the "WIMVer=10.0.0" line. Change the version number to 0.0 (it should be WIMVer=0.0). Then save the file and close Notepad.

---

I'm not seeing anything in the log that would be causing the hang issue so that may be something corrupt with the WIM or a Windows Update change that broke something.

This is very strange.

I uninstalled the previously mentioned Windows updates and then created TBWinRE media.

No errors or warnings regarding any of PartWork, a plugin or WinRE WIM version and the created TBWinRE media booted normally.

At this point, I thought I had proved that the problem was due to a bad Windows update.

However, I restored the PC to its state before uninstalling Windows updates and created another TBWinRE.

Again no warnings and the TBWinRE media seems fine.

I have no idea what t make of this.

Maybe Windows was doing something with WinRE at the time of the build. That might cause issues with it finding it.

Not likely because I got the failures twice at different times (almost sure different days).

I can't explain it, but the issue seems to be resolved now,