-----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/jalu9uZGunHyUIFAmoMhXMACgkQu9uZGunH
yULV8g/+L6gi65GahQ600XY9gjAhJFaEMLCIB26aFElEX2lNmYkk0m9++GDFT7F9
0cEQZx+KXneZ0reFFEilK2JQKyrJvz3rerUq5mFdvP7y2Oj1cTNvi+JBPZ5zNe+T
K2AOgER3CpJAeQT4rMHXSN7XKI7XLOUsfXcdpwNgZ2TN7vrC6OIO2LakK05BDZD/
0CTree2seATG/yuihW3LG77V2WgmTTUsHiLspoLOV6e/oyPNJFVtIjslvFDxDyGx
/aUlTbc0WeIugh+DLmOBKMxY5Bj+ktb8rbs4Kl0pcVNElEADb2fyW6MBkSa7yIDn
5U9LVGxZl78Fgh31NyjKS3AIr6IfVwZTnF4y68M3Vana3BebaHPO2fyYC/Rr5rXY
XQuwbJ7MLm4z74GunnqPuRmxYD9RV++puETlGQvx2OpVcPn536sE4lLgBoAHkLth
vupS4mbTHT38edj/UQvECQ9281KtMq/cVBXcFsvItLNzdzQeQftxSTgh6nApUOEf
aRHn5qBQ6zCzaJWShSdvJ8qo5PC6gcMM7el/2/lKG7OYUI4zpYntHmj3wIs6VH8P
GCV/vQOg8pRMTVUhTNgJegHXuk9tLMAdnThaxKD7lYPMKAeZydrPjVbpq6elw5e1
JYW+W3W6iNTNDEXaoz3YzzoSLSg0pajTUS6/9/oQwRuMMkYYj2g=
=5P3w
-----END PGP SIGNATURE-----