-----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/jalu9uZGunHyUIFAmpPlkQACgkQu9uZGunH
yUJdQw//UObAmskGmp/LA7NKCE25fw661PkmAflUOke+1vEStosNN6+sV39tPI/h
zPnCqXGHYdWR7tzdzRMdQ62QmKNcG7L8GdveziOLLopOn/d/MGTfUcdCqOrP/wpr
O0hCTazZS/+N7IPNjYogKA9gx6PIpFcjDxd46PDEBN/EFDfCo3eYualcRIN0Gsmd
bKdDpnYm7D9pir+9GUbjbz4jWuoCpdXuZJrEAD8m20JtECg9aW50KEuejrnZxS96
YAFeejFWnllAI+eJ6zI0KCjRt3/Wbu0+df5DS+qHNyGdw37JexPGoU6FlYR5jzzA
hNdP4xggqMdU9gTefF4vtBoka5raaOrq5RufAG9NurrFzLBIMuHp01uZLcPidK5N
WWSzRsT7yhSasQIGja7JDkqcpKaaosSliss2/JKzj7PETL6ETtRlsncA4x+fpUF7
46fCdDo/8JoSYPrmOIHQc12SyxDe0Tz14FF1HwzKE0y1uBbcYo3F5qxU6fwB3fls
OobzZskdtPnbdaz5Vx0lBVnDA3j1Dbqst0Qrl1UU5Bm+Extcr8JDJLqtqpSb4AUF
OvOaK/iB1z8Yu9IDQgAC3XxuOTDK/IuSOGGNKxJvZojNY+tQ7KbKjjd6LKbWv0Ft
suZ7J2Y+xlxJhPr5JWSjkpFvk046fOaq52BG5XNHO9VRcd+R7do=
=wbDx
-----END PGP SIGNATURE-----