-----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/jalu9uZGunHyUIFAmok+MoACgkQu9uZGunH
yUL8HBAAhlTrcIq/M6SGyus5uiKy0Zn8akWxuZUkjKHH7sOH3kvfFDUhooyts4cV
IPt2r3IsWPx+gmbHYovJhxFpKlZT1ZZD9oZZWQi4CKIiXIhmZoiEoWloYGdm1FMb
GuUiWeheB95Q7S3g0ZO3DxScThd2Dwgp9USoPzdthcxtDF4fk5U/T/ONwPfiotW9
ILiDqKN7EmbTZNIsSkaloUSz4/48rggPZgjcJYiWDCvspkxs2j+yPHBH1yIm8MAM
S4Zt1gpC3IoYtwBrbNcl3kavED64wl0cxWlD5FgIZIBKSA0aW1zVuQMDlYMYfntV
JHcYeQhc77T6XNfKpH1ooZylsuaN0iWkQiJvmN1YfWMvGNqVB53Xkh4HHf2vMSNG
Yvd/hkUUiI2TvEAnsXKSB+6ZJLttuj/lo8coSBrn1Llpv+xJXY0e/RFqSBh8ESQf
wDJQzN4vxzaKpiTFEVuBR/Rfqbw01rqCyvD0Cg49EqMjf6sewy4q/gSiBfre/nfX
6QTvA908s7ZhAf8iktyKx7bRztNwhLPEvrUFkj6zpJGHgxU3HJZ8EkkTB/UYeJTB
abqo1UfihDz8pJc7iq7GFZ4vz6nYbMtrT+D9xkkuqLeHT8j+FSVGUzSFCQvkzObM
CPK+tV6086QLoYdBQ9B5uVAZ6ZTAW2cXhvVkGLfcPcmiE8CduBw=
=GQw9
-----END PGP SIGNATURE-----