-----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/jalu9uZGunHyUIFAmoqgNEACgkQu9uZGunH
yUK+lBAAqPepGhUpURKA+MtxmIzWpnPmQhoAdFPdzD4RxiNJ/A4M4iPXYoDQr3eQ
beo4fyC9W9FbLmQaCghY3zdtHSI3mPglqw/Ms6ABBHQX9Zfg2PyLW0kL2lwPdqVD
dH6+1epthasHMd/1MeBMEiOYi0476DrHn3ruIHEIuD5VVImyNwz+TmickcrqH1So
kKbQFGgHkX5bFySjy8Ke8TyaJI0RND9nwgTL4IU3xqb+vOiPvwwVFuRFa4J1ahTU
rjU8GVr6vccrNscQtsHaXOSHuWEq9+lpFyFOI+u+kdDX9IUFmhvE4pPjXNnZx7FS
2vMaJTSGEDwMLB/Dt15ZXvwZspP7fwvVkc9UJ//5p142CIpu2whNXylnte2qGKAp
SDP3/3o+RpVkyN5OTjDpxce9gN9bETPZ7UuxSMvS2UEJXhKKS7DR8B2jBcLGGcer
o5h7oN5fpAbrFfN+WVJps7bh8dHD9Zou6uixWfEme1TbCTIgen2NA9dIutXt2L/m
gJQbMGBe8XMmp0hapAOjMAmBE7sjHNVGNX6ZjzARWZnEHnXxHeh4KNDAxCJKKQu9
663g/APSuqRGUFkHG7wnxyJ5xY/uUsSvQui78N5ycuS6BUqTT1pD9FcSu/f1Hl4+
nzNbtTENpAiBKF81TWhPC1x7Up2z4ilHAibrmQQr3igkgiQ8IK8=
=MUWO
-----END PGP SIGNATURE-----