-----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/jalu9uZGunHyUIFAmrXKdoACgkQu9uZGunH
yUI64w/+PeLO543O+SsHaQw3FVW7i9k+PtIvT2uyBIbQtlDU/sZj5kEXw+WUl0KU
bUCO+mV1gvrlICWoVf3sTkS0TlLr8kyjEGFMVMfxrjLLVbKHKYzewRSCYc/5i+mF
wpdl3cbUZrCuLQ/FtmnwIQ191NVAgkMQShOie+HUPaDdGtV7vi2Eh7Cg5jmn+qep
VQH5oFx9uLglo8EBUx7qY0HqT01zAfUBNQheldetql+O+be14cVbQC2hSkOsLzg4
Ze0yf28Yl68t8RmEUKX7jUTpYXWPPJPt5FCJRMHYRwNiNP+gOGbFUeRMKUCPWXJU
c2zoPHmkI4ZyQTcryg1xkS9wEuN4ROWEajctwp0ZtsG+IEKOpIg7StpzDwteUioT
FnQRi2smljjNdV7sSYJMg0qOa4KlN+VVw8Cb2iATA3GvmAqSWiDAmQ4FCMBK2g1J
NeLTp39LTK3i+HobX/PwOKHZa+GtVuL1scRhQphgWAZkUPIXOufPk4teRwjdAeYn
l+95xA2TNE8LSnXPtpbibha6pF9B5HtsAlbeYhAFwzrwAuYZ9gaJ9Kr9DABRES5R
T3m4K0VO9W6qM9SLXlfALV6TDH/3Wl7MaE7+norWwuhJjEaV32bdKw7RHGfQmrR0
BpvqscP0eBWfhsn2tkNL+8nec2gLARtIm+PXTjNyNbuVaAp+320=
=2Eeq
-----END PGP SIGNATURE-----