Is boot.wim a good substitue for winre.wim

[yottabytes2]

I don't have WinRe.wim on my PC. Is it still possible to create a TBWinRE .iso with boot.wim? (I tried extracting WinRe.wim from the original ISO and put it in C:\Windows\system32\Recovery folder along with the .xml file and TBWinRE Builder still complains it is unable to locate the file. Is it supposed to be in an alternative location?)

[TeraByte Support(PP)]

Assuming it's a valid TBWinPE/RE boot.wim file, you can use it as the source for a build. If it's some other boot.wim file then there may be issues or it might not even be compatible. For example: TBWinPE boot.wim for TBWinPE builds, TBWinRE boot.wim for TBWinRE builds

TBWinPE/RE Builder can extract the WinRE WIM from a Windows ISO. Is that the method you used? On the Paths tab in Settings, you can select the WIM file as the source and it will use it even if it can't find an installed source. You can use the down-arrow on the Browse button to directly browse the WinRE_Backup or Extract_WinRE folders.

[yottabytes2]

Hmmm. When I use the WinRE source browser in the program paths on version 4.07, it only looks for .wim files. It doesn't seem to be able to extract from an .ISO unless I'm missing something. And after using DISM to extract and, then, export a Winre.wim file from the .iso and running TBWin builder, it displays the warning "Unable to locate WinRE at installed location" even though that location exists.

Nevertheless, I succeeded in creating a TBWinRE .iso despite the warning. So the other stuff is just FYI. I still don't have touchpad support on my laptop though. . .I'll try adding drivers to the build next time.

[TeraByte Support(PP)]

Extracting the WinRE WIM from the ISO is a separate process. It's in the File menu, "Extract WinRE from Windows ISO..." option. This extracts to the Extract_WinRE folder and the file can then be selected when browsing for the source.

If WinRE is not found at the installed location (WinRE enabled), you'll get that message. However, it may still be finding it in the \Windows\System32\Recovery location when searching alternate locations. It should be logged if that's the case. You may need to repair WinRE to get the installed location working. Often, it's just a case if doing a "disable" / "enable" to fix it if the WIM is in the correct location (which you say it is).
https://www.terabyteunlimited.com/kb/kb ... ent-winre/

[yottabytes2]

OK. Thank you very much for the explanation.