-----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/jalu9uZGunHyUIFAmobgW8ACgkQu9uZGunH
yUKk0Q//ekl27rDuxeqwussT1HqLzZdt512PaRNfrIRniMM47uin/NZ3sf/NBKON
hDeWd573AJQdJHO7WqyDxgP1C7p4QXDhJ/RYlBYk1D+4smFGy6TwX5Py77OBVB9d
lMl6k6iG29++3cfKQrYjNm/5v7cJPTrSarSnJ1gz9FRwS5SbKCE3scgI5yFqvlxZ
vD/41XRi4mNf8lbVoBltzBrpWkdBVFIoGxCG5mcXWcqw10KF+pwH2I3Y8kzMhodt
cvV7iejqAJvrPGXpFu0qoyjPZ06JVsIsLEgQMtlA1PlgVxeoalICxjPUaSEKlz5O
mKNjGLwrzewkKNcPds0foE8xxJtkZVILyVV6wPB+YMvlKTeL/3I6FcVPXmtwKAGU
WpVFSIY/VfV8dfuM26tTaG1avN+D49P8cQJsjTjfZLWnRK3h0+geN2Gm8AoQHBpv
pOcb2NuxYjQL99EXlSKpeX375HOmrTvtKz1KFsDw+oFnH7qOrYlCUdggOlDqMFkI
sB643fNVFVFBgLCftUP/mx6JngaD4M2UugaMdHaayqmKS+XG3ezXwCL4qJxv3diR
EKxRIFjEAkjmmEi1OCm6fwRiDMiUk7oohC/kYoJ+CoaOjh5dzRhOydXbECjd4UBq
PhlQHViVs/YIteQrNBHNvNq0iDtDpot6jq0BRAseSDdQThX+Abs=
=EuWS
-----END PGP SIGNATURE-----