-----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/jalu9uZGunHyUIFAmk0uIAACgkQu9uZGunH
yULR+w//bmC59qJ8dl/O5xWUDeGM5AkhNIGuLg8+nlPozjGYEiFh7XcXerfD7apm
rpgx34gHXOjhNOhdUcWLSaN1kvhnzQKdMcK1ygqBYoqN1rGUBl1KQC1CoBhYf/nu
HB5qzBFAAS8Z2TvYdl0fntBSxOMqXU/BkyWjBjyaayYDWkPuTAZJvn3rJqIkXtCI
WDY/k75xNUs2iypwex1jnToeNJyVcA78AYhXJwLHAjhV1t7sWidp4IpH/fsndqeD
OXkXgm8DZi1nVInom/Q2urKUHVvu2x69D4FOWw+iO8UrfHqCSfoT1WSPTUGhvPHa
l/ZtsriKlPzGVsHaiJKw+eSeouoyQH+Nx6qtn6eQVgDIGvudvOkGzBFVL+gKYhEn
4CXP2Rn/HkBKbvP1C4x8FfoAxUmYvRqOOJB27eo6EHhLm7o1TxKcyJgptBj1deFH
bSsgtg/crDo4oQES9TPIz7bgn8upONQqjT3HgMhluoJ99qiaS/Qk6b47Ma1psDu7
Z+WAMq8OuY+7C7mxHeFLkg/3m4ivWdx/712JPZsobcAFxS5kitgyJIzjInMeiOHk
+i9AGq2SMao6VGN9eiqPHbHQLHlyybfXuNNb+kMyrOtskKRE6RJyNq0T/nZmX+RH
WihIoEZtvE3cojd/xYsKklnnc7Hu0HiBc7W8hMg/MR7OKOuLyjk=
=lwEW
-----END PGP SIGNATURE-----