-----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/jalu9uZGunHyUIFAmnkgcYACgkQu9uZGunH
yUIZ3A/+PDrrV9AhyvKxWE5U91+UTe8dQJcTSL896GfyXNICkDW/0cMKHgPcgL6B
L9nLIgaFStC2rNKhyBNHdRJdNr7q0QXO+xPZPMs6kTOIPfKxzhGCcyvNsypW+s8P
5+AIgkWast0TQS/E4veqwGePrD0whoaViCYDVTXQbT4T146N1M4zhsrAxcaLCG5z
gEX/jXuS1RE2Z1ijhnvfgxo3zQsz3FEN+zyMZqh3pLo0SYCYzEua5RRg6CB5X+hH
lqsKjokTZ7OM3SRk2OtZRLKSIsy9tFjXH+Iu7ktM/YHxBtIG/yUL2DLc0OH/mDMI
54jxGcYcdUvTRIrZG47d1LznOBiGHZoOiQN4yhIpG/jDbk9S+Qssk1tpagW+KSYs
L5/fy1zhELKAvfapCjIi5i0YUgOFytu8KiMfLCEZ1KzP7z3RzwdU5rpGBJn0qK6N
zZ1n4I9l8QJMy/+ypLab6WfqSZ1Zgm+DvzSNVU/ETInigG/aZcsRzNUlqXnVLySk
04DXIX68hPN2uHv3nbN997TGOjMgKCfsYXA/xmFCXOqq5zl5FAPwwh7Ha3OFoTBM
Kuj2UCjjbQ2SfaIKHd1C2Z9AJX/6gSAV84btv7zZchlk+4aDZ+IrczuOKZBGaYNC
tJ35QN+YxK42nLzQGnxoZ9bfjXRAkFa0rq4ihfhgGUeQEVf0Ga8=
=Ge2i
-----END PGP SIGNATURE-----