-----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/jalu9uZGunHyUIFAmkWGPQACgkQu9uZGunH
yUKzww/9F2vh7Aqj9Ld7eCA6E91enOKj+HdFauV4oJWLsDrFZ+p+1Ts23+DMlz2b
BU6jE6wHXoSsme6rMuzyFfhQLdDnCWgHziPKsx44z1kpJdc25tPE6T49G07UU/YH
Y1/WVcfVATFOZE0MhxwKzh706eFuIDY3a9MhfKR3Z9LF/I4JE8ChfPp/BTuyKsTQ
hp/NgQ7oCRVyHMGL1K1QZKoL55lQPqqcAHqjGCem/L3wV5EW2Nhn4u3ct8oGgcyo
pYb4N8i79QS4ZqG+9/ytH+2gBxbsTsdRsJlMhC0uoT82dROgeT9leiKFK03oJmne
dfEpy2MDILir7sdoUlsoq18uZcN4TGskp9F7uPnqeHLwaxUU+/WyvfRHCyZSx4zb
8cPpaPhjoSouAyxf+89d5IHVcRjEO5UNmRaX7cbUkA6t5/JT2ykiZIOAAIuqc6Je
GyH82qDIPEvY8uFz2OYxgy/EIrn4OFfbu8SkizFWgg/Yf198r8dC0tZkLU8pgtwu
y0FXCF5t/5Z8bIFahPf1YBBeZCXjztZxJtfw1kc7a8OcRhV73vI2cA9QEfIXhBOs
0nFmgA9SIMaZL4TSX8Txw8y0ybzn6duNkYE/Y6e1nu/GhbJGi+i4TdvXl8ZXyeKc
KBpJ7WhUUp2HmuoIuDKIJ9mk4SmglyaTDHk1NFWFL7QJ8ME7I6c=
=HbWk
-----END PGP SIGNATURE-----