-----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/jalu9uZGunHyUIFAmllr+gACgkQu9uZGunH
yUKpzA//f7lmFI042xoa148uRLIGJX1S0xBNoqcjet32N3y1GfRVWsPaRlvINdGV
pfnp8L3PXrgXw0Vl8mk0KdxxrHFPZS/peRo0OKpEOLmSDTay0tBvZTWP+Ak2Ys2Y
wYArvsjkGL/Z0pyPyGjC3c9UF1bXOJ9nputWYUicwDfJGHpmF4Xu/Zld1y7QfcV5
gJ9w5i/tSJZhcITh6WEMmrMTUUM8v1OtnEA0hYFDNfVpmyRb5FBmnGl0bn8wq2Rt
GPTxb19Az8a0uNDo4NZHjgyqrhGRKpXbEpk8NN+/EArPeyHO8nHBczKtJhaziosE
UVxudqs8DBCy6+VWkH3c2JuMBfYj4Nj35gVvnHKavhamzi9uBW/AzvacFsPci4dr
52YrRyvLe2eJ3opOQbRsUgHE6tVLEZXuRE/ML5k4S3b3jEhyhTw6n8Gk2y02ok0r
VsWtt/jYASPaPq5kl4IzYmBWOLVpKOOXiotqrzjgs8tEX2L3P0oGaY5r4cI9Hm9+
23/PAkedItyc/955JqsEht5H5IeU41xZiOcSsI2zu42bkjrHpbuC6DSTJ2GlhwPt
Fbqrcqfoqd42cvzfDjmxT+2y/1ppPOZ16XqtWUj6OruHFs4IjzDVOhKvRl/+yxPN
Y9K75qiVIukmos1yw8jnmNTFiVELcU4s6JUcY8q+xrSND0QQEwo=
=+twZ
-----END PGP SIGNATURE-----