Opened 7 years ago
Closed 6 years ago
#3590 closed Bug (Fixed)
Autoit product installation deleting all psmodulepath entries but its own
| Reported by: | whiggs.ITPRO@… | Owned by: | Jon |
|---|---|---|---|
| Milestone: | Component: | AutoIt | |
| Version: | 3.3.14.3 | Severity: | None |
| Keywords: | Cc: |
Description
Ok. So this has occurred on two machines that I have installed the newest version of autoit and scite for autoit on, and this occurs right after the installation. My process: I uninstall the beta version of autoit, download the most up-to-date production version of autoit, run the installer, uninstall the previous production version of autoit from the installer, proceed to install the latest production version of autoit. Then, I use the AutoITupdate script in Autoit's "extras" folder to download and re-install the beta. I then download the latest version of scite for Autoit and install it (I have done this both with and without uninstalling it). The result? One of these installers is completely wiping out all of the values in the PSModulepath environment variable. How do I know? Take a look at the only two remaining values that are configured for the environment variable (see picture 1 since I can't post image links due to the fact my submissions keep getting blocked as spam).
All I can say is thank god I had backups of my environment variables and I was able to restore them. I don't know which autoit product is doing this, but please fix it. This is what greets those who open powershell after installing the faulty autoit product (see picture 2 since I can't post image links due to the fact my submissions keep getting blocked as spam).
For those who are not familiar with PSModulepath, this is what it should look like (restored from backup) (see picture 3 since I can't post image links due to the fact my submissions keep getting blocked as spam).
Attachments (1)
Change History (6)
Changed 7 years ago by whiggs.ITPRO@…
comment:1 Changed 7 years ago by Jon
It seems to work ok on my tests here. But I only have a few pre-existing variables whereas you have a lot of paths. It could be a bug due to path length within the NSIS installer that I'll have to investigate.
comment:2 Changed 7 years ago by Jon
- Owner set to Jon
- Status changed from new to assigned
comment:3 Changed 6 years ago by Jos
From which version was the upgrade done?
comment:4 Changed 6 years ago by Jos
This was fixed in version v3.3.13.14, so when upgrading from any version before v3.3.13.14, you can still have this issue as the uninstall is done by the old version installer.
I will close this for now and report if this issue occurs with uninstall of any version eq or gt v3.3.13.14.
Jos
comment:5 Changed 6 years ago by Jos
- Resolution set to Fixed
- Status changed from assigned to closed
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.
pictures