-----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/jalu9uZGunHyUIFAmoPiQcACgkQu9uZGunH
yUKUCBAAgFWk6N/kiZNwDVdFOv8hXC2dS7aTFMIfxrqvS3Hd0zQ325j2DhggvDR6
MQB/CVf3z3oACN2ProG8USMAJurziWX+zkxk584Bc6acpE20hzQa4fDNuBsgO01S
MuRNrnH/yOcfqQMxkq2emNJkC1Z4hU5u6dguvDpmvCZKsA1G1TXqscfA7VHbZ49/
ga6HvTr8FYxEGLuN/FtceSUFf1xtQGxd7v1U17sGF+0SxrYv1uv2EZBkr3r8GgRp
JPYFaiSNupzt5b6IKv/SsFKRny4n+daDq3/MavW/lq0qiHociAeDsl9eINr4Dwf6
6fWq1HZkKc0l7sQZqEHa8Tg0AInnrSlUo8JdS4F6nGM4A3FiHXmDZQkqVphrap7L
DnrqBIguzAIpDHlTvUGX2HMHnL6mmLH4kqC/2+qPw+fu5j8TZ3+0yr89FgyIAOmi
aX1tSfH0xVNFSszd1PVzHWFJylye9Rw4tR4OPVls+ZSL486lbbXEhiW+NQqXPBMn
tlaslt2Zw28VEhLwysWQ5wZeZU/HJ+dBvcNeTJ3NyTAOaK4Q95GoxOBWNmVudtp7
YQjsi7pSSf/lAOrK4KgyfcNvauLB96dlzvLlaJUG2gGo0v21IdNyldB/0rWiTuUH
y0F6y8Sa43UAbrpjIqjPPmmxiAVoh4kLWCbnCYAbeTT73sD7axg=
=Mywk
-----END PGP SIGNATURE-----