cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
rguggisberg
Level 13

Windows Update Triggers Repair

Jump to solution

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

Labels (1)
0 Kudos
(1) Solution

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!

View solution in original post

(4) Replies
rguggisberg
Level 13

What could be causing this?

Thanks

0 Kudos

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!

Thanks. That helps.

0 Kudos

You're welcome. I'm happy that helps.

0 Kudos