-----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/jalu9uZGunHyUIFAmnUN0sACgkQu9uZGunH
yUI0kQ/7BP4kafjFMHYj0/Urae/JJklZIfUKAjZH67/KnM5BymYopXlP2WTZ+rUU
Rw5II+OslVoh7oAD60FThZGlTLK5me77fe20+voPO4Fkb7ZLdryD4Iz9CV2RA0a+
0f5DHS+37scDAJf2VpRmSVB2XcgrZmQdTL4+qoqG/UfXVfXuoXcxmZLzYG4W3/b+
KnmBHLteX8SytyJ/5iQoTBQ7Qk5eADFltgQ6+tFe43VpEjwu6j841kveUDmNinnc
EJ3Z/RVZL0fahAee0+QbDlUeoq2J5kFnkDaFezPahAMnUZG08OOjXN7HjZzK7VY/
dCoYMkApPZre+0J7H4CWvORXn0WaJ5a0T5AAklGPc47bMnrEay4wijV6oa/kzpdz
lJ3P+ZWNKKcKGVG9skpg+yYJTCRGL1h8RXtPpv/Qf/mFs+vAyN6XNTaNMhfSxCkA
gETJjtggM/ahYiW1/RFmrViTeWo37ZbFPyoDojMc8vCF9AX23wMJNjJygWiUQwSY
mFPjza+xIa3m8kAVxmhEYy8yQEx1Js60f3oC4DwJTqw3CGCTyG6rE80x9W9HdBhL
c6v6/MXqFA1D02gsVi4jtWfehGngoCvw2HG6KXnBIYNfs+Oa90LmitwioaK0aoSM
mcygPeIHDWhyeB5a72OY+rtXky6QsBjYMor8nHP49rAYJfn7YOQ=
=5hxS
-----END PGP SIGNATURE-----