-----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/jalu9uZGunHyUIFAmlQrOIACgkQu9uZGunH
yUI06g//eAucjPuwmhJgoQ4IxNYOw7T64mpIOfeSO9uvnyb6x0XI/1BwTab49BQo
SviVaeOluqUy7QXx1zYRpgvX6ViIjt+p/a1XYbtXKjEcDO9dXZoER+mtwW3NQSES
IB0kmZ5eM28v12q5gPxQMNq4w+0IbABGJnDadB2vukj6X3V+GnwLV1+XcbxezY9/
gE5l0CNO62MhKAhKlFZNMsrylTSgi2jNIi/fB5Eg7hsORLSkx+r58af3QhskzbnL
7AdGC53/vVh2ndMG+nJwL4jGeeiSRitUF6e4R397O80HVeUTQBr7LS16/EIJeT6U
KqH/2c3R229Blq3ixudV4/Wru8fXztXSNbAjMPE9f6WIpZqSh6ba97++mAUxNeLV
SoUus4veCk7b1btMPZS2m5VyKES/HAMm+rtKuAMT/0wgQ/NeSb4aLpN3dLXIvtd+
vyvuVq6GlY98lZZujwoQD9Zeg3ZtWKIGmFi24SWbStvUdsPFyi3/BDJeUD4orX8Z
3j4lUBmUqNDBSsWpDXqSOKrgon8elwh/xSRTTkThtE2xX/G4sWXp4qpLcZhh0t2O
dvxfMklOdWn1Z1jLHCTY+iLLeEgYhPwVjHB4Wsvk8XNS8dqhXBkbcEyfq8dGQeLy
RRWWNDVqrxJZAQhpdII5lebz0PQbEF5NDkqv2e1iUS8Bvtloy5o=
=LTFl
-----END PGP SIGNATURE-----