-----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/jalu9uZGunHyUIFAmn/BXQACgkQu9uZGunH
yUKHPw//V5S/3iFp4LOl6/5Ts4v/ZqW1GEjOsw9et9MHWffm78d6eDyZY0EXbSQz
lTr7LwY5BVZxSVpY7GazjClt+QAP1aDpli9CVmGkjopuMQeXk74QTZGVbK8SWpoh
B0Kx2vW+n8v+SIg330GZVRQ7ECWqIztB+SG3UMAVFYcclZDjHU/G6xOzlEYLaHGj
GM+wJOBRGHT++qMQivUYZ2Oc7DdJEEYyAhiPTYIINhovnOlnzWmvKSFomgAjdqgd
NXA7Sd+PaUhZUXOpGvPt3noHFiZOxcZ/xv+oMVRFvUC/dUZCuxvXMIITDo5Q4JZ0
WCSNzsAt4gGFybDM0pHfFQ1E2FuxN2KZKe+qbAtW+7ilCzRwHX2VUxcfpanIrivm
ja6Y7WzxO2tKMcVbiWrLTMRK78B/ArpP/SlB9vped7C68jxbgKb6spTYxiKN8fZB
pqsI1iLGq+jaqeZEiTwhG0gT81v2ziUQGWecjSComNeEx88mfZ9StXnMZ8fPmyBF
zBfDGn+QHIeW+y1V2MqZpHk/pPtXjuCp3fWKUyAb2QhTucLOf/OPWim57IIbOw07
Io0/pnGNUtNUd7PAkfpKwinqVP6sFfyXCoImWJuplO7THmjbzTWAUg2qMj6PWenB
WDVWDNfQQ/VcVCiA8O8FRYn+5w8UNJZTVhmrKsz00H0FOuM2rVg=
=H9d4
-----END PGP SIGNATURE-----