File Removal not working on Windows 7 ?

[Mardull]

Hello,

I created two similars installers for two similars applications.
Each installer has two "Media", one including a config file, and one not including it.
I add a "File Removal" to always remove this config file, that is created by my applications if missing.

When I run my installers on two differents Windows XP computers, everything works fine. My configuration file is always removed.
But when I run my installers on two differents Windows 7 computers, only one of the two installers is correctly removing the config file.

I checked and re-checked the parameters of my "File Removal", everything is correct (and this is confirmed by the Windows XP computers where everything is working fine).

Can you help me with this problem ?

Environments :
- Windows XP SP3
- Windows Seven SP1
- Advanced Installer 7.2.1

Thanks by advance.

Regards,
Arnaud

[Daniel]

Hello Arnaud,

I'm not sure why you are encountering this behavior. Can you please send us the .AIPs (project files) and the verbose logs of the installation to support at advancedinstaller dot com so we can investigate them?

Each installer has two "Media", one including a config file, and one not including it.

I'm not sure I understand this. Can you please be more specific about what you mean (perhaps exemplify)? Also, can you please give us more details about your scenario?

All the best,
Daniel

[Mardull]

I think we can forget my "Media" explaination : it is not part of the problem.

Lets exemplfy the problem :

I have an installer for the application "Foo", deleting a configuration file call "Foo.ini", when uninstalling the application. This configuration file is created by my application, not by the installer.

I run the "Foo" installer on a Windows XP computer. The install process is working fine. I launch my "Foo" application, that create the "Foo.ini". Then I use the intaller tu uninstall the application. "Foo.ini" is correctly removed.

But when I do the exact same process on a Windows 7 computer, the "Foo.ini" is not removed.

I remain doubtful about this problem, because I have another application "Bar", which installer operates similarly (with a "Bar.ini" config file). But with this installer, the config file is always correctly remove (on the same XP and Seven computers).

I've send you the .aip files, and the uninstall logs of the problem.

Regards,
Arnaud

[Daniel]

Hello Arnaud,

Can you please tell us how it is created your problematic .aip (project file)? Have you copied it from another project and reuse it to build a different installer package? If is the case, then you should use the “Save As Template...” option in order to reuse an existing .aip file to build other packages.

Also, can you test the related package on a Windows 7 clean machine and, then tell us if the behavior still persist?

All the best,
Daniel

[Mardull]

Hello Daniel,

Thanks for your answer.

Yes, and no. I created my first installer, which is the problematic one, and then I copied the .aip to create the second installer. I didn't used the "Save As Template" option.

About the test on a "Clean" Windows 7, I just complete it successfully. The configuration file was correctly removed. It looks like a problem of file permissions, but I can't explain why one installer is working and the other one is not, on the same comuter, with the same user logged in...

Regards,
Arnaud

[Daniel]

Hello Arnaud,

Please keep in mind that when you copy the .aip (project file) and reuse it to build another installer package all the GUIDs for product, components,etc. in the two projects will be identical and thus will conflict if you install it on same machine. So, as I mentioned in my previous post you should use our “Save As Template...” option if you want to reuse an existing .aip file to build another installation package.

All the best,
Daniel

[Mardull]

Hello Daniel,

Thank you for your answer.

Rergards,
Arnaud

[jusher]

oops!

I have saved a project as a template and then recreated an aip project. It seems that the dll's that are registered with MSI are remaining when I try "Remove" they just get left behind.

How can I fix this please? I thought by creating a template and regenerating an aip it would produce different guids for the components?

It seems teh only way around this is to create a CA to delete them?

Regards,
John

[jusher]

I created the CA as mentioned and added it after the Remove All action on the Remove button.

The files still remain even though I said on the component page not to register with MSI.

Any idea what I should do?

Regards,
John

[Daniel]

Hello,

I have saved a project as a template and then recreated an aip project. It seems that the dll's that are registered with MSI are remaining when I try "Remove" they just get left behind.

I'm not sure why you are encountering this behavior. Please keep in mind that project files, having our default project options, which are installed by the installation package should be removed from target machine on uninstall, if wasn't edited by another application meantime. So, can you please verify if the related dll wasn't modified by another application between install and uninstall time?

Also, can you reproduce the behavior on multiple clean machines? If so, can you please send us the .AIP (project file), a verbose log of the installation and the name of the related dll to support at advancedinstaller dot com so we can investigate them?

All the best,
Daniel