-----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/jalu9uZGunHyUIFAmm2oPEACgkQu9uZGunH
yUJBPBAAraPRpzuOJKSZMU8uIGt8FqBF/8SxCDgy47dA8hLKG6/BRM4SGfbkMokp
9oDCFIc4K6Uvp6gfVmG068bCpVlvQrxweK8yQRw+DCmkHIINHyDpZXz37V3QuCv3
q34p8CTxKp3q4QziKfWzmUzxQwscqiAxZstw5HlRPJlrF0GOidSJsm0zWEQG3IIL
DHJM1KiV50oC9PdT76FmP/IBPWr5JHmT2oGvBrFvCFluM4XNs+E/IrzGprF4Rvej
0sfcS/+Ni/a5x+qAYBBESXqsEkT9aUBFFRbRc3vLK/xeD58ViLoKxmRVgKO4iUCv
SWLC4MGya7ZJLPcPdGSV2AlHX2/val876dPKUj8b0/udCSq60clYCZbn6z1gSI5/
j0SQl3qmMjzxh65QiUn/kM2/1hBLy2je1G1gN481klueaGz1hxygfyZSbj+0CmBS
56D1hSo3J2QlIpvGBsckREkQlYzFUaD6M73BIqqI/5iidUIbfT5LdZn6aXFcq44w
v3G5Yg21QHQCe+Zeng8BZt0vaTkAW39Xa+Ing+KOoMAQ1atsLl4eFLCKjGsyj31t
8AW/g96I0lxgSwvg/Ypugp7grmPfjid2xtlgQfcycF9MDBCkLXlDMPR6HOahXvy6
zBBc8I8N2h9xJQlFyqmXBSy5b76buBIx9BNc+gvPsigSer5HyX8=
=Tkk5
-----END PGP SIGNATURE-----