-----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/jalu9uZGunHyUIFAml+7g8ACgkQu9uZGunH
yULJKA//afgiCaBxXcXX3PXmcCpFr8+TxJ22zPINxaCnxfubHaXT4fzmHEry8usH
r/yDMv9VIFGZPxHKdF3SjwsoUpcHgbJTWA+uTIiAW3M9kwCVYtJkvMzEahFQdYIm
e2axrS9kqQCp/QNAY5Tm8Yi0va9raATi/T9skpzI0/VGNSEJO/u/859SZOxEPMa5
FyXt7+iUeLCQVwD2T9D06Wg03TOJBHFRcYryh/PqCzMc+1C0bFOFlBg3rdRFEnIN
SzQzsMa4tcLC+E3+UW26C6yXyUHsR3k4NEMdN7VkkSuTXhVJYXhHLLja2vLXB84T
quAeGek+7N+agc9tUJitNC+/lsUPHgz70kNe+jmMw4+EpFWXvx3G200OSqkuIXOQ
+R0rSiOkl4zzTyrkFBZZGivJQly6QJaFXyl0o2oGQ+P6ySGw79JT+8Sa8rdDm8qY
7ishH3Y89w7KEbWsP79WwZllm1mmcCrt548O4nMtK91Iqhy0ewGJ2qLhuL51tqG+
34qmXXb5w5A0PS1+EWM1ollylHY3n2BfRKdUlivhrxkxL4h9L/iACWSvntj9ld5w
pipoMihrecQwQEHWZ+dajw1PdhBIqDjvATBm7kujxiAqTQPX+wJY8u7y5g0+Xwtt
mjWm2WHfxNuWDTpjBu6nCZCD0Zh7Zmh90QHNXSqH44icVHqNrTM=
=iBNo
-----END PGP SIGNATURE-----