@Juan Conejero - I can guaranty that I have no backup software nor antiviruses running and "quarantining" random files on my astrophotography computer, nor did I do any "system update". For what its worth, I am a system programmer by profession, I am very aware of such problems, as well as unreproducible problems that still must be handled. It does seem like this problem is experienced by a few users, so it does require some attention.
I do get that it is not easily reproducible - this is why I suggest workarounds, e.g. a "
restore default scripts" option in settings, the installer's "
repair" option, an external script, or something else which would automate reverting the software to its original state. No one should go through what I did just to get a script back.
Here is a rundown of the things I tried (
@kkuenstler and others):
1. Re-ran the installation software, and clicked the "repair" option -
did not help
2. Uninstalled and reinstalled from scratch -
did not help
3. Uninstalled, manually removed every mention of pixinsights from my hard drive, as well as any mention of pixinsights from the windows registry, then reinstalled -
WORKED, I got that script back.
However, let me CAUTION: DO THIS AT YOUR OWN RISK. Messing around with registry is not safe, and you should google around on how to make backups of it before you make any changes!
In my opinion, the "repair" option of the installer should have brought back the script. Further, the "uninstall" option should actually remove everything from the system that is related to pixinsights. It is customary for the uninstaller to give an OPTION to retain some configuration, but there was a LOT of stuff left in the registry I had to manually remove for the system to actually be clean of pixinsights.