-----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/jalu9uZGunHyUIFAmnoaEEACgkQu9uZGunH
yUI8dw/+L4kZz7Z3FInt2aJP8xYgwF7qnTI9ShJKmx4aGk67hYvM+5811Juys5nd
EIFCFQ+246kjJslzKljxlpog5ubmE2Xiz3aP4J4TH7ib4t0IhmYlbcPK0QWZAJCn
opnDXrdGDDTzAAlsGMQ2M0M+yp3crHI/hL14JGNm7fS4V4mBXKQeXjQ0m7kWeU/9
6cdktbCalUiK192+7yZdJ8zY2ghhf6nmzCGs0v9j3GlvbLeD8M1CFFwDRQ2Keimm
S30Z+eNSOjcrtW3dXnMgNfXrAKooOm6t4YNVkqWR0qw/B7BkhUMXkRGQYpv2yTXS
QVQb8yrFP8KGzr5h4hLluolTbmojtMHRuGxNmFEbnDnqsPhfK5l1qLvX6y5gaIFC
9Tdlu4myGjV1zL8i81CWWQ5wjwBhmr7Gzajm+YIAK8XXV1W0ghgWJutC/zGW+o9z
2nS2ZPUZBKlr9ILIbdhZTGt3Y3OBLMKBy7J/dUUzePmWupllUv2q8Cr/YOQFX1XP
M0Pg3N5DcQFJ4cvU4Adtv/3j9L3F9XJGnoDVLnKo9AveXe/D614Snc6yS/MrEBoU
Bt3RQmC1HqOc6Ub80cq8/wzcfoVOw5L1ZGy/gOAKUIQshWp0jh8nDxMDf8r0rivs
foWIwyADvqS0MGBR6MUtExgsJMTga7fp2+wbqM5XPNNhebBpE3E=
=cmpR
-----END PGP SIGNATURE-----