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

md5:
05a39db99bef224495078c24db168869
sha1:
f72529f5f4831038b3f783aec8d5207175c0283f
sha256:
f37be6a7a14e63d2b44f67616c070b26b71266a3122c8e80cbddcb26f8cabdc0
sha512:
b152cb08a2cdd707284e19e5d50e22c2e0f1d00fa4aefa329c5b30fd7024ae01201459dfd77170f9f4f1f4c7ce3ff02191c0204cbcf55bf0e4e524e7f145b70c

Use https://www.quickhash-gui.org/ to verify file integrity hashes in Windows
or you can use the built-in certutil command as described on https://cryptostorm.is/windows

If you're concerned about us using weak algorithms here like md5 and sha1, there's no way to collide md5 and sha1 at the same time.
I.e., you could do a collision with just md5, but that would change the sha1, or vice versa.
That's why you should be checking all 4 hashes, or at least the sha256/512 ones. The md5/sha1 sums are more for CRC than security.
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEETYf5hKIig5JX/jalu9uZGunHyUIFAmo/JqMACgkQu9uZGunH
yUJH4A/8CrDactBZuBSq6M1I+URLkDuA6Gmni1eaw4xkWVq67IeXKFj+x0NKscE6
+AB4vl43Yq18a9l7DeS6fxuq0rsfL8SkmdViezNyg0djA8g2w7cO9ex72NywwLDr
9dRFIseXpR0D23XLnrYWPvLlpe7x9LTUMw2NfoaRy9rA+WP0xdM281ekpJ5YFfeI
A+DziwsAysznFmziQvT+HGoi+8QG+yOBIc8jQOTd4y1WWAPFJ8GDKYAW8VUzamMk
hzwCVe5y+AcmQLf9ifHsu35p+hwNV1rWv6QCA2TMAaXoD+79Y7alt8g+PMkRK4Pg
ONZJsufKA+AQ4XgdmFzkjpRekpuMqwoHqeXgOMYk12bXu8pMNIYSgUeQBVw4dolq
wNQic73OtfDkj/0mYB8joTIluFKgvU4qL1476x/jqjPDAptePbRgNQV0pif7aqF/
4FgiGhxtFb7hGvfoYy/zwFH//FtkJv1gp41t6C6dx3mbdNkri1dt0poNWvui96wA
ReYEPf1yWQdOZ88H1Yp/MIY76Zg7U9zY5/vgG291dz66x3aFs1j7B2GTkehE8TnC
SCbx9VM7vCgBSJTfAT9RSxDzTDTpUAy4NW6tPpuUg4bYgxCvnJkHsb6y+EfRyVsG
vK7V+i5s7ZvIfuOVLwKX5V50kUvresfnzu1JZjfvPaiKmNW4Iag=
=SuFw
-----END PGP SIGNATURE-----