-----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/jalu9uZGunHyUIFAmkb0rIACgkQu9uZGunH
yUJD6xAApBegg/+qnFQYxR9903ZwGdGZnQuEVk3QCiDTB+xgT04dHRGFREMJSrQH
TYbiYkvAuX9oFU7NN7LrOonG1aKLIKRygLHdONL5PX5W4Gm+qQEYI2piYvZDjmHg
S3/rnBKacBcAls/Z9td4nh169j8JwWhuHMyrEkwZqGIHGmA0Ycsm4HqFoXlmxE5Z
OZSB7PHRqgJBBMGh4csMAJ9qDQhguhwZjBomfgiIPx2khbu6IL2Fr33vKTIgxduj
/rf2b/ubo7HucKNR5g8EjkTK56DdzsbQ54iN+3IgHrptG/hKPIxbASdByKnyVhyJ
w/aC32v1Ud/gSFFz2Fo+c60TIWdWEWbXXWHrthPMFoq38KR3GasaqmExghRlLxyc
ckMe0GaGdr4eSZGCcTiLU/epd5TjpUr2wyv/Nxvjy9yqwj6lbTrPBSakDo0WNXgP
NnsqJ/v6Gioth17Ys5zHPyczajfJTrLvm/chSyi58GuIQiaYtfIPs/EwBZwWXdOH
tLd927mZo4U1hkBTG2rSwmkLH9hVcEo2sb+zCu1r4lN+n5ZliWV8dqsdNY4JK+bw
A2/n13zRvsb11GvK+Eg/dTDtqKxyPxmRo7TYLOdyZc4LUDbqAJRMaJhH0CtJRDeu
wMRO8DgiPbPfBAhKckH70VylkJidLQz/lVLqEin8hV8wo5kr82M=
=sDla
-----END PGP SIGNATURE-----