-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
7717c2c1a11c37f3e828445c8b19ec42
sha1:
82c2978255444fb7a824eefb1b39a59920e1eb52
sha256:
984e8838c7e363f29b0e59cb601aa35b18f941337e388eaccc9e355e49c90f43
sha512:
538a8b595c44f3380e43fd077fb3ab5c1a1f9a07ac8ad0e08c95fcb627f44a619f35fc02d8af9cf0bf15e3f44b5d36a5133f1a0cb419b937ec0bb88d36131731

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/jalu9uZGunHyUIFAmrRvo8ACgkQu9uZGunH
yUIDbhAAunttgAskKwj3ylg/Alj12yGDDGk9e0kDfxX3/eVDc+I6jRM82aowL8ob
/SNwmfHHev1tzDOhfRrzxX6yWZT+rBNqE9fPk8OfmeJImFhrhZv9zbAxqywwLuPO
n3inCRSorhwK8No44k7N84vkTNsb+q0WknMEto2HokyVsdx7yfyLNgGWn7Sa7C4H
t383P1vTX81o2hXJiFLkqAmJgmMp6tqwuvA0VPCd9ESsMurtkdhzWZbhYRBTXxFj
SFtZuC2VQDU64svAP//qnS/6sSsbb/tH9pEBvIYSOTrQ6bWtDaGdha4ih3x82dWK
Bbl3Vu4HRRBxxqKJoQrgym6aspXgZtiIBRafykY6h09GjE41uTH/pCBEdxlD8t7W
JeBhhvSJTcq7Wu3JugAYoSxHgUxat8dCsRA0Qces8iLDFZ0f6tVEvn6DswBCgIho
qoAnzU+lsVcP6LDkdc2oY5HmiAQY8CV6neCNkbnMbZk2qhQGLUj493U8zZLtCqJa
lZPrhgkVx9kDZqvMyutBtdeO10zpUQXcWUEQeYBjUYKtZp17wsqIo1tyIUoQoZbw
trkon+ooe7y70aou39zNLElsrzcKyAmJUI1xiyYXXEIU2o5+2ciZN4WPALeyRWth
T0lNOvB2+IoCTvXbP/4xPDWjR+QyKIwdERI0jjV+KhPK8FAjMHc=
=Whn1
-----END PGP SIGNATURE-----