@RN, I would think it is just a case of timing and interaction between some of the runtimes, which includes .NET, and some of the other RunOnce items which depend on them being in place. It is sometimes the installer of the app which utilizes the runtime, and sometimes it is the app itself. Some of the repacked or slimmed apps, such as some of Rick's, strip out runtimes which the full installers include, which is why runtimes should always be the first RunOnce items installed. I would also think that this situation can vary based on architecture. While I suppose that it is possible that there is something in Win Toolkit's RunOnce code that has an architecture related glitch, I would think it is more likely that it is something in MS's installer code or that of the individual apps themselves. Just my opinion. Cheers and Regards