-----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/jalu9uZGunHyUIFAmo7A74ACgkQu9uZGunH
yUJhuhAAurBPB/kMRPsHNoAATaIgO2BFij5capkgJrvyxwSvz2Ao1ALboBSWuPm9
c/BIg7I8aM5CMUq6HLEeag4MjPFQqFKZvUbq3RC6aBXbEFENHpi/0kq0QUYWmK4Z
+8i7hgZ7fsh/MnJ693MDyojT6pPgLg4B00nQw8juhSxaNpLL85p+MOp9OoYdG2vi
y3X1oIboZip+7B9E7QbVgW7UsEJHjcLtDWx0Gbzh0McATyL2Zz8/XhsXfIaiN1rT
/LpqSQ1hv2upGIB49WoO7tneiXFJgi/LjiOd9XnchiwqZdY/47XfXiR+EcuXxT/r
BubLKN/5+2VsUQrRO31Ay+rcml3ra8WzFY4xSl6kbIhxPTnyYsqCoIstvJ6NWZ0b
zYOk5KBjBhcDfg1D4uPlcw7W+XjRSyXD4BT4tcVqaeKT4SvWqCGEFugDxXkcX0UN
3HLLhIrThXEK1X9U8wa2o4byXzYvIYWDUf2hOTzz6UDO8yOddkdtGNE1n5V0AwhT
damHKftToIWXKRhWYf+zQDGlqmL4QSTNOljPTJphMeu9iFkxSGyCU6cojYHGMD5k
VjRHwS2EQR5uZ6J18689j0VD6Cb4MrQhoiknkqlL8oiq4bPOVrr52rM5Inx/nHqt
0TPe3SihRam16r8qu7Fu1MqqQ5AfHpjrVKvhe0HFWqIqtm5ygw8=
=D+YI
-----END PGP SIGNATURE-----