-----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/jalu9uZGunHyUIFAmkqGK8ACgkQu9uZGunH
yUIIIg/+Oa+FEucXoyeZHGYyf2GUMM0AfRP970+NTnbnIiOkplhC2s7rH9E3HHaI
s1FYFFH/GLX0BsnMi1cs5JpUM5ho4d0uW9Qt47Ly3Q3bsHszbTDnCevXmdnXz46b
HeisQvHGPYRCP3+lZhGUKcSPGWJHm8KbpMjIHhMkcWS5CDVgsDpGGoDWBWwTbF9O
jHwzamPhL8QrPtr2oq9sxLTcFsbV3kn1EJRQ4AiPMlPqWFxdVn1rHMWvQqVhnbN6
qaGQXSajxg1w77LMV0CMfkAXSup3HJp1SDRaJLn7Hz3SuJSqnJNky/0LwowfdV2w
PqNgG+uFJvJrIhHj70dSGjSca0Q6YEVmEmgqKt93Cb5OM1RziA133vbaG2oacqFi
bDbZ6plrq471Ui9GmnZGnxjTq+czVERqJD7JUwuCc6r91LJPq9P5psw2FTgGr7Xf
4GLxpsAqx2hilDVPXOfc5xGXe8lqqLtqeOb6roBZQipnuMczklKXUI6scccuYB7R
YrCxtA8FJzW/upH0oE+JqBv5VXDUt/1iT1kkApeqp8asZSgbwThkoaC3SWxgT//0
8oZwPMDxjPFeJ6IBVWrlG9du9+OyxHoC3HtOqcpxYY+EBhzEFj6Uh14lBxahjKqO
Cnf9dGhrth45CxHWLSgh7NvV/bzMP/14pzbyXW8A6eTbkfwlSpA=
=LZOs
-----END PGP SIGNATURE-----