-----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/jalu9uZGunHyUIFAmor1eIACgkQu9uZGunH
yUKh+BAAm28Z0guxrDparkwMejn9XjXxnqEbDhnE5uLI05YaT2BMYirjOGnF+ArG
iMm3w3TdvbVO2mc7BzVivG1Q1JQkbM9fa6u7fxhY/UKcCTN+Pp3QPbiL9uoBHxpp
PQMqRrW9v2WPeRDJu7lHLmPmIs0k/wWvZYWRveNBcOeROObx3ThCcDlH9zsQFnAQ
ZFWSCb4CgY2xaIVbSyRf7G+fvMYP4+OKA532/bPFH2+YG4KsPvbWgI7cE2rXZtuy
5p1vRamqLP9PgvhpMRCI7LR8jrhI7ShTvjT/3wiU2R8sJsiJftuhnfKk4Wz/7Yy5
B5Wm0Zushe8iYjv/WNqi1iv0z0Qd1zSJzuRTVi6YkPpHkDs2djVMxPv3TN6wcJsz
9vOaBAY5VQ14UT0tmZ28sRc94/2ZN56AgEmVHDAPn16m/2IFORGfl1NvoQQm+uks
8AbCXbBBNqZL5a3ePnU8DtQQnFwEx0ac9mEWudyKyNUZrTdRM/rdN0oFWiodN52C
tHtf189G5UUe6pxTwVi4+6RNweicV7UfLVJyg2hvFrZwYDLrYR/aVKbBXLBcqHvT
UR+IxHHUqxEJEZE2ncaR1CwcsON5BKKTAIKmwY4F6DbLDylCITn+7lIE9hx/QB3k
Uxn7X4eYT1u5xlMANqlU0qLPdDJYOctofblnv8D/6LUpKk0eB5I=
=/H3f
-----END PGP SIGNATURE-----