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

md5:
7717c2c1a11c37f3e828445c8b19ec42
sha1:
82c2978255444fb7a824eefb1b39a59920e1eb52
sha256:
984e8838c7e363f29b0e59cb601aa35b18f941337e388eaccc9e355e49c90f43
sha512:
538a8b595c44f3380e43fd077fb3ab5c1a1f9a07ac8ad0e08c95fcb627f44a619f35fc02d8af9cf0bf15e3f44b5d36a5133f1a0cb419b937ec0bb88d36131731

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/jalu9uZGunHyUIFAmr4S34ACgkQu9uZGunH
yULyFg/+L79raTmoAo0kayAVHIH4LfRrrKZJuZHhPwHJS/NlP9UuYa8JThVBk4GB
68/NX5tDH/uNbukGbo0arsxX4kham/z1fXdfA8qFyDSz7O8zRaOnDLxkhNKbwtk0
ZyThqSWa4+gPrzCrXdfTm1vGiLn2rpR7D07YGXxF+aq6phiQirvDOPXVfsdE1LFX
EdpShZhTd8dawpCqETPh5gLZ/DvjvQYKumuo5KtoXp6EIz36c4G6JGC7rVMXeB79
+O8EvNXNjvbRchqkz3fUYj7dhWM4XNu82uwOKs76wXvEv7kNBE9nOcf69qspP8WW
wv6eGlDyO2qP+i2h2SYH1/CkSyG+vWlF2Gd40SO5f2kySZ8GegP+HcfBzTFUwgbZ
+5pH1Jy6F2jGyccZt0E3w6IMHyhwmaeBwwzBRkFMe7AqI8PvfcAuIL6YlSrl998t
pp6Py0LjLsBPn4bBvPbibOOWDUc+uVcDDj0QnZ9xpdBfpT6dE3fqCt0T62c5oVg/
Yizf/Wmb10aZpE9a56Y73HN8ffjj1O5Q4GJM2dA0kUO9YvWl6lC0bUMp91RJygaF
Rqq9kvJzjnN2JX9Ip02hdBX5CzfcjDtRNMopnCnGz2SIErDS8INZpLQErgGWPRcE
r1tyvaEQrO6vgmwfiXhh9qRDuGtDym/LOSvlfRboQg/f4Ps1R74=
=BeUS
-----END PGP SIGNATURE-----