-----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/jalu9uZGunHyUIFAmnvZQIACgkQu9uZGunH
yUJnqQ//SeGn7a7tD4cMeToQ5Aq+HhniGUTCK3/0Dzm+aTgTd7btCc1n0GpnTlKj
Z8fO5CfcXmNhP2KCfuiLhVemtvf9Bcm1+0VNfw5yGC0Fk7XvvJq6pdDavQ9kmEYQ
qBPLJs78cgH/aFCFVs6MA9PW+Bxy1CnsReHVDvas0E+cnmogfJD+rzXPTA+Yyu1T
zwFAjeteuwHGxVcDmdgGRuEIor9HVtBM+Sw+pbNEP3DvvoVMhb6TFLaPN4Qx+i3n
dLvT54UtCN0w/rQTYtjVrzp/n+T76rhXczNpmlhnzi/f+bxWSoPgwivZm5cJyprE
v7tkplNq40XudK/x6CSa5EO5SVecQAJmlqxEZ87hPv+LTvPmFTXdX9tVDEbHhsR3
Js64aD1IHy1fFaS4PLHSQi97m7bc6N1aSXVlcxGJloTkElJr4VplqIPSxW1YQx2m
7ke7m74QhByNpFm+mfHZjGolgPTHV+FkoJRb1cwXOlExTGeWFjP08B5IbzSH/6UG
HqduBXI4tZ7obPbw8S145jBxLbQBNd1zO/8UovI/gOek16C1HpmJo7brUvN0ca/z
dll1xHW77Et1EijcdWfqaw1rBKIM/6v5r4Qmy55Mc56xPSu9kCWOZCTGQQo6jbOV
vPoJUyDemYUag87EtTREKhmFjkA24Z4+1ADkWiZ+/No009B/8FE=
=t0uR
-----END PGP SIGNATURE-----