-----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/jalu9uZGunHyUIFAmkoFsQACgkQu9uZGunH
yUIV8Q/7B9CdVQ79QCi0T1E3eIK4caKHKsvtSkmTI9rYmSmmw5zmAG6/90DryqU6
WZLOkxUM3Jsu1gmaPd/BFSn5p7VJTcQ4tiByphtldVOtuqX1rgiCDR3+JcpJzYfm
Zh9lu/OZE5zVstHSLf2KCS2nZfCwmRQCUw06lQIW5UwlQwEAvPKSakP8WKqUn7KN
oefqc8BzUMv0PhHWPEqrnYI8+RlghsnqEUBJR3K5PKIDxxGHZ/PBpiJ79K8HZpCD
TeHw814VznXb1rAmezwVnxwqszNBnWvBlLoqKk2IIP/cumXVijNRjNcBQo63dYoz
Xh/knq6QYgKjuetMkC00Oqtg/iQzx4hpLVXv+ZBi9cbF3pt1/TSq2ZkzyabRjhef
Gj3M+TPbGd1+x/ceOjydTSr8JXGRsGqpuYQF4+PjWYdYMHqHz1pPF6VmlfzewsP+
Amm1FAlN1dDDFNaVjdD+Yxl/HdQWuzKr0MbndS4AVTYjz/2zCkr8fDMH17qhtKom
3fmd9oQoeKK+UEMZqCGgH4pZvKE1MXYqOztAboU3Qp8ttQF6R8n2o0MkYlgraoLZ
0o8wfhIe5YjKBqg5RJMJCl8e0pPFAjQfGgqVj8d+ilcNkcPeuqMwbWjuP06iKmi8
vxcOkxUg3//ptwlf28UxICTCO8XkVym6/IKFZorwwyRgOwEyP/w=
=nG5r
-----END PGP SIGNATURE-----