- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Windows Update Triggers Repair
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi,
We generate install packages with Basic MSI projects. Occasionally a windows update will trigger a repair of our application... at least I assume that is what is happening. All of out patches get reverted so that the app is back to the state in which it was originally installed. Wh
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
HI @rguggisberg,
Thank you for your post.
The best practice approach for diagnosing and troubleshooting autorepair is to check the Event Viewer > Application log. What we're looking for is a component's missing keyfile or something of that nature that's causing the autorepair. A keyfile is a file that the installer "keys off of" to determine whether a component is installed. If a keyfile is missing then the installer will trigger autorepair to reinstall that missing component.
In the Application log, you will find warnings from event source Msilnstaller with Event IDs 1001 and 1004:
The message details will look like this:
Event ID: 1001
Description: Detection of product "{AAAAAAAA-BBBB-CCCC-DDDD-EEEEEEEEEEEE}", feature "Test" failed during request for component "{BBBBBBBB-CCCC-DDDD-EEEE-FFFFFFFFFFFF}"
Event ID: 1004
Description: Detection of product "{AAAAAAAA-BBBB-CCCC-DDDD-EEEEEEEEEEEE}", feature "Test", component "{BBBBBBBB-CCCC-DDDD-EEEE-FFFFFFFFFFFF}" failed The resource "C:\Program Files\MyCompany\test.exe" does not exist
Please have a look. Do those entries help explain what is triggering autorepair?
Please let us know if you have any questions or concerns. Thanks!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
What could be causing this?
Thanks
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
HI @rguggisberg,
Thank you for your post.
The best practice approach for diagnosing and troubleshooting autorepair is to check the Event Viewer > Application log. What we're looking for is a component's missing keyfile or something of that nature that's causing the autorepair. A keyfile is a file that the installer "keys off of" to determine whether a component is installed. If a keyfile is missing then the installer will trigger autorepair to reinstall that missing component.
In the Application log, you will find warnings from event source Msilnstaller with Event IDs 1001 and 1004:
The message details will look like this:
Event ID: 1001
Description: Detection of product "{AAAAAAAA-BBBB-CCCC-DDDD-EEEEEEEEEEEE}", feature "Test" failed during request for component "{BBBBBBBB-CCCC-DDDD-EEEE-FFFFFFFFFFFF}"
Event ID: 1004
Description: Detection of product "{AAAAAAAA-BBBB-CCCC-DDDD-EEEEEEEEEEEE}", feature "Test", component "{BBBBBBBB-CCCC-DDDD-EEEE-FFFFFFFFFFFF}" failed The resource "C:\Program Files\MyCompany\test.exe" does not exist
Please have a look. Do those entries help explain what is triggering autorepair?
Please let us know if you have any questions or concerns. Thanks!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Thanks. That helps.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
You're welcome. I'm happy that helps.