-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
dcf85a80ec1ca90ef95993f48960cf63
sha1:
7d77cfde676b5d703ec34609193c566be7b490c8
sha256:
b3bbd255ec588a1ea8af1b32e95679c6f38e04688e1ae78d578fd397cd8502b3
sha512:
653cdce855b29abb77037aaf67e148591746dfd1af6d1d8d7b6615ad25e4131fa780718f4ff4c6194db101fe65415a00df8b5686c2a47d5ed87f824aeb08715a

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/jalu9uZGunHyUIFAmgeA+4ACgkQu9uZGunH
yUIGHw//VBIR/ujPN6hlrTYPqVIVodJr55p+nhzaTKvpaNoBFZ21ag6Iu089SoYm
jmACy3uC8k+Sh2RdTDXEgdcTEbV1Rc7P0PjMt9yYIH8p6t51tLS5rXaoWrg1noxk
Ciq8y2BeH5Urr/qV4nEDNIhQqb8hXKkNLTf2jPhfe6QRplfpnkXOsjM6SCjXR1FK
XlYZTlBfcHY9iG9+p61Gg27+8yi06LWqhBUrrSRZwI0GuNrfhf34uf2Dk5B617Mf
hMXZxkOPocz/0rjIJcjNnSuJb6A9SXtwWbglo9hAaITkL0Dmtisu71/dcjNlGozh
A52aHnYjcYGoGW72HKrhFHpDH40HzWtsEuvcgJG03YIt0Vr5JQt5mxUmEFFMWLkb
5vdqNqbuPhXKicusha1DXq1S2sf0BGqQ+FaITD7TtDB08y6EDW+ruiKEY/EhYB0Q
2Oz8P1N8+bcUJ5mHcuDvIdgE2I9LTI9+vp279YHG3cJWa8ew3dEjHXmaA+GBo3hX
jvWKmrftq/cDtMcAoUmJ53g+WQ6sz8rEW9dazvnUlsVh2/lUCzKEMJY15l5t47b1
DUopPXAVhjDGR+KAgR6UZGt3b6hV0T2iyC6kh96c39LfeikGWJ/1YIhMln11dsW/
oMW4cfHYAIz99jtvPTQbeiH76BHrsdLlpSknrhCzNPMvayjC+vA=
=47BK
-----END PGP SIGNATURE-----