-----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/jalu9uZGunHyUIFAmlwbI0ACgkQu9uZGunH
yUJK5g//XzFWtzS3M13tdXEyWNTyXPHuxH//QjkjojOixGfhvvvfmHk0BfNjCtPp
eyQLpSF4SRItcGCn8rIruSY7L8YPwHISqYqcwFwbKDXDmnEBujgfBjDq0qCx4SZh
MquboS2/GsY/oOnroLsj8KWAqA+yDumKQ6uYrzBE2tWrijyruC5cYZh/zXaHrXjL
ht9Jr7qZXIo35OMEH5oLBSni/VUeMtkZ/7zAbGrY8GXnjq/c2V5gS9sArS5ltdXR
x73xkxO7feNfTohI4QfPyIWA77zhWmd5K5ySCZ97jJ2sCUJ2wBfvul8T2CtSUT8j
7s35QhVVGW7aZGyvO3Xaipfj9k+LTuECdEbC+oLinn71FJm1KVOj42BgsDqdo2n2
BBMjKPhYkvReXi3AyUsyt7tZmmTkH2P14QB3Wb95/++ZQC9g+MNrdF52zsVZ66R3
dCSqUcghynBEgZf2I6LSEFz62+7XN+CTM1koTVnFuB3eLVazqTq8R1WG6owbYbjA
K4q8ncz6oR3Ino379boRcJueOxvy8t2aIwjEx4+3sy0rrTVzUF6Q/obfcWPoXlf1
WHpq47GHSOSPMIEv90u0NtNsif8FDO8nR75gxf6lTsoil0jt2eBSiq13m3UzrApz
niBSwu7fNmff0JDEZWOaonAaktZCEbthyUup+OF+crWuEXl/B6g=
=WGcj
-----END PGP SIGNATURE-----