-----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/jalu9uZGunHyUIFAmmv24YACgkQu9uZGunH
yUIu/w/9FeKl7QVpKlR6Lg5rNqzpmOWgo/GwccjeWeUB7Ut2NUIib9SA1LoyQBek
NQnLxx62iIAAywS3chdAoV0wY8awqDRdO6eqWWwqHgwahA1yyF/kIB1U2L+OiXZY
b3GLBCRhkV05FO/k94gBXScZjdTDzbEEaiM4aOu0Y6j4E+HuGRWmCrMu3fFaOG1B
hZgqvOmxF96aXKZmxoyuGDiMbE+atla6p1sx+Hu4IWvxzjgjB0hwhEZA7gf+5dZO
kplaNAn6JQCxMEdJ8RqB4H21PaoyyqCYFT53rNMt8gpqXbOK0UcrjdLGIYVGRcvY
Z9G+UJeey/IJ4O1Ie1Dwdfko1kV0pDrkWLslTIZ8RYEi37j719E8FtY5dzceljvX
0Y1JQ/MM6WNKqA1hMAS6lHwIRafgBLRB52MtzRkgfYis182/bF8b3XVeuOxHycv/
NkoehcXC8UxZaKPT+OXdtOAOoNPCZR9r240p0NxSvUVoLwxkTllPoYYDFJ7cGoEB
uW1nxVotoZUKWid2mOg56Fujx0uUHUW4Y0wc2aZomxKe87kBRux9cG+sx5uy6IfU
njP0peGT1erIop8aAvFVTlsRTA/46oH6JAOc7gTJaGLfnf2OWLA5u6r79n/yP+Ru
+cYbXYqlTo9MEVPGXnqrqerGjzt6wFydXLvC4YpyYQFWmAodtzI=
=4xRG
-----END PGP SIGNATURE-----