-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
05a39db99bef224495078c24db168869
sha1:
f72529f5f4831038b3f783aec8d5207175c0283f
sha256:
f37be6a7a14e63d2b44f67616c070b26b71266a3122c8e80cbddcb26f8cabdc0
sha512:
b152cb08a2cdd707284e19e5d50e22c2e0f1d00fa4aefa329c5b30fd7024ae01201459dfd77170f9f4f1f4c7ce3ff02191c0204cbcf55bf0e4e524e7f145b70c

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/jalu9uZGunHyUIFAmpB130ACgkQu9uZGunH
yUKbhg//b7JV6zUDZuohaEDqnQDVqm2oUhswyfOCOhHYPZdmDCrzn+ZKOcqZBf/U
0YzDsnH1mfAD31jwtKyez3bbV8r92K4rKf6EMEYMghnTq7/o2rImg+jpXmGXpK0M
+tmPCU968vssUekjTy83PUC/MXDnFySQVVWKtX6uCXJdRWUNGgMSAV8GBG334v30
BRWy8b97gU7sw595OMmFnaRx+MxE4cEESLQCSTeFincc/DOePFtLn0sPy08aSkwu
H1D7yLr5fblXpkF3QnnVVakjJgDINepfcBbptp7azhXxr0cwfT9aWdAUeBMpe7XB
h+EGdOFchWlXwlg9hy5ynfAXQALC6Gzcj2I/k5rPKe6NmIGNlpsXs3u6qELxwhUL
2tLR1wDSMWZIU2Nr5HUKfpp3SqiY51gu2TWleNIWZJ07UqIgb/V+v4XRYCJEfnf/
8fjzQ22cqxTTMuF0jAWkiBaEcG3ChRNJYL9vkZrlrlqR+2F7ui13A38ydOhwBakU
m69/RKPjQOlpf6y56yeeezUoKQEfbsMfO/c+KPhJMqLk00ijLRKaNQ7jhDnCiN4V
1ok5AAGkiU0dxEgW9ovl2GtdmHOKHF55jfihXWEFyV3Atqvm1aIh4A0A/+KS2+7c
yulOdVgNVxPBJTpmV/A84OgHI16TRAy+DT6r5SARd4cKvHkY2l0=
=GWqM
-----END PGP SIGNATURE-----