-----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/jalu9uZGunHyUIFAmnTz+QACgkQu9uZGunH
yUKXXw/+NS1AAxynpnDB5VelmOXTWr0BcnlsuvGZhKwazId0KraT2bZAbHwPabI7
U6iGZ/PWx4uLs0mhPwbqG7vKegPDHp/3Jqu92ttKLa5SDqh6iygaw3alxzvFCaYK
RVwWRiqkfm1dinLKaVdgQ/lZY6lHtX4oz8Og18/YxJ9+zcOpxPCXWJKrDIjdmCay
OP9cerI9Isliwj6fm6gtLGmOLZVxymprssVfMFwVwGkNANwXwVwaHOhq+vk/nIAM
5+c33zjdYMQYK8ozgK0AycnMhC46+UB0xMmsufmU2d8XaC2rhcCKwHYv40DmDXv4
Ejh8iGt8SomYmsd+r7Tx7gSbRzOGZhyPIySm3LlgTgIQdQ2akD7/pOLRx4eoq42p
cXEXpydmLV5eVJLSTwHoYaxux1K0Dp+B4qNgCq8NUApKX2mDqoi2N6TLSOL4dk8i
96J2O/BIc59Wym480XlDOAQaWT9tZQdUDJt7gzM6b1lDnyllsI061WYnPw1zonl6
tumRflNO/RyDYYhBF90CNzzbHNQa4+eiyAZirVHAHPq+BX6QIEHGsLTQ9DOJVjT7
wxB/SKmGXVdz7E6ObifPsVPTJ+vlcGhDOuev/mTGj3p5RdybFLpd4ns2crqErf9i
0hKECM0cdjuCiVomLcloTq65migNxw+pQ1p+I+7Qog/kKiqSWEY=
=jeHw
-----END PGP SIGNATURE-----