-----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/jalu9uZGunHyUIFAmmdVFIACgkQu9uZGunH
yUKwNw/7BC+vgb//XqsTPcGOW9LECwtTLf7P2uZ6/4soorDKmFoJF+Bd+Jbb7BAF
+eVvLYBxfMyiw0pF+MezL9TaB4v9Kf85w7hOqLekW+LAhl0JSjs8S2ue1lxIIPSR
yAPV900iHJG4b75nPyWlBrvQondHrc+KM4EvAHL69piLja4NNo8f5oL9SjYPdz4Y
Hc3A6B83tX0o9WdYmv17fb4f6Ed7KFoTQM1Lp6REcFmAPhlxtn83iqV+B8pkceY1
PfRoJoFtLVYadCgG/1zAOAu9NkIG1jU3KrG1YwuA0nBzZYWwEMg3i+n5I6bFtFvo
EYb9upWAUn9v6vzHsQ+9bVAkqKpRljXnuTLLVkU8vU3bM5POFsaEEd+40xoiVpw2
0Myysz1syVf0dFwKWsUK2R8P5ojtDWYHDRdwXK2jWtX4PIptdrGyqH16WbDSrIbp
BMdJfK7ytVw9SHRJOt3ZjBFjcnnXXRBhuauOuryDsfD4uwZgbkrneBGuTWLkPoNu
UJPFKcz9ThtEMajMrQBVpeZ1va2vOBtTNnROUGKUkTbRaQnnSr0rCTpVE9mMmexh
v51fIz7Qlwz/O8mjpu213wHLjloGsjC203TB/+KzDcMI3uS3nqE+OHTLhRiDzEOy
ivPXITaUSoY4p6RNgwrg1RV6Yahg4fjVGz7+jqVyjCUMiJ5/gyI=
=0nhP
-----END PGP SIGNATURE-----