Package Extraction Error on updates: Win 7 Pro

[TheMadOne]

Hello,

I continually receive the same package extraction error on my main Windows 7 Pro Machine as follows:

Failed

C;/users/mark jordan/appdata/local/temp/pixinsight.com/20151127-refdoc.zip (Exit Code = 2)

Any suggestions or clues, I have researched here and see some similar type bug posts for Fedora, but not Windows.  Right now I cannot perform any updates on my Pixinsight installation on my main desktop.  Seem to work fine on my notebook & observatory work station, both on Win 7 pro as well as the recent update on those 2 machines to Win 10 Pro.

Thanks,

Mark Jordan

[Randall]

I have had the same problem. I just purchased PI and after the installation on my main desktop machine with Windows 7 64bit, I got the same package extraction errror.

As far as I can tell, the problem lies with your Anti-Virus program. In my case it is Vipre.

To prove this, I also installed PI on my Windows 7 64 Bit HP laptop. The 8 updates notice appeared and they went through with no problem. The Anti-Virus program on that machine has Bit Defender.

When I first tried to install the 8 updates on my desktop machine running Vipre, Vipre returned messages that the updates were corrupt and contained Trojans. I figured that this was a bogus error and that the PI sight was/is a secure download site.

I had a clean system restore point before I installed PI so I went back and restored and downloaded PI again and did a fresh install WITH THE ANTIVIRUS PROGRAM TURNED OFF!!  Then the 8 updates to PI 1.8 updated flawlessly.

It looks like PI's updates are in a .zip format and they install automatically. There has to be a way (in Vipre) to allow these updates to occur but I am unable to find it, and I am trying to get in touch with them. But this error comes up as a PI error, not Vipre so I hope a moderator on this forum reads this.

In the meantime, before any updates are attempted for PI, TURN OFF YOUR AV PROGRAM.

I'm curious to know if you are using Vipre as well.

Good Luck
Randall

[Juan Conejero]

Of course, a package extraction error is not a bug. Quite the contrary, it tells you that something external to PixInsight is either altering the update package that has been downloaded, or preventing it from being decompressed correctly. By issuing this error, PixInsight is protecting both itself and you from installing a wrong update.

Typically, this happens on Windows because an antivirus or malware program has been doing "its job". We are not responsible for problems caused by other applications.

[TheMadOne]

After much chasing of virus scanner settings, firewall settings, possible left overs from old security software suites that have been uninstalled and replaced with new.  Chasing of Windows settings, posting on windows user forums for some input, none of which did anything to resolve the PixInsight error as listed above, I found a solution.  I once again did an uninstall with the PixInsight uninstaller, restarted the machine(s), opened PixInsight and attempted to update once again...  Same error, so I used the PixInsight "Reset PixInsight Settings", and Restarted again.

Guess What!!!  This solved the update problem on all three of my systems... The Observatory Desktop, my main work Station desktop in the house and my notebook I use for travel.  The only system I had done the problem chasing on which proved out to make no difference was the main work station desktop... the other two have not been monkeyed with at all.  Figured I would not be beating about within their files, security applications and such untile I had found the possible culprit within the Windows and/or Security Suite application(s)  The work station is a Windows 7 Pro, the other two are Windows 10 pro (upgrade from 7 Pro)...  Same solution worked on all three systems, leads me to believe the problem was something within the settings somewhere within the PixInsight application.  Possibly something had caused the same file corruption on all three systems!!???...  Hard to believe that as the Observatory desktop is only used for observatory related workings & such.

Anyhow the "Reset PixInsight Settings" has resolved the issue on all three systems....  !!! Yaaayyyyy, I can install the updates once again!