In this case, the self-repair is run in both cases where the folder is missing and where a file is missing. I don't understand why you go into such a long discourse about having a filename being changed.
Why delete files after installation? Sometimes they are just temp files that serve some purpose, sometimes an application may come with the full set of files but some may not be needed if a particular feature is not purchased But that is not the issue here.
The question is "Is it possible to suppress the self-repair and how? OK, so it is by design that Vital has no connection with repair. But one would think that if a file is not vital for the success of an installation, why would that file being missing later cause a self repair? Maybe not enough thought has been given to this logic? Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums.
ClickOnce and Setup. Sign in to vote. Hi, 1 Can you tell me what trigger Installer to start a self-repair? Thanks in advance. Thursday, August 2, PM. I have no way to get back to command prompt to enable it again.
The only thing I can do is get to the f2, f8, and f12 screens but from there it goes black. Any ideas? My computer run automatic repair after install driver. Your email address will not be published. Skip to content Advertisement.
Support us Winaero greatly relies on your support. Otherwise Microsoft and I are going to have some serious words! Hope that helps someone! Leave a Reply Cancel reply Your email address will not be published. Next Next post: Change the Chkdsk timeout at Windows 10 boot. We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. Read More Do not sell my personal information.
Close Privacy Overview This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website.
We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. All of the program's files are uncompressed on the CD and the MSI file contains no other files and is just 2.
The problem is that the program doesn't run without proper installation, which sets up many registry entries, installs some video codecs, a kernel mode driver and does the license activation over internet. Each component in an MSI requires a Keypath. In your case the shortcut seems to be set as a keyfile. The Windows Installer Service is trying to verify the availability of the keypath element and if it cannot find it it will Repair itself. This will hopefully fix your problem.
First check your event log. When you have your event viewer open select Application Log and find the application that is giving you trouble. An easier way can be to right click on application log and clear it. Then run the program and let it give you the repair error. Then check the log. Copy that down. You can now close event viewer. Okay, now you need to find Orca. Or google for Orca.
When you have Orca use it to open up your MSI install file. On the left hand side of the program you see a list of tables. Scroll down and select "Component".
You'll now see, in the right side, a table of components and their information including compenent id's. Delete the information in the keypath cell for all the component ids that were giving you trouble. Save your MSI. Now uninstall and reinstall the software using the new MSI. You should not have anymore problems. I hope that fixed your problem. If not: Sorry for such a long post. Last edited by gabri3l; at But the KeyPath is an empty value. I can't delete anything from it since there is nothing in it.
0コメント