Windows installer now creates the installstate file based on the new dll's name and doesn't get removed during the uninstall of the previous version. hope this helps someone. al. 1001 always means that you had an installer class ( installutil ) custom action fail. you'll have to debug that code to understand what went wrong.. The first message (with event id 1001) states which component was being installed. the component listed here is the component named in the component_ column of the shortcut table for the particular shortcut..
If you want to stay constantly protected from malware threats, existing and future ones, we recommend that you install malwarebytes anti-malware pro by clicking below (we do earn a commision from sales generated from this link, but at no additional cost to you. we have experience with this software and we recommend it because it is helpful and useful):. 4. edit the msi file using a msi editor like orca and search for the “%custom action%.setproperty” in the custom action table. (%custom action% is the failed custom action name copied from the log file) 5. choose the target column in the row of “%custom action%.setproperty” and see if there are any windows installer properties which. A restart did not solve the issue for me, i have attached an application and system log that contain entries related to the two installs. system-log.xml application-log.xml the security audit log does not show any failures relating to the application install..
No comments:
Post a Comment