-----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/jalu9uZGunHyUIFAmnUmpoACgkQu9uZGunH
yUL96w//fBuuzp3gathqXQX96SVP9hOTxUCaM9GhP2XTiXM12Z6MgQjyaN3hIxWe
T7L0bn9UdWJl9gLG1mjFEekYpQxtFommwqUytRg4KnzZ8v9h2FN+L3gM/hq2xyj4
GKGnJTJwk7QqxUIFu4SDqIS5JdS3y29Y4F47nQ3Il0iidzBGSkKMbv+qlM7ZES7U
zBCpAlAgDU74QsLj4jxk4sPQ4l7YqZrXFyHCGYGC6WUqkINtAaHXp6mV0pCWI2Do
QbgWTpOEdQqPwT/owRQ7b+BVrZR0ETW/Dxj7xvP/l4abEv8PUECSYp/zvSLRzOqt
qiatXdx9PW9fvB/sQe+wGsr1qXvePikLcoCuH6CA+9zOjB4ez9Al3GA3WORJ/VSv
wzoNj+8yy8t/N/uH628QxNJx19cXYFRs9LmUYsanMJ4GJWNCSXhK1t50gJPodU76
Hj1lriG507RDlzzJBscWGG6mMw1rJIgow45yLUE3kzRFaF8DbYKNEfFq5QFPswR5
WfwonfCGrAt8xYGKg8koFGR2s1NHRZz3ImrZP+lHp6SRKgeguuvRIxwwqvSfcI3C
e3UbdRwdeEbjYj2LbLYV8T+5wzmhncfki6hIThqi2qtKIGnyJM664EPbN2ugtG3l
p4z2h6JSMShLIvNnJ7QSsiA5rDXjhDP5U1ZWUpWfiEzg0EI2Il0=
=zvjs
-----END PGP SIGNATURE-----