File association - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

b.biene
Posts: 66
Joined: Thu Nov 08, 2012 4:21 pm

File association

I have a install-project with 3 diffrent outputs / builds (x86 msi, x64 msi and a mixed EXE)

My Application contains diffrent EXE files and some file-extention-associations. If i install my applicatiion with the EXE-Installer (Mixed mode) i get a error message similar to

"the volume for a file has been externally altered so that the opened file is no longer valid"

when i try to open a file with is associated with one of my Application files. If i install the Application with a MSI (x86/x64) the Windows Installer pops up, the progress bar is shown, and Finaly my Applikation opens.

If have tried to readd the File-association, does not help. Any Idea?
Dan
Posts: 4530
Joined: Wed Apr 24, 2013 3:51 pm

Re: File association

Hello,

I'm not sure where this message "the volume for a file has been externally altered so that the opened file is no longer valid" comes from. When it occurs? When you are running your application or when you are installing it? If it appears when you are running the application then the message is triggered by something from your application.

You are encountering this behavior because Windows Installer triggers a repair for your package. Basically, here is what happens:
- when you open the installed application, Windows Installer verifies if the application is intact (none of its resources are missing)
- if resources are missing (files or registry entries), Windows Installer launches a repair for the installation package of the application

The auto-repair is triggered by the OS because it detects that resource installed by the package have been altered, or removed. This is the normal behavior, recommend to be enabled by default in MSI package.
Even thought it is recommended to be enabled by default in MSI package it is possible to disable this auto-repair.

You can check the system Event Viewer to see what is triggering this behavior.

Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”