-----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/jalu9uZGunHyUIFAmn98RIACgkQu9uZGunH
yUKByw//Rgrs+ZEGnuBIK9mwCxCVAZp9mI7bnsk6FmFpGgkGLK2Z6Y3AAq8FbAuD
ZngQHWN/bMsrDkzoEZYyUa1hhwsWWc38Kv9E4Jggi2SFE+9YWUt15D1j2BooccI/
8sIpptS5GyMU3UXNfTZnfUm0jAEDJfL49bED0cdLDb8DjWK5DS213WAhMaKFqZdW
PyFiurTGNmeaZjWxc9U8+6Qr8yx80GCRzwR/4F8hu1iChGqwtUWY8R297d4HdAxL
H70PCfPMI8hvHSyv5wD5fnwEyWRjJQwzLWnRNFQsWo0Ij/SThWClyOTSEBoL25HP
t4NuCC4GDROq5jlx/2fmfghhGk8Ach9CbPBFRNzvam16/F4ag0kQVhiA95F4SUxm
Otg+bvZbegz9vdi8z89jg6dqeyYvpAcsEvxwK+oxI8H+jOKn+Yllyr3lGooDgX3h
sdVfbc7/i6ZVjaCcphl4jk3lVfKPXz2wVoIsa68CQLoW8ALhmNgDzcidZT8z81sL
tg/WA1ojkjvi9ppLbAxV8yi+00PH7gq9HmWBjNruTYzMwW7PsfvvpeU0MMceSv6x
U5nz5GPzld8TMHB2KCCe4nUP1jGJn5WdXIjf1mf7vBrpXkkeSLqYKMgRmfyWR0qz
fKf2nWaJSEz/tSunlkYtcvSUwZN54jGbmaIPupVXv+mcJBRQqHg=
=N6oK
-----END PGP SIGNATURE-----