Opened 13 years ago
Closed 13 years ago
#2115 closed Bug (Fixed)
Installer/Uninstaller issues
Reported by: | Valik | Owned by: | |
---|---|---|---|
Milestone: | 3.3.9.1 | Component: | AutoIt |
Version: | 3.3.8.0 | Severity: | None |
Keywords: | Cc: |
Description ¶
The installer for 3.3.8.0 installed to C:\Program Files\AutoIt3 on x64 which is fine. However, 3.3.6.1 was installed to C:\Program Files (x86)\AutoIt3 and this was not removed or upgraded. I ended up with an orphaned installation of 3.3.6.1 I didn't even know I had. This particular situation needs to be handled more gracefully.
Speaking of orphans, the uninstaller leaves behind the CompileX64 and RunX64 shell commands. This also needs fixed.
Change History (4)
comment:1 Changed 13 years ago by Valik
comment:2 Changed 13 years ago by Valik
I just updated to 3.3.8.1 using silent install and it ignored the x86 install at C:\Program Files (x86)\AutoIt3 and put itself at C:\Program Files\AutoIt3. Not right.
comment:3 Changed 13 years ago by Valik
I've been slightly wrong about all this. My auto-update script was the reason installations were going to C:\Program Files\AutoIt3 so my fault there. However, the AutoIt installer should still detect a previous install and it should detect I'm not installing to the same directory as that previous install so it should warn me/let me remove the orphaned installation.
comment:4 Changed 13 years ago by Valik
- Milestone set to 3.3.9.1
- Resolution set to Fixed
- Status changed from new to closed
Closing this. Since most of the problems were my own doing and Jon fixed the one that wasn't I see no point keeping this open. I still think we could do a better job detecting the scenario I describe but it's probably not worth changing the installer for.
Guidelines for posting comments:
- You cannot re-open a ticket but you may still leave a comment if you have additional information to add.
- In-depth discussions should take place on the forum.
For more information see the full version of the ticket guidelines here.
Actually this is even more confusing than I realized. For some reason it seems 3.3.8.0 silently installed in 64-bit mode which is why it left an orphaned 32-bit 3.3.6.1 laying around. When I uninstalled 3.3.6.1 I broke some registry entries so I had to re-install 3.3.8.0 and I explicitly chose the 32-bit version to be the default so it went to the 32-bit location.
We really need to do some checks on 64-bit systems to make sure only one version is installed. If attempting to upgrade/reinstall to the other version it should ask to remove the soon-to-be-orphaned version.
Now I have to go through, uninstall two separate versions of 3.3.8.0 and then install it again just to ensure everything is sorted out. Crazy.