I think the registry is somehow messed up. Once that is done, I re-install the same exact VC++ MSI files (from the same directory) and MSI Afterburner starts working. I point them to directory with MSI files extracted from abbodi's VC++ package. I have to manually uninstall integrated VC++, which of course requires pointing to installer location that, by default (in integrated VC++), is expected to be in non-existent directory. In mine I do it monthly to be able to give some feedback here and to be able to make my modifications available on IMCKĬlick to expand.Nope, doesn't work. I repeat this on the family machines every 6 months.
Msmg toolkit download install#
Now I prepare the ISO in 1h 30min, and install everything automated for each machine in 30min and everything is ready.
I use the Toolkit, because to install my system and install it for my family, and leave everything according to my security and privacy criteria (for the most rigorous I install Sparky Linux "Based on Debian Testing" after all we never 100% get rid of telemetry, and in the case of using Windows we have to limit ourselves in what we do in using the system and, keeping in mind what we are willing to share about our personal data.), I lost 6 to 8 hours on each machine. But I only build ISSo with updates released in the second week of the month, just like Toolkit updates are usually based on.That, being based on the updates of the second week of the month, is not always the rule. There is a list folder with templates for each build, for ToolkitHelper which is what does the removal process through the menus.
0 kommentar(er)
