topic Re: Upgrade from 19.5.1.7 to 20.1.3.2 freeze at 3% Verify image in Aerohive Migrated Content

Upgrade from 19.5.1.7 to 20.1.3.2 freeze at 3% Verify image

juergen_dannewi — Thu, 19 Mar 2020 17:28:16 GMT

Upgrade from 19.5.1.7 to 20.1.3.2 freeze at 3% Verify image

Re: Upgrade from 19.5.1.7 to 20.1.3.2 freeze at 3% Verify image

juergen_dannewi — Thu, 19 Mar 2020 17:29:30 GMT

Hi,

I want to upgrade the HiveManager NG from 19.5.1.7 to 20.1.3.2 via Upgrade pack.

It´s stuck with 3% Verify Image.

I´ve downloaded the Image a second time but same state.

Ideas?

Re: Upgrade from 19.5.1.7 to 20.1.3.2 freeze at 3% Verify image

a_huerzeler — Fri, 20 Mar 2020 16:08:28 GMT

Hi Juergen,

do you use the tat.signed version? Maybe restart the appliance before you test the upgrade pack.. I

used the upgrade pack yesterday and it went throu okay in the second attempt.

Good luck!

Andi

Re: Upgrade from 19.5.1.7 to 20.1.3.2 freeze at 3% Verify image

a_huerzeler — Fri, 20 Mar 2020 16:09:04 GMT

*tar.signed

Re: Upgrade from 19.5.1.7 to 20.1.3.2 freeze at 3% Verify image

juergen_dannewi — Fri, 20 Mar 2020 16:10:36 GMT

Hi,

I´ve restarted the appliance and installed the upgrade successful.

Thanks for your support!

Jürgen

Re: Upgrade from 19.5.1.7 to 20.1.3.2 freeze at 3% Verify image

Muslim — Wed, 20 May 2026 11:45:05 GMT

That freeze at ~3% during “Verify image” usually points to an issue with the image file or the validation process rather than the installer itself.

A few things you can try:

Re-download the image (it may be corrupted during download)
If you’re using USB, recreate it using a reliable tool (like Rufus) and try a different USB port
Temporarily disable antivirus or security tools that might interrupt verification
Check disk space and run the installer as administrator
If possible, verify the checksum (SHA) of the image before upgrading

I also saw a similar case discussed on Dubai Web where the issue was fixed after re-downloading the ISO and switching the USB creation method so it might be worth checking that approach too.

Re: Upgrade from 19.5.1.7 to 20.1.3.2 freeze at 3% Verify image

Asta-Noor — Tue, 02 Jun 2026 18:41:30 GMT

This kind of freeze during an upgrade (especially at “Verify image”) is usually related to corrupted package files, storage read/write delays, or an interrupted update process. In many cases, re-downloading the update package or clearing temporary cache resolves the issue.

When these long update processes get stuck, it’s also common for users to step away for a while since there’s not much that can be done during verification stages. Some people use that downtime to quickly grab a snack or check something light online sites like daveshotchicknmenu are sometimes used just to decide fast meal options before getting back to troubleshooting.

After that, retrying the update with a stable connection often helps the process complete successfully.

Re: Upgrade from 19.5.1.7 to 20.1.3.2 freeze at 3% Verify image

jennymartin — Sat, 06 Jun 2026 05:17:07 GMT

Thanks for reporting this issue.

A freeze at 3% during “Verify image” while upgrading from 19.5.1.7 to 20.1.3.2 usually indicates a problem with the verification step rather than the download itself. Here are a few things you can try:

Make sure the device has a stable internet connection before starting the upgrade again
Restart the device and retry the update process
Check available storage space, as insufficient space can sometimes cause verification to hang
If possible, temporarily disable any security/antivirus tools that might interfere with the verification step
Try downloading the update package again in case the current file is corrupted

If the issue continues after these steps, it may be worth rolling back to the previous stable version and contacting support with logs so the team can investigate the verification freeze in more detail.

Let me know if you need help with any of the steps.

Re: Upgrade from 19.5.1.7 to 20.1.3.2 freeze at 3% Verify image

Asta-Noor — Mon, 08 Jun 2026 04:01:30 GMT

We experienced a similar issue during an upgrade where the verification process appeared to freeze at a very low percentage. In our case, checking the installation logs and verifying system resources helped identify the bottleneck. It may also be worth confirming that the upgrade package isn't corrupted and that all prerequisites for the target version are met. If possible, share any relevant log entries from the point where the verification stalls just like call sms bomber, as they may provide more clues about the root cause.