-----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/jalu9uZGunHyUIFAmnZmKsACgkQu9uZGunH
yUI4UBAAur/+WhJ3bcdZk2FTyvB/ePiKxZvRQ2zG1F2WE/g9YEbwftrEcoDYMw8T
LmMghqM/KWMGqvUP5r8bKbnyGibEPVryws7MwOqOP1/90mNtUC/A1qGZtRPqiiNF
Ufl3cQWC/aIk4iQGSFRVjDXLTwaHifTOJTj3q/A7LlbN9XEpAo1dcq0FHhpMlLoa
iXIT7lavNGRcGlyt4VdtXl0818WNf6jnSbfRf9gR4PY0X0YpNvhN8qQPvUMFTp1t
l1Qv8giBY8lO0HyznYHy5gUeUeb7MRoTxKVzl9IytQ0q+UOg9GvZDylVJFEe5q/T
QK8WeJkuNT2v9dvmqu/Qti5+vAkXgTYd4Bk8sHpKDLPYzx5T+xCzXi3TafEhYviU
9VyZTKXta5aAykX+sychDcZ3Milih/NETyr3AA1x7Ljnr/tjEVB2wodDK3I6MGrY
mP5b69q7UEp8GVJkE7k1RAK35iWWWvpcvKqF6BHRAyO5TSDwWv8/J/gwmb2mSQsS
Jp9F1DCdZVuXKOc159H5ng+pAKNWAbaC/bVK8hJ1SZAYJ7o3LZHCkXzL7girc4Ik
zZCsz5yiUpH5WGBdn4/eXJyG+saHzpP/0+1WiSrvjYmH56Jb6ZshfTctXr18lV9a
Aibi8YBBXXgPs6r2qN+8nMhG0/twUMc9Ntlu0HXfDT1uxXm+U5c=
=n0Ky
-----END PGP SIGNATURE-----