-----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/jalu9uZGunHyUIFAmn/Qa8ACgkQu9uZGunH
yUJ+dQ/7Bj2sP5pOPXXf6/DhVLuMb7hM+UKcWYu/SwEmmFcV9xkm0tH1VnZoV0eF
n5KOqONzl6fkuO4JqpXZBn8OjjB0qnfcKPJ9nqvUKheAuQoWsVq4RR9RBa8XfwoV
Bp7o4cUU5gw5moE2SH8P3tzuK0bQc2oLkE+YybBn3ab8liRAs02ou0QTYv0g3zhW
K+pEhAfR1tl/xhEkHVUZRbqn2E9W6m+DcpjZsAQ9RkhhSCFkf719BDyClbY7VB13
xiYLoGXIfY+CSn7+QlbEfP+AeRm4QMGNynOsCB7ESdbOnesTVqY4mRDpy1cjFBUH
FziBOalxy/C53i9vOh74qwKDcjxpAtuUJbX1eGeHTQ0OSvKmdsjoQGpJC8JURdHQ
PAwt3h/1BFbraBDjkjr/8yBWZe/QCjyW2lLFmGXMRyco21DShx2xF1EPJ9tT3hWP
eBjNHJin6wzyz2adpwwi9lR1dqQ3hGgWwgV85BSd32FyvL0iODZGIc/SKx+rT5Kn
pDMODPrOoa6H8mDkUL99/DYbECZfmm4/OGJTgMa3lSg8eyRoD9prGfpOKlMl7gyD
pZrieQea0lB69hTqSciQ8AAhBeqXRFY2w/2spRtBOioy9OVgJS5aUE33I3m/Tstm
kbywIExbNDljr1HEWsXRb8WMBAblOsLpzvfpvIbEi9t6c5Sz5Us=
=UUsk
-----END PGP SIGNATURE-----