-----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/jalu9uZGunHyUIFAmmHS5IACgkQu9uZGunH
yUI0BA/+PEgQgutNXaIX+nGuQReJGsERy1SfVvFa53+C3aWpiMEqljxFBHf5+0t6
zaVXtlvxrYEXqVd3aQVCODBcb3OSWC4Q4rYtUMuAw5gkwV+QvbL6t67IdxcX19vE
SwzoT8MgJSm1m/YCZf9vFmARTV16OUPHFiujE2KG9ExhHw3SASnlC+nk7G0brMl/
VqCZkNihIIAHzwDSxWV8wG12MSKlLfRw0wxYFUoDWQfNgklCyR/VBlv0GmewaykT
D6f60sbpWUSTRF00MFlOsgAsVCRZ7/0hA1nfOt5xf0TJYf08xnr5rQ83ntmIdvdg
7hpE4MauXwpEjiZ1Wojl0NLuRfQaab1DoJhxVPeqhU0sKO2X6StzTdTqnsPUWKRJ
9Ts7F436lPWU4s6L8ALuZrIKTNesxfAa+ED5d1QK+SFNeWfH6Ga6wH5FlCIMh1Da
9wP+GmLihpsedRHd0NYFCt4ExU108vmZ8mwbo67aMMeztzZUz071c2EBEUHI8dvz
wNzs6SJkTn1BFER4chCigXI0kuiSJQ1BGMFXGUX+8iHH7/rxf8rxv8PDLlTktADg
cmkyvvOl8JiBI7IgSe2PfGLVXr6//ZB6gHuUpc3DkmgZmetPSe/s1JjE55HgJKpV
FYIM4lP5dPVi6f4r+w8/pzKndrezRNwTMEe1Yb0yHPYBzAoNP9c=
=3ecb
-----END PGP SIGNATURE-----