-----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/jalu9uZGunHyUIFAmopKmIACgkQu9uZGunH
yUIWEA/+PRvWn0V7nFgC/zmYcxnvG/GVSQqhbqbM7td2r89zQUV2EUynCkKzbyQE
qb+hjRjCUEEpcQfz4RPLQXVBmCQjyy3nl0D0XOAwcnYzoHmMyu5hT3wy0jRV0kkD
d4ZhFebD/3nAPH3+Nhp7D9PvHWqKtEGxdL9mVZTJ7b1xCjGQz4ruOFZj1OvBRlS9
1kKJjJjxT+mh5iJVjbwppL0uXu5PG1AM+JJHR+g6pB/lTqHHznjaFXDXAO1V2Jtf
JfPGmdiTEv7UtxpTroBpT4QTPv9Azl9d5hqK7n8REYPZRZzMrzMx1eOsGxIZmgGW
NxiSeVot/rFvuTMO5BhdAFdzHVaOFZyBryAD5Otf908+fmh0+g84KKOUV3ek0D5v
Tas2hN901Rv1VJ+1sibwpNJOeDT8JzJvs4MczJGU8niytQjl+Zg/oJsx/N/MFg5E
ebMY1cuwP8PFAToj8woZhRS692oBuXYJdDEHVqumSrsyOfQ0V7HXBvXIlmlknWi8
ptiOW0qdzbxVHkx/pnexwj+Ixzo+G+sjvbdRyCOgjfsgxbNWND4YAZJaNkyDwwXI
f7JH0WOnJFc6Vn037Y5iTiAAThPsBfwbO03WXo3N9U6QpAYM5sIhTfRxXklMlaB6
ehYAf41aCtrpo7f8qWQKvWIbKUrdKiu/cdRu99ruRlWNt/+RinU=
=eSU1
-----END PGP SIGNATURE-----