-----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/jalu9uZGunHyUIFAmk20+MACgkQu9uZGunH
yUJeuxAAud3yywOqEaOEDf6SKHC9nK6BaM3eFjTV5nBmNIxy+rKOOYqpWJvq+Kqb
BfpZ2JnUqv7nwodgmATfoPsZm0FsX8t4RchuIZrEUepmmmtaT8VRdlFHUcojm+Iz
yfeUwbnY6UwK86sJjKxDjknr9ffHYbGx2Or6N/pWfsye6umFKqxKOYqPAQy5ejUx
TllkkQF0HlTuqF+Y+ZWiXSNBULFGuCv/5vV1peUkiNEk0nKd4XJMSY2NLlMKfdIX
ZKj3GIFlJlYHSevFcKtK1YLcjOhBwTCY5ZwcFRtZa5JfaJ9GqWjEbasl+/Y4CHVm
JgUxTScCrx752gp962KETaRUBxsYdPpvyZZJxbRHb73cJd2iKvKnxz+B9Rxj5tCp
I8V1bGzpPssbgU7ioSTDYtcClYZb4t3RBIRcLqcdNRaeA6eruk+0Kt6R2//dl8+o
uigUDcpyTJYdio0sKcsX6Q4aLiIMrgMlv7EcNHgmiJfBtSIbgtYp3eh7WVNbClgD
OQVx4C/AH02UjFnF8n/wp3yvpNC8Rs48pw3nNLe0aPvEIAd/s6T6xiqRT7oH4rxR
jL6XBZKVdTlfI0S1EYQ8LP8O3iydP4uef63i5FCKduTTsSfg4p6dzu+gasRw/Bd5
toJLjbQyRBUhka7/e2hbsNQw9hh8+qCqm1ZvYsP/gh17y64/qDg=
=Nfp3
-----END PGP SIGNATURE-----