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

md5:
365c280c6cd21a0a0f1b7b1e47cc7e7d
sha1:
1c33f9a2f49d36677e8fa9d5e22de34d094b7534
sha256:
afa4f567f60fa5cf2ae4832c50f475cd98c79d40e8d4479083139ea7e53a8b0f
sha512:
9759cf59707b7f6f315f59661c48d8fc147fb3b50c65ae4ffb2997563bc8c7cedbdb65639fc0fd7ae9cfe849f9bf3c9895cce5de5d56335c7920db83a6763930

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/jalu9uZGunHyUIFAmmDVwQACgkQu9uZGunH
yULd+w/7BIsixsHqif2E9z82H5/mPmd5K15qJaqYSO6Y9UrGSVm2pNrosrR9GUye
InUbuC6+CS2Nhr1SnXVwzkvVM+QzZgmbnXl1fLm1gIBf/rqEVumKLkdYtB4yIdWH
FGeq+EKEzQDlSvxF6iQ1NaXPLMTkbx6FNdE4NCWECs8KexUNuXE5f9vNJK6Mxk1B
9MdMc73bgLGpyJF9M0gs7W0MeAxDypwSSC4GhF0H0F4ZbUm3i5ZIObS7zD1qHGwS
4iSnkKRz4aZauH81hAC6A+bbC+5B+XR6yWTTLdYxhHGucKh1VjP0yspu2RhPVUHA
yR4AL2jye7KYenkZjC75WzIH7WZnW0dy8hDkLMFK2SnVSNsfF51tq90XDsPrIRa0
f48x+gXEnwyJWKoq3LCB+v32voY63zHm3fDDzuYi2cIgUcs2fKlpwp9A2fGZShsa
WTfpT2IJmG+fLySu/LuZS60+h8wX1buSmOjWh/bapkI9ItG3XC5vNQW21D4pTJBH
CX7RLuTp3r8fMEZxE3KqhvgGabW7TqEv2IxVC51jjJp+RvJ5n9bEXGPT3iZEuBI4
9JxvIHz7rrxXDrxUgyaHfpIS5xksEX0YyASPbx36xX83yC4DjbWeQNf7M6YkAest
mNuUINPvSanxBv3J0JZ032rhoXYYPVqk/D6lHWT17FHon3XzxPQ=
=E31b
-----END PGP SIGNATURE-----