zaproxy / zaproxy

The ZAP core project
https://www.zaproxy.org
Apache License 2.0
12.51k stars 2.24k forks source link

issue when installing the new version #8486

Closed DorghamX closed 4 months ago

DorghamX commented 4 months ago

when i tried to update to the latest version of zap the uninstallation process was done successfully but when it tried to install the new version it popup this error Screenshot 2024-05-12 160753 and it doesn't matter how many times i click yes it still pops up again

any advice ?

kingthorin commented 4 months ago

1) Use the issue templates next time. 2) Is the drive full or do you need admin etc permissions to install in your environment?

DorghamX commented 4 months ago

No its not full and i already ran it as administrator

kingthorin commented 4 months ago

Exit ZAP, goto the location, delete the file. Launch ZAP goto the market place and install Active Scan Rules.

DorghamX commented 4 months ago

there is no location because as i mentioned this error occurs during the installation process so it's not installed yet

Screenshot 2024-05-12 172446

if i clicked "Cancel" the whole installation process will be canceled and if i clicked "yes" the error pops up again

kingthorin commented 4 months ago

Maybe your download is futzed. Delete the installer and re-DL.

DorghamX commented 4 months ago

this also not working i deleted it and redownloaded it the "Windows (64) Installer 2.15.0" is the one that have the problem on the other hand the cross platform package works fine, same with the older version of it "Windows (64) Installer 2.14.0" i downloaded it again and installed it successfully

kingthorin commented 4 months ago

What Java do you have installed? What OS? Any AV?

thc202 commented 4 months ago

Make sure you don't have any anti-virus or other program blocking the file copy. (The installer is working fine, it was tested before the release.)

DorghamX commented 4 months ago

yeah disabling the anti-virus made it work thanks

github-actions[bot] commented 1 month ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.