-----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/jalu9uZGunHyUIFAmnzhR4ACgkQu9uZGunH
yUJGNxAAsaRVuR7NcTY2lXmDbcRnsFlLjgP07+esZ62wrV4geu3uqxgSRR8ZYNJX
RbhyrElGP59dOoI12NyiL1YUdPZtjWL7nwOHdRvg0iDLcKWQqPF/ABFJ71WRXePP
lyal4aOBRlrRUBvcDOa6FehD42GqW5WQ4zgpljRvVmBQm9Ky0265PuA9hNqIggTK
V1O22KMQl2qS6dy3jAkuLYexIvPaiBq1w+Ul7M3kSWGoqWdH/5PQZ1B0k4uhe8Bl
TDuZqtxvqyJBsVqNTd9smMPaC8SSfzfZjakUzlP43VR9BaPDmwp3E/5Ql1LmQuXN
a9o76w5SZoX0LU/cPPoj12/Rzn24p/ohjrduqjExmnGR2qBEmSwbI1gmEHzPL00E
D/HUcrwox6kWZfM6Jxnjdeaq6KjmiECHgp+IzdWLRHiDm5c5Vq3iHuqxakGuLN+S
YQ/fIhhA6MEBouEI4P8LWAmP3IqEZykHgmr3l/DYH9ogoVFbOMOO87MnPnQoc8xo
CBlX5dztJzVtTYMXeQt6bMy2eWwBPoeJKFCgsmC743Y2fu+VzV/NWzNKIwgKNuGm
BIJClHZPageGLoFXd1/+kxjvhqH5ca3cU296i6CfN5S59MHEZIKDKg6N5ZpCQREj
BUS5YshulqmKc6XfKqk7VoHSIqgvqJd7g5iRSbawPQe5lf6XGOY=
=+MtY
-----END PGP SIGNATURE-----