-----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/jalu9uZGunHyUIFAmrql/EACgkQu9uZGunH
yULhpxAAitPl3ahzpKqxGn5nccfcpzaCu0bkw5AY0n3qSeF3lIEuKobgG4VDHMPa
g9dbGrjsLFSY3X+ggUf+h71a4vhteBkYKUL1ZsjivxQ3HMiSHau2rkdX2af01BZi
6/B/k5mawaEITEsUC74GQihI+z6o/3HbcGGtrweR58WnfDHhdWfN6TNQYLyJcxF0
nYdXJlHvKBPizeU8qrETKaPjdzkSwkBrRmriS8T9x2PAlV8bo2QjGwfOzCEG1gt9
d559eS7Lwmag4YHY7OopVoAaT2TS7lmaPQeyh8tmGiAR9U6tnJ7f3OkMsuhaCty0
TltSvFHyeo6g66sPFZZLZNMnycUTyFXmjPL/01LYURW9q9Mn4yVze/8rr23evsM1
WxGX2tOutYgsGwxddgJXojGIMu6Gcai2lDN8lFweXGZCnRObIK08ZkMOZ3GQQyOj
MqHBhkCtt52WhZ8kp32C6ipwp6HvlEYVx9XPyrq4u3tAKYoOklZnrZnzOrw8XCnX
46/gn223BHMWA/Et19Wk7UUTKS7phrNnveJjWBf3yMuqkb/qp1VwKpONJsMZXoHj
xHaIn5G8lSa57HLn74GTi4kjy1t4Ym64+pcuJKsbun5Df0KwhRuf0FIYuuTYX7q1
PbtlKSRbKMtRAis0O9eiNZjyYZ5nEo+837WEG54SVenIEpKM5Gs=
=TgFA
-----END PGP SIGNATURE-----