-----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/jalu9uZGunHyUIFAmkjuSUACgkQu9uZGunH
yUL45RAAgOXNpjY6GMdFIPqpB0DPiGrzOfXJ+4LJz+kyEcHO98ZGDlLyC9XNquSn
Dtp3XU1n/hkyYihvdZXr+9MkZAyzOuPLNBXqupGDiLfkwxSQeyHsylh1G2AqzUn1
xZ5Kmae1VluNxmp0rdb6sQFuyk4eavTLB0lzeW1qLRj2w1JX0I3yyTHLbIGF94AI
HN/UKMWLeE5NToJZwBtpcnch/Ji2ERTMhnXuL1Eg5jkd+4Q+baQhcglJA8KRwPi1
nU16pMauAFBbsAshWjok8JbYAfvSjMJa94OIJHt0JZlXc+JMbnpoHP++1FEb89Tx
bcmkBtrAvtYFzWyvDCg9M2V5ge9oj2sIj/MdqMjlSetHTY0eU3CGBuGBaRUw1C3Q
krHL3vRc+uAoXzgUhyNIIIEKlhuizjG08GXO13WaSUPVVxU91ukniRk0GNNXyaRI
+UYLNmXX51pC6OlAZXprq/16VTuH6BGRMBTcN7N9ISEBl2qjRVJpntzWxHBLKufY
kkGs8yygEUd0Foko479nI26GGF1JuQh7IfX3TR3zT2eQAa065aXcB77zNQJgG5OO
6ZlrhnzK9VkAOCvL+65EHOY4RP26QLVqWT/6R456CkW23555K+PzowosUXCUcflb
KVncfEOOfs57v6gHEJiDbTONmsZse64DF6wGJFo154Er787io00=
=HRJG
-----END PGP SIGNATURE-----