-----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/jalu9uZGunHyUIFAmkrbIcACgkQu9uZGunH
yUKw5Q//SF5RprLDhW4P2M5e1vkLqnAy/bnvJairptue5Db7q1NBX6Bz7yf2TYtb
e7Q/E55Bm92jb1e8U/0N/xjPA+Us1sD2aQmtsw+/gfmgAepP6yPqqzFr5JQUxx6q
61/iDtwZVd6Ve4uE9kFNhf7Ra3iJjEtaT2F1KuvS4E6KZ5wdj6B0mZKolxLn7fm7
pmKpsZHZi5MwJigTYlfU7hq7PMSL1iURt4//v/xp/YOCD9BVflQ9+VG1ttBzHjYP
d9zj8tnVdl2qMV7MPvk/kmdhFTIQNvNCZGrCA+hS+g4skvlci0P9bZFuR6zZ2W95
vKmKjXO0S/3T2r0/A/0LDkp9sse7J5TI3CtXXRWYxSXzFil0A6pguF64wYeCBdR6
pi+a3eh9bnW4xMr33y1g8cfq+4tGNkco7OG94xZQR618Tkh5HVRhRF57/Yuo+VBP
Gr5L17jO34oLGjFcPnmyrq2ZzcuJgCw/y7Su0aJU1R9Ko3c+blu+8g7NU0y9Yvhv
U4cxbU0f5psqsdmbcJA2VURQwqE848U2dfYYG+bEdArPrjcksk7vtL8HOBnckjne
cJ8BK82Zv7jMKosr3aVirAo5QI+DYqKubv1E5JwQ6ugnaVCpxY+go5qusrBokY6E
vOdm1+v1Uwb5JblmIDTnqpkiDLiOF2Y2rqybs/AUY9hxF6EGqww=
=MLeM
-----END PGP SIGNATURE-----