You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a well-intentioned, but non-technical Windows user wants to un-install and re-install a program, they often try to DELETE ALL THE FILES. However, this leaves vestigial registry keys lingering. Unfortunately, when they manually delete all the files, this often deletes the uninstaller too, leaving us to manually track down orphan registry keys before the NSIS installer can actually work again...
To avoid manual intervention for broken installed, the NSIS installer should remove these registry keys if they exist on each new install.
Users can currently add this functionality through a custom installer init script as referenced here: #4057 (comment)
This functionality should be part of the default NSIS installer script. I'll be tackling this task in mid November, if nobody picks it up before then.
The text was updated successfully, but these errors were encountered:
This is a ticket to track work on #4057 (comment)
When a well-intentioned, but non-technical Windows user wants to un-install and re-install a program, they often try to DELETE ALL THE FILES. However, this leaves vestigial registry keys lingering. Unfortunately, when they manually delete all the files, this often deletes the uninstaller too, leaving us to manually track down orphan registry keys before the NSIS installer can actually work again...
To avoid manual intervention for broken installed, the NSIS installer should remove these registry keys if they exist on each new install.
Users can currently add this functionality through a custom installer init script as referenced here: #4057 (comment)
This functionality should be part of the default NSIS installer script. I'll be tackling this task in mid November, if nobody picks it up before then.
The text was updated successfully, but these errors were encountered: