-----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/jalu9uZGunHyUIFAmkkpB8ACgkQu9uZGunH
yUKEIQ/+JvJBiHUfv7wmfAtOSF/rRhjGaj/cjkYlvd7l0eZw2bWJOZTS0TUVZeNZ
bQ6s8S98LK28MqhAEIXz+UspKvPNFBNHgImxN5VRgOChytYlHSAIHwwyIl1etI+x
W7UrmaBBgRqDa5jf0i6Zzwq6cRVnTLrc/otxtkehAbR2vHidXPMiUoOq/hOu3DmG
npFoRtEICidgx+76OI1IYqsoGUyYJQvACu2L2PxrL1OyNdHS/uCh7E0AyDTWjN/0
8C/LMhZC+bkLQH5Xo+ymfdZyrxYLrwfOLUY4Y56Qb+AErnJckTkX54X3wPYZMokv
xBCTYHKorjYItwlwD+NXYNDmIFplWp99lvsfw7pw+O9Nh85YwtT6RUm6coFao0Yg
ST5R3b8upD5Y59818+gn1sVSCCjwAHg0jUm5dicQYMHNz0lvNefVyEL3BYCcRoid
iz90AtTEW6fW15VpJmfq29tikSFEPHIfwDbaZFnlZM6zuB+Bz4SOdkb2+Ecs2N5E
bBFmNU9KExgHWWe+dvCI7dLP5HZn//9+H1Okkv31x6fhYgvCOc1TZeL25spB5v3m
XXGrUYbmVOBX4srsWtsAzNnw1bnyQqiuSD0yUQBX9QFi2Slma+Ow2qCKuUkjYbHv
DYny2ksuROAferm5RCM39UtdHv1b1sGDtkOOzWBEMz3y5/y7xAM=
=OoIb
-----END PGP SIGNATURE-----