-----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/jalu9uZGunHyUIFAmoKtJUACgkQu9uZGunH
yULBexAAoNpujupDu965N52cjyKQFGEPMmVSOS91obXzT2F80CcpnLU073osoZHv
rbb/QqKCePHAWUNbGxdQy4r69HHl9JCpAulabbz89PnBsQ7jfbTQOrDQ3khY/Z2H
h//OEB1egtaqMx5x1wVFQd0J3iidVCEpiWExJElY9ZLTsqYi+6b5lXux17En5vwP
1eRJk5ATFhm1gk9rA6OkEOGUExOnpuJM3Ivtit9Qq0xVGDSz8c6MHsDrEZ2uu3df
NV8VI5kj8dcy3VPZfxCi/pHAKphDcUuaTqqi4xff9GZIyPYzZs4Xq9Bwxkwwcrlq
WFyo7KXdQ/67Bu/fbO1kW/rRbaCalPnzlz/zowMntX5+PTqwCi9enlb1Uxv1F7yG
fYDbzM9dMDg4oxKK3yEIqcJsvzR7Ohvls9/bSCZqQVextgvr6Bp/9/f/bs8LhI58
ZVxZydEcPHX+uemi5kZDjBakrcSfWs6nqdcaKIhe0Xu9WKX0y6BVt+esUBtPw/Bc
OrClwQnzbS+FsWQUCMKljlL7oZDkIV9lt7YBPEQjqWFz+aev4Xhqoz5RDz7yzUVN
Ud7TGzFdn/APLcAx1BdnvQiHJRKGmmuCrHLC0zciGTBJOw3jU3f4/qeggrNo9r0X
I1/95wFivcSAylHw+hmQHAdQVpQ8ar45cFzDmWoU5gnR96yUOVI=
=2Xcs
-----END PGP SIGNATURE-----