-----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/jalu9uZGunHyUIFAmo8bFYACgkQu9uZGunH
yUIoVg/9FOsatOs8lrHWoWcpxbQZ8nsjPzDVvxPd/f5rRdconmAtSxaeVIQk4FEU
q4lFyzLY7IRA+IHWiKFKg5T7326vH1Mhg8nu9nNOyc+NoinhTI7nFDdbcWGWp8BY
Nh82PCYdy6r4iMaMuvU6Y9N5JIc9s0rjE9AI70lEA64Svz/q5qF3i47fu42Iw/vH
fAgEV/yrxTOqPzC02dtHuFk1tsbk7UXG3QPLvQNK+pdh7/vFsRPztfmfpLpkuV3A
o8BQ+XDpe1vwltaUOX2Cs4agXEd8zP2gewyvAMTPcOcz8YTIWQov/CMgcAPajfNE
sKPgQQxb2NNVhktJa5dARpfiPzHJDBp2olQkns7ZsjZZHyetGLYIoQ79j+f6GQZ+
qZvDqQpHOXcm/pLCxixkjlYUdl3+ZoR5U50ebbIQYeGO7MqPyGYMEI+SqulyrUb1
HIiiHre97ZF9KwCgCPaT15YkTx5OqUXxy7UbIufc72684evzW8iBPzcrfsDhlEA2
dNCL1rVdukPEB0zSIOjjgpKHZA/0nlpXbavLHzZO5sRl7d0QHEb7ePgjLe0LqilM
BlPkJzZJUnsIs+b+eb2QmX4F++TPQpGhGkmlobZHMQifAqOECPbLwQ7odbIYJcsk
nycuZHXY9udHv7ueB9Shx7w9BgKIjgpQ0V8TyG5VsNZL1q5syWE=
=rjPQ
-----END PGP SIGNATURE-----