-----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/jalu9uZGunHyUIFAmnR1gkACgkQu9uZGunH
yUIFHA//SqYDp2kkJMFCnLV8enAqfOiFgjFMbxGscBmyX+b6oEag5YCN10TbLam4
BdotYZqEnL/wyPb78PiJAxMkHUI2mWtI4yCd9YKetD82BlcS3TZ8TirmXP19Oew4
r90NKoK6LwzyLCCAy0aJLRbPDmqTVUQdEjnAuTRbRfqy3tih0Uc8B3kQ+KmJVe4k
38egtFfCnDVBqjgKlP1FFUcOcRQRusMtjhNCX46nxVhfRkie8oQ7DznajkIbrWuu
3pEpmyAErLmaIdWNaCQCEe5Jqo6pe6k5B/ubjpB0qWALlIZGFqONdlEpdvQrxEfu
luumzIokXJU1UrjBistysGtyxP30EoV7wxtVJiK3wEclkFqPYEYB/oqK8aTJRlxL
lL8OtoC3BoaVOqsdlDT2E8JV1ol+dGZRxDHaHKBFPgYYhRbMjF3x8AwSFVvlHmeU
Pz9xoybLR/nt5MvNm9JCA84k4HUPZP0Vp0hAhpKmMgzn/iuEcb4kbF6bQ3PSOxdh
HqOcP7bjpbph055Gye0qJVpLBgOPVmme6VRgaN2qT71l6Y0vBmPOCwGC0wI23HuK
5do4cM7E4c+lphCFOXQHX3uyCvtuC2YPXduSikqa0yezpTKDFpEsYSaghASAwQRE
XJSJzf54hrDgpCxSUINhdcysCYZtpyjMbLszNSOyqvoh2YBoDeE=
=Xrl4
-----END PGP SIGNATURE-----