-----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/jalu9uZGunHyUIFAmnI4NwACgkQu9uZGunH
yUJZqQ//bD8ScJxtfSNqp0xiJ8lUpc6ytSVqGlMH+Qikc650TO+7M5Ce8E77B5wR
WhtlBr/oN26Rp7zCGmYv4l7nbmCilDlRSkKWzakHfeP9mcsP7OQxdCzI+9SieqUR
9cY+lpmAmyZ1PNqeARZrHtsuC2zmAvERuU0UWcgE6S3FiNgvJiWYKgWCbRhs6Ys5
yBzRp5U+pAZkPjsa1lclHuYw+E60oKfRgYLa9b8M7upe7mIWC1/IebBt05LhqIaK
M6uAcoCeYIHxyLBWzNwTnjQDUOCqzFU3Kp2JiCzhpWF+2NYnPiB1tWW8ewhMt7on
s3x2DCLdrlP8h18VRYCardjyMApjGPUThfFgZZPGn8JuZ8AFo8gOLNboY7Y8aLCC
2p6y8maJpe/xm3/Y9EIICHKiSm2XKSLwiCQxb8g0KKV2w7JKjlexsDeNW8uvfhcF
bEt0tIHTYgMnFRgqVEB3sSi5olT4XPfIDZ8jrclxlmpuKzPxH6SJhthzC14PFDbE
uKaa5hK+4f+XR+s90cTsPk0PUwwLniIPjGu/HDsifLg96GOcP0u0f2G36Gdx6zzF
65f9WFaSa/DUxw05V1gDg+PYWfz1YvIDGkwl3/Cz1WElz5aIugDkTSeZLKwmnQrE
+71KkPQnxt8eCf4G4UMIunCNPQkO08LNdWsfiGe0cgSeTJokA2M=
=/MZO
-----END PGP SIGNATURE-----