-----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/jalu9uZGunHyUIFAmnkHGwACgkQu9uZGunH
yULFCBAAq7wk1SU43D3SmyFRWMZ59lUDl7yjm3eyh54fjRCvN7S0LMRHYwR7uA2n
Tw6u6nYXH1bBMnwDztLjAiyRLpkvC4LFx9kzYMiRIBEpsJuLf1poIf5c+oSdgT0/
bzsflx+tkx9WEEC7XgvZNWoAKURzk3HiuQ8zs2gKYUID/209jZQwJ58FwhuE9zbf
EiNQOQQmkJ8MIUVY7+WVv2o9v5++i16X0m65XDJsoHBuhANIow9KQgK+mkdzNynT
Kv2S6u8qORDT53O3BZpP7oq7nKfIgVV7HE07SRUpHXGmQ8L+feqI9x4ndTcsOqpd
ruxpUqJOfcpfwdbSNPUpquRVzX/opcavrg7cUYu/v980s/8XKUBdO7daxBezlt3Q
Z+fRW7o+jijm93z/l6+p8ICcjWDJLYoYNc1pKVaLzd3s0Iq/isLlLyN7y5K6zvUp
td7UxupW3TdQQ6v0lSicvt5lPGLv3XNFMqz0KVrpPDfIYfgCU8AbKzQiLhKOChds
DfLra/jtFB0xfulg8X6KxPXR7hb2oL3C0Xyisrwl54Xqjvo3g834X4VaZrvoLQGN
0jhnLOLss1PfwtAEicOIY58o+o+CQ7VaqdeC1aye7zHhlPBJ9eWmLRUN/TsesJsp
zV5RKNOyjids4j+4rmeNu/lXnbWVk8wWwqGwFwia24IsWAi6SVY=
=NXRO
-----END PGP SIGNATURE-----