-----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/jalu9uZGunHyUIFAmrYiNMACgkQu9uZGunH
yUINbhAAt5QnLW1kOHfDYUsJuL7EdYDu27D3wALuIwEqmU6dPZsg/OtGNGMvlAsP
YwdBIyVMVH/LT8LOF5a7UWWc4JNRqSYtR6untU5MdF8E+pm3sjaSn0bY49XNSjPb
OSuP92Vn7pP7vveSXYvwHERERXWf+LsaLQeOjdKZW2V7kHVPCp8KwG5xmdkI7jkk
YVLK8x9inyKe1oKJzhMEFKrUwGorhacxKuVLFCvudqJ+YbnArdSzD0k3P4/6fz9G
U8Yu5hZm+rHmkEBFg4k9sood6ztHGJcjQUdvyB6+zW6UNdeIEmdH9QJ0w+GcAN56
QE8dJJE4LV73YMK2gC1mJhWHmadtAx6K1HQUvvhBkEbdtg2O8UBaBqn0D+JfVbcF
+7S1EqrqLCtPDTrnLBl3TrtYcgcipJZNQd1D7t8MkqNHthyckN43Nl52lWb7P5OR
XPzy4zTj5mcgF1avDYCQbmzImuEyb0+WKSnVBV0Tq1sKwzR0JifaGtkK2kdZE8C7
UxPCYc729OUGxbbra0EZocQQYXnyd3++C3J1N/X/tA38/vjLPzpWwL6ZmT5zZY0A
PaiqKAhMropfGnN5Hkgwyr5yK5yjVan/HIspqDYMOILzcQk9x84gZxyK2ezu2dbw
w3nhDksTqgC9xj5/yrKqBqjHS+wVOH17A1N75BTNDw8iF/L4WRM=
=E6rI
-----END PGP SIGNATURE-----