Just installed Parrot Sec 5.3 in VirtualBox - won't update

I installed ParrotSecOS in VirtualBox per your own guidelines, and gave it 8 gb RAM, 4 processor cores, and a 120 gb hard disk. It is configured to use my wired connection. Trying to run Check for update, or trying to run sudo parrot-upgrade are taking hours and not updating anything. My speedtest on the VM is showing 96 mbps down and 22 mbps up. Thinking that I must have done something wrong, I deleted the VM and reinstalled it and it is now even slower. Should I be trying to find the ISO for an earlier version, or is there some reason that this one won’t update? The screenshot below is of an update that has been running for 5 hours.


  • ParrotOS iso in use:

  • Application used for flashing the iso:

  • Logs/Terminal output (use pastebin or similar services):

  • **


    **

Yep, it’s the “sorry-lory” upgrade. You’re lucky if you’ve got a working system. But be warned, not everything will work

At first, I thought the problem was installing Parrot on read-only media, which is typical of flashing an .iso to a USB. After perusing recent posts, it appears that every installation is problematic, especially with the new 6.5 kernel (Errors on upgrading to 6.5.0 kernel - #6 by XBo0t83). See my post at Error while upgrading to new release 6.0 - #4 by Parrot_Live_VM

Fully reinstalled this morning and am leaving upating alone. At this point I have a working VM with no issues that I have found yet. It does seem that the update process is not going to be an option for this VM.

For newer Parrot users, this is the .iso downloads shortcut to monitor for reflashing your installation: download.parrot.sh/parrot/iso/

BE SURE to validate your download with the signed hashes contained in a text file within the appropriate .iso directory, e.g., https://download.parrot.sh/parrot/iso/5.3/signed-hashes.txt

Terminal Command Example: sudo md5sum <path to your downloaded .iso file>/<name of .iso file> (Be sure to get the syntax correct, e.g., the capitalized “D” in /Downloads/)

┌─[✗]─[user@parrot]─[~]
└──╼ $md5sum /home/user/Downloads/Parrot-home-5.3_amd64.iso

(This is the hash returned by the system for the file queried -->>) 8b4e423a97217e1d06f7244e3db5fd49 /home/user/Downloads/Parrot-home-5.3_amd64.iso

Compare this output with that listed in the official hash file listing that shows the particular version of the .iso you queried above.

Note: The sudo command is only necessary if you are not logged in as the user that owns the file being queried:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Parrot OS 5.3

md5
681f690cca8fc15be94bd3c712fcd474 Parrot-architect-5.3_amd64.iso
a8b6f87031e71ad436b1d6888a82d4ac Parrot-architect-5.3_arm64.iso
ee271161083f5c3143abebab82d1d33c Parrot-architect-5.3_i386.iso
8b4e423a97217e1d06f7244e3db5fd49 Parrot-home-5.3_amd64.iso
33c4ce83eac8e3b58e3c3d3e09fdca11 Parrot-htb-5.3_amd64.iso
50e547aca80b533d54bf150db9d1e250 Parrot-security-5.3_amd64.iso
88fc8b529a8df1bae19ca7358a2382e4 Parrot-core-rpi-5.3_arm64.img.xz
ea11de5e92ece29d21943a2f88c2030e Parrot-core-rpi-5.3_armhf.img.xz
4e7a73ab3a2ee0f06b9ce02889eb402e Parrot-home-rpi-5.3_arm64.img.xz
da988eae7778f763810fe2f3dd4a70d9 Parrot-home-rpi-5.3_armhf.img.xz
dc188873ea2c97f672425d0476b2f41d Parrot-rootfs-5.3_amd64.tar.xz
50c3fae952ab0960ab631e4ce59fed11 Parrot-rootfs-5.3_arm64.tar.xz
ff12bd3c4eace31434dca965089b4924 Parrot-rootfs-5.3_armhf.tar.xz
f78609812cd37daf1795452429b306d4 Parrot-rootfs-5.3_i386.tar.xz
7875cac906a05c4e59d4188818efa92b Parrot-security-rpi-5.3_arm64.img.xz
768b68192d45aba08227eee7f22f8231 Parrot-home-5.3_amd64.ova
6e05199417d5c1a053c1e33601a088da Parrot-security-5.3_amd64.ova

WARNING: If you did not store your custom package selections and settings in an encrypted persistence partition (which you have cloned – so that you can clone it back to the newly updated drive (i.e., reflashed with the upgraded .iso)), you will lose all customization, including personalizations, like display font choices, toolbar settings and background/wallpaper settings.

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.