-----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/jalu9uZGunHyUIFAmmuiugACgkQu9uZGunH
yUJiyQ/6A7AY91Mv0CiBdXPylVLAYcAt1BTyhpqDarCOtXsRb9URXvYA6FAIVlA1
8t5EVKaJXy+F5yBUbyHbLhExDtFkIeSKPlExe5f432PyXaz16li6gG7/DJwA57t2
xH4ZN7lXGhDMIp4pHelDyIKNLt9VlXeRt61ojYXaNgNhcJ89gRm3aNd5O5Uw90or
1Runctbyqify1qYdNHcbpA71V++dbvfb3gDDRhCtyKhgJ3tjpVj7FqV/NDTsRtHN
Pw50LiT3ZiTyv4FU9+aLNfXqR38eA6uGUMLAMGTox+TvkSrCH92oXgk263AscoyA
kcn4mfdSudaThaH5PLaQVa/0snNbd7pG9RMPpzx9zWfkr1nYgC2yVOXqFeC6G91R
ZoxUxhfQSBZPH0lY+jr3ycH2wumdBGQYMwAWsJMPrrgPfW/cXqMjYbZDMxnyT/KV
f8ZXuuRDA0+OL80p0xHGU8Oa61FCZznNQ0ydyj7UGWP8X7XTYPsJYLqQvnRzPvG3
18x4onbY6mIAi2T7xcJ27ZblVGDxOnkTZvXe2wBcJXrIl48Uz0wqLeLWr3necTOC
yt7+2fKYOe726/2dYLCp8LYPPAsUFw2Rstc9LV9FboqWkCqbVQOd8SWqTjOdonqI
ADEatdSbnXgHZfzkHCHdfWZQIN09SdQy8AWsRvRjPMFXygWB3IQ=
=Vvyl
-----END PGP SIGNATURE-----