-----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/jalu9uZGunHyUIFAmoxTvMACgkQu9uZGunH
yUJvkRAAsuNe0x0KqJRwAc2TgEwLapV4J/iLnx7OtaMWjojf89N/0h7Mo52KYqQQ
0GZtNImgr7bO7yywRlEtq/rYOkI7LH52+kEG7VeKnLOeCvblr8DAipK/Pjx08Iyw
r9Lo6mDtufZ2QczrJlXA3dA6kRFmdMkdNU6M3I1mrqr4/k0XftZ89CuSDLc6t1mw
ijGgtHy1vsgHUs93mPTfBO4JsWVQXFjK+HmmCOxrIoCjd9Spyt9yMOxGmyY2HkzV
57Y0ZliSnm0HppCT31+kavxuF0OaA2gEbXT5626atFo9cLqSTlzM1363TmZwlKI/
4e52s0WxyNsQghzpth/jrEa5NNKI2tzEXLL42NWhe6Mnh02O4CeO1ar4ZuAEwmTC
w0b60c1SpHX7YZo2f6or/3RYnq98fwWZyrghkAPrOog42LEqNv1tWyNCC6TWbBZn
A1iIkpfGjzllzDLf5DRufNBRQXvxFrS9sa6cC/y8s7McUX4gvnSCMgkPsoTSeMEk
3mH62/FIhigyV2WvBYk5lzsV6b8C1HoJu2nDpbAOxT5mdthYhbskWcUiEzUASnkW
TMcu6Z90Tn7S4+owpfpI47JC93nBvGITzrtoHJuJv/NO4bNoOJcaMyq6E2rTh70F
DyWqOHlhSwUfG3F2udTvA5vlJmQQDM3eeQEX3Sz6MwrGJ0iJjHw=
=dYPk
-----END PGP SIGNATURE-----