-----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/jalu9uZGunHyUIFAml/8UoACgkQu9uZGunH
yULhNg/7BkpW1OvVg4n5A/JJPRR2yszg+0ovySIf5DNK1POhTgKvv7iMQWbqN5oF
wnYC2D2AFAkiiwarL6OIcP6jJi2NH9avo1TFxvzY2lxlqDUGqjAEHwjDgsnEcoq1
GvVHjQarU19LopZw1HmACa+lynw6XrP7uQf8BygtEvx1aPEDpwvXu9vmN/+2ZDWt
Dkxvb609gC1Iq01K7DFVcuo8HU0s76f2s09Kj5TeSVx/d45ufd8L5In731A/jpwK
hX7nNU1VyV3NsC2d8nLgWkc+0h1RpIzaELonO99sAbiBHpp19Tu5oDnaq/B2KHUQ
xjiS1LEGDuGio7uvDwA47ORCQYbwtxAIQX8pXhyvLGU1UIuv+wfnuLlfIAlnO4fn
bpGxMmlaequvdXCrKzR3cyyMCwCUkQOJxHjzfrT6QD22SuXtFmaoEmRenVo+bqZK
1JnhUcmgL6gKdC2gtsVpNnikg+5psllcChOiANOfJZQaJQ9PcIfTGxygFs3KPHfk
MXOq9x0aecXhoblyukhbfDejEQmYwAaP+ZvkhYRhtpe8Z/EYgFvxJYnbfe9XZ0V5
YRehorFq1tgVsdX67PFeNs3fdrgoTk8K1G5hQET9aPJTnXaqfAZClDTDTjnK3KTY
LoJczA8S2Gs41jc55g4xnVcB89Ibr+buKbL2z/Yn28sSWIEUQf8=
=1Mst
-----END PGP SIGNATURE-----