-----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/jalu9uZGunHyUIFAmng/xIACgkQu9uZGunH
yUJyOQ//T669aoi86452HgE1eb4net9NGJoHLlLgeMnZVoaM/Pky8Il3Put+VDDX
NJl7tP5IMJ8y+osDLyCMG4ua6p96Xwpq8n/sH71gB7Ja92ZpPF/Qa6GUiGwHI81v
2vUeJyF1HciJKL/DdWjBkwWZtKH/Uk8EjUII3N1L3DUitx3CohsG429T4M6whW3h
Ie7So4uKg9CIIgqA89Iaoh7+hTHqTLQ2FTqjHbuf8cHMHHPZsLDHxxMdtyTx64wV
tfAvxR2SanPzr7xp6NxoJtwYweLwAq4doKMG1R8Ib6ii4gYP9rhprU9J2YFphpca
qz5WQsMmo9duNH6We9ZsZiRph1cgufaKib9Zls7JIsQ5vwmgiGA623urgACq9CrG
RoTfyI1hRLpwfjFv7z8JiePvIR2nxJ7yNngWHdRJBtMFqWuuERHUlpogpP6MnP/8
o2ZHKTsa3GZBbV9TlGg/PEsNqrBi6Ynu7BH8dox7iVTrYdPmLkahPKW7XTysuG9/
vUpwQ3y6qwS0jY0rejXMm/bqqFEv8PrP4zg+15H4RzeiukA03flRBvD0czkrmdCV
YXUECvAE4yEuro5KIWPGt+XZNf1gRXFy3RAAU/HomBN/0fqGJbd0HyRcntCumlgU
myA1sw8oCXKRde7fLme/X1AKVDCBmnF4X+0vMaqKz65VQk4vZME=
=NNBh
-----END PGP SIGNATURE-----