-----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/jalu9uZGunHyUIFAml3LIEACgkQu9uZGunH
yUKNfQ/+NiJbkXYMLNSWjo1PdksVj3ajw+4YsXc/armxzgBGo5XdOqYB9NBbVRo4
42qci+YiAHkemaq8KN1bgQ3yHu4SY34PnOtnD9pMmYzEFrqr07MCFafxcW2m29rQ
j3BCDgMTLghApFxeah3HFIGMQ89w2z5EWxMYTK+fmtFPA8RN1MAdOnExkE4dCtPH
TpdKtLkmlXuiAr2TdoaLWwxhDaX3Dq+U4PBDLjiAk6BnrUsmn2yoKn4citHedKJR
DgnKb3qmW/d9CVB4T/VuW1TQYUzcPobj12juWmAUK5RFjV0DW2cXxz9O9Qo8Y7Cy
6FJGxJ7sS/SH5pQoJNV5pF2tFwbSKMZ5djZloRGQburNaaPnik/9iPQqQW5wI4V8
QS35koXtVGRTYHI+eY3XhWC1nuu/tofUYR9v2yvFt/R1AFYsWYzD5BypTgcXnQnW
FfEKq8Cajy7dBXwikmLTuSCef77eVfDPFyBrqcyhmDKLCmXXHbbDoXLeNPJHMgh1
MCbq+dF6PyID0M+Ar4amO492iMpG3mx9pxMsv1xxnaANTPGL+sNWSxXSgAGcvMb6
34zIuNrNsvQtY9A74bIkWIa5HdW14fa4rCPxiUEr0z5C5iM8HydoZdq+HCoQK3HH
9g+9nExbfOYBbgAkE7q1LJ95lRuup0Yg1fYj3r2WK2/NggE/eDY=
=Q+kQ
-----END PGP SIGNATURE-----