Now this is starting to piss me off! There is a difference between pre-build and the finished ISO. This is the TBLaunch.ini I'm using. I copy of it is in \tbwinre\config and \tbwinre\. After launching TBLauncher64.exe in the \tbwinre folder, everything seems to work. Everything is listed correctly. So, I know it works. Then, after I build the ISO there's nothing from IFW or my custom entries in the TBLaunch menu. I don't know what the problem is with building it.
I just noticed in the [Menu] section that you have this. I don't have a DisplayCount. This is all I have in the menu section. I haven't done a clean install in a long time, so I guess I'm using a TBLauncher.ini before DisplayCount was added. The Knowledge base doesn't mention DisplayCount. It only mentions ItemCount. It still doesn't explain why nothing is showing in the menu. I'm not sure how those big apps will work, but the menu should still display them.
I'm using 4.01. Do you have your Custom folder located in?: C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\tbwinre\ISO My CustomProg folder is located in the ISO folder. I see you also have an IFW folder, then a Custom folder below it. I wouldn't think it should matter though as long as it's in the ISO folder and pointing to it's correct location. Also, try commenting out or removing the DisplayCount=6.
Maybe that could be the issue, using 4.00 versus 4.0.1. I removed the entire DisplayCount= section and rebuilt the iso. Nothing changed. I'll try moving my "Custom" directory as a sub directory of the ISO folder and re-run it. Like you, I cannot see how that will matter. But I'll try anything at this point.
Are you running the TBWinPE/RE Builder (TBWinPE.exe) from this location? C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\tbwinre I'd also try "Run as administrator". Are you using TBWinRE or TBWinPE? I've used both many times in the past. I'm currently using TBWinPE and have been for about a year or more. Once again, I wouldn't think that should make a difference either.
Brb...off to test. I rebuilt the iso as admin. This time I can see the TBLauncher.ini in the iso, with my new edits.
No luck! I don't get it. Launcher64 sees all the entries inside of Windows. But when I create the iso and reboot, booting with Ventoy to the new iso, no TBLauncher entries are listed. Only the system repair entry is there. But the TBLauncher.ini with all my entries is listed in the iso, along with the custom app dir. I'm confused.
So, you're creating an ISO first rather than going straight to a UFD. I also create ISOs as a backup, but I don't see TBLauncher.ini in TBData when I mount it. I only see TBWinPE.txt.
Well this sucks! I've had more fun stabbing myself in the ear after I accidentally started playing a Taylor Swift song on Spotify and getting glorious temporary deafness. Yeah, I use iso because created a ufd requires erasing the drive, and I can't do that.
Well, booting from the ufd did not give any different result. Everything was the same, which means I just erased my drive for nothing.
There has to be something you're doing different to me. Maybe send the Bat-Signal out to Brian. Keep at it. You'll work it out eventually. It's probably something simple. Do you only have one UFD? Maybe we can get Wilders members to chip in and buy you one.
Ha! I do only have the one, but it's a 2tb external ssd. That's why I only have the one; backup (of backups of backup) images are stores on it, along with Ventoy and portableapps.
I'm fishing in the wilds of Cape York. Phone signal but no computer or notes. My only thought is to make a conventional UFD without making an ISO first. Are you using a buildscript.cmd?