-----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/jalu9uZGunHyUIFAmnsgWoACgkQu9uZGunH
yULBQA/+MeSAwOd9eiQTqcBCtswaoBJGPJmUdPDNye/XDbeeYsWyi9g3Ab2b7MKc
++7sZrH9ZErqLj8ba2ghdCSwEwVS9QFKBmu078d4oHkwIkZp4eeOuDZSd3tlFrnu
WMjKjQq4l1V1MbnKD3oGA/7YQGEUjVZLMLtVLjFKUtNdC6+MHWOPQGF7NMNrx5b0
Y8iurskLBiUOBg9Do9SfkHlYHU3HtlGv3c35HVcwlF2SQxaDcJzWQaySvSFE3zGT
sVT5TlsdmfeWBoDLS0iO8z71yxbEI23+LedQeXmUkpkk8ZnNGJJPxLI9yIHK5DBv
3vEnH1ZqaqQaUh9VULngLZhhBz53iaisSa0saqh7ML7KmmhjGfSiixE/2TMc9Eca
l0LQZE1EfR+8U6KfR34ImnTQNAp2hNWWZjUDJit0sLN1soALwzy+4WIaX5UY8NOW
IjVsL+bBMFW7hBUNtpgXRFEmR+40qnsBmxLPODcFKmq/ov4HunUhqZgHLCjv5TmW
tIegPkqmNcxAHFHUMlZBAS8LA95NFdwws3M32YWuTIRbw2aUrSX/Ec1TWb54QwGJ
UKTMsTrTWIMm+T60y12mBlSsG2zxzglElaO1LqBO9AA96eOb5A1yOizR65/T7Kce
ycRGIe5O9rKrDadFCEun1TaNTocExMsaR8dyTlqpIZlUbjvZBa8=
=urw9
-----END PGP SIGNATURE-----