I've spent the past 2 hours trying to get a tiny 1kb file to work in my MSI installer using Advanced Installer 9.6.1. The package I'm creating is very simple and will be used to make sure No Adobe products auto-update on our workstations via files on workstations and registry keys. Here's what the packages does:
- Adds a few registry keys to Windows on target workstation
- Adds a file to %APPDATA%\Adobe\AIR on target workstation
- Adds a file to the following 2 paths:
- C:\Windows\System32\Macromed\Flash
- C:\Windows\SysWow64\Macromed\Flash
After creating it, it all works great - except - that it doesn't put the file in System32\Macromed\Flash. I read that it was because it was a 64 bit installer. I saw that I could create a mixed installer, but need it to be an MSI if at all possible. I then tried the following as workarounds:
- Made a Custom Action with attached batch file to copy file from application folder to System32\Macromed\Flash at the commit state - didn't work
- Made a Custom Action with attached batch file to copy file from public UNC share to System32\Macromed\Flash at the commit state - didn't work
- Made a Custom Action with attached VBS file (uses xcopy) to copy file from application folder to System32\Macromed\Flash at the commit state - didn't work
All of the above worked when run manually on my workstation, but not in install. This is when I realized that the application, itself must not have any access to System32 during installation.
So... besides a custom action putting a file in the startup folder to add file at next reboot
Thanks!
One more thing...
I was going to leave this out of app, but since I'm posting might as well ask... It's easy to add registry keys via an installer - but - how can existing ones be removed with installer? Would it have to be done by running custom script and not though Registry GUI section of Advanced Installer? Thanks
FOLLOW US
Get the latest news in Application Packaging