How can we run RunOnce / active setup in windows more than once?

In Actual Implementation, sometimes client give us the package with same version number, they don’t change the package version, even if it is upgrade, they don’t the package to be upgraded with the version number. The same version exist on the client machine. We do uninstall and install. Even if we uninstall, active setup doesn’t uninstall, we have to do something for it. So at that we need this that what we have to do so that it runs once again?(run, runonce)

Under which condition Run works and under which condition it doesn’t work? Just like RunOnce/Active setup runs only once why not 2nd time?what does it check? If I want to manually the run the RunOnce 2nd times So what changes we will do registry so that it will run again one time manually? for that which value we have to change in registry.

How can we run RunOnce active setup second time manually?

0 Comments   [ + ] Show comments

Answers (3)

Posted by: Nico_K 7 months ago
Red Belt

You can set this Registry key multiple times, so it runs on next boot once.

Posted by: rock_star 7 months ago
4th Degree Black Belt

Educate your client as how versioning of application happens. 

Also, go and read more about Active Setup and Run key.. 

Googling don't harm  before you post in .. 



Posted by: EdT 7 months ago
Red Belt

Active setup writes a copy of the data in hklm to the equivalent location in hkcu. You could use a release number instead of the version number and increment each time a new package is released. The version delimiters in active setup are commas not periods. As someone already mentioned, teach your developers about release versioning.

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ