-----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/jalu9uZGunHyUIFAmlG7UgACgkQu9uZGunH
yUIaXBAAq7p9k4G4qtpxZWvj5QYeToCgN6QYetg2i8LrzbJ3fYK/JfXj8tO1nxkw
d1mYtPZm8ruAjlZReKosmBpoXLI4qO78Uj0qtnek3mMzBj1Bdw5U6JjelQUCzQ8Y
RvcYnV2glPQCH2/GnlCKoAA0LXz+03bgtWWWp69JNSWuBSLRuVrm2q8igx/eMeZc
RfrhXz2rVeTSONQXFO3sJOREOT8fU7l00O1tPFwV09awHjyIfuEAOPjK5kkvni/S
mZWhuJU54g67hEkf6mW/pcudvNaQhkorhKLEO0lscU3d5w/O82Id91FGkhF/Pudk
uN12Mz9xDHT/ktTqM3jos5VmDARCABdd+xcLn6MLO2EAc+ZITgkYQwMZegsjpa24
qkR5geISvUcvr6x0hlQDuGIvoLw+of/hXYYG6hwjA1mzQSBDzuhXPZ2Mq+LfefQC
mwpUUopCpAdBwMvT+7HJ9bd2ChVlhU9XU9pRTTsb8MgRo0rycAq0iNpuJZVBKvxg
NFSI4J6ve6wBAr9gjhfTQMreEhq/LITu+TaektUdlXfpaUriaJsy2F6gf6HOtzXz
2e3XNjhhJ1bHbqZyoU02SqTtVivi1WpfyC+uo+80s/z4Mc8nrHnA2z6LW6wFnSRg
TBTHVmLdIztTYsapX9+3/QVP07BSUFv68lPokYw27FobBv0UB9I=
=GF1m
-----END PGP SIGNATURE-----