-----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/jalu9uZGunHyUIFAml4A0UACgkQu9uZGunH
yUJoJBAArRhDf+ujN0XKksJJ6gohQsTtMHDkEt/FTTzzXvN1jpYiNmpF2Gitdh9c
YiAJhFp4tNWM61FgpzyTTSYvNeatKGZhlTWCl11hsqEtDkzDyefViO06Uoccw0Qg
Q6nc0f7kU7wQEJX2PuOqLdmGjjtRrnsqorxSvmBtnm7oEEY3b43369OMzAom+S18
dVMLBIKyASkMjsGLVlplcHcpxohevsaIk0L8YZncxK2OaVY1afBmWjGklRAraqoa
TRss4RrndTLudtGed+aadiso/t2Psve4/mGRhkqp9Bam7OJ6fnTGVtwRp4VNA40y
PknFClTVMo20Pw07qh9H+DqUJWebLGd+7bgUN2x70uYTwFS1i3QSW1dhNs8xQhgx
caRMqssIA7ZUY1TulfPcX8rk5bgSb51cYc4KQzPY5c84ic/EjWWfVdcaJCFI87KL
14b3PVTegZJpbmWIjFlNYWPs/WbjOPp72sJ3ieoaMwjOp+EYPYQsiKkMfL9WDrPg
J0B1/z/7ccodxaLTI/AhQaunFDZ0NH3CQ4tgJ/wWm4xYKoidQGSRqtAkx1k2tRDL
hB/sgKrqmDTuUGmjDnuxSg4pyk0Bpz578lqzbwV/oxL81ymghG7JjQX/O4WZpL0r
smFy11N+0eVpPpoWFufTlQ8DL4SF5d0yjpUx/GheeuWGtCn8xow=
=9bv8
-----END PGP SIGNATURE-----