At times Lego gets tied up with real life, and he is the only developer, so it might be awhile before a further update. The time between updates sometimes varies wildly. Since you are "desperate", you can help find the problem if you can do some more test runs. 1. Make a build just like the one that causes problems, but use an older version of Win Toolkit, so we can see at what point Win Toolkit changed to cause your issue. 2. Make a build with the latest version of Win Toolkit, but without any silent installers, just to see what happens. 3. Assuming (2) works, slowly add a few silent installers at a time to see if the problem might be related to a particular silent installer. I'm not saying that would mean that it is that silent installer's fault, but it could point to some kind of dependency issue or something. 4. If (2) doesn't work, make a build without any tweaks. Then slowly add them back in as in (3). Bottom line, you want to try and determine if the problem occurs only with a particular installer, or tweak, or group of installers, or if it occurs with any installer no matter which one or how many. Same with the tweaks you use. If none of those tests provide any resolution, the only other thing you can try is to do the same kind of thing with your updates you integrate to see if one of them works better being installed at RunOnce. Upload any logs created and provide a link to them here. I know it's a lot of work, but the more testing and info you can provide the more likely the true problem can be resolved sooner. Anything you can do will help. Cheers and Regards