Thank you for taking time to review. I have a captured IRP to ISM and finally MSI. After installing the MSI, the application launches without issue. However, on closing the app, I am getting a Program Compatibility Assistant (PCA) message box. Selecting "This control panel works correctly" closes the message box. All subsequent launches of the software close without any message box. Functionality of the application itself is not affected. In researching, I've learned that this can be an errant message. My plan was to perform a capture during which I would include the toggling on/off PCA from within Services, and then close capture. I haven't tried that yet - my thinking is that it might not work as the end user still may get the message once PCA as been restarted.  
My question is, how do I engineer the ISM so that it does not result in the PCA message box being thrown when the user closes the app on first launch of the application? I have to ensure the message box does not come up for the end user when they close out the application.

I am using InstallShield 2015 Premier on a Windows 7 machine. I am using Repack.exe for capturing.

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

0
Does this message appear when running the application from a normal vendor installation too?

It could be that something is missing from your repackage if the vendor install doesn't produce this problem.

Run a 'Gap Capture' to capture any differences between your package and the vendor install.
Install your package and then run a snapshot of running the vendor installation over the top of it, this will identify any items that may have been omitted during your repackaging exercise that you could incorporate into your package to resolve the issue.

A 'Gap Capture' is generally good practice run anyway, especially against a complex installation, to ensure that everything has been captured correctly.

If the vendor installation also produces the issue, you could run a snapshot of selecting 'This control panel works correctly' to identify what settings are applied to remove the prompt. You can then incorporate this into your package to remove the prompt for your users.

Remember, if they are HKCU or user profile related settings then you'll need an entry point to trigger the self repair to set those items, an advertised shortcut being the main example.
Or an Active Setup entry if that is more suitable for your situation.

Hope that helps,

Dunnpy
Answered 01/12/2018 by: dunnpy
Red Belt

  • Before running the vendor installer over the top of your own, remember to remove any installation data. Otherwise, that installer might see that it's already installed and do nothing.
Please log in to comment
Answer this question or Comment on this question for clarity