-----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/jalu9uZGunHyUIFAmoOCyUACgkQu9uZGunH
yUJQXw/9ErEDx/5tlGcBOk1MYhjtk+cbfkdBirSAIcXs2IBRUeCGqZujPHL4KLvN
ARMrqOtl4QxOTzm7kUeldss9iR0iMgjI/5letXyb0BnEDHUHPHfTxkbSy0M1TKxr
zu8W/pXQwHZr3UF62slHELBcdlA2tAaSGBeEy1ddS+qoH9M9KSxkHT5FBx9/VtFh
MBVTj8f1IS826u+iKOIA49kK23esZGQnufNn28yMSy5vtTOV9m2XrysJyFbcBmqB
BX4lrHsSFTDNLS67PweFqQ5wxDfGhC8UfY/n++dfPi4/0jjBvXJTPTMJFYz7PTRA
Ox1dyyppsdGia3kZpf/1KhPEVIKwfCtYp7FutpoAj5pwnR9lq8MQDPnWOYxyIloW
UuLpsdfLdPudEya5Wm4xFumWHVNFuXNUW9A0uBvTX37r45hJIPiLbE6SAg0KjbnR
zfNyRsPOFEr/FULsxQZQyGmbEROEUfoko994BsMSKZWMF55XKdkZcK0sq3ndyX19
DX7EPvU/S1Vdg9Buuzq69mkgX4YvgFpnj0oqyDTTMaoz1eiY+aWIxiEpA5lXprHN
oiITR50Sl6egdXsCn98y5AoiPcnflvsYMGliDqoFp6vo0kADRGcBZARak6TYkZNM
1E5GwE95Km2ht9HzcpfigNPp+Zanr4zV5OLizpqXucfI22nzC2Q=
=T0MO
-----END PGP SIGNATURE-----