-----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/jalu9uZGunHyUIFAml1w+0ACgkQu9uZGunH
yULpzxAAmFvTFzkHEUAdN4n8RdqEWzzWcJUHe7Zu+ztPaOgG/zKwGzDmqHS3Axrp
qcGnX49j398brhYj7ZAzSY0WYRV1WRufJgIrMqfcvqqz2Q8JAA147gx1mjT2+9pm
QQAE9ZiALfmsJST8TPPzYfk955dCdvkyvX1Y7s3E+Mf1BTduyYlyDefaf82OErSq
Yd190OWrNN2jZPOlZ0hwGqLopwnAjxel7yCdm/aJFfiOnvPLegYkLgvnugytmwNt
tAsw95BlIabCg/fCk97Jt7wk5zeaXphCaPW0LAMLWlwwkakqt8GP4gM26YdDy4Ns
LjYW/xl1W770lrqVyzJhdRLpWk2JjBldkDgrib33ZPdzrOzbVTAJsdRSF5Nl8u+U
0qZI3InivNL5EDxsGlHo8RTba6+mf+3i9NM+qG0mgOVaLIzNseYQCCySwRw+gs2z
CBDBwBXcFjTbBXVCXYvTY5NOhHNZy9hM+zlp70KGszZFrsjPYIL8Z0xulP09sHYT
OjSKSP4psth2HzoqLkVb8ten7bHVgDiSmkhyT9Unm4H7kqlZOxivtnDGCaQa2UHw
VUQypmrld9IdUq5XJyikyES+o4GB61nPXexcy2+Zt9c4iQoEHpCsj8Bnjq3JN55L
ojsbQjzE14FXBu76CEcuCcVRVMoyR5fNe7Iii/AI3mpx5qTazpU=
=Me8s
-----END PGP SIGNATURE-----