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

md5:
2e528092dd8428d62ac5dfa69a46be7c
sha1:
71d7487b62373fd107d633b50b31743419eea92e
sha256:
b8cc442963f5abf7452d95aa0ac9e703024302110e14c90fb788fa0be33ce5bd
sha512:
731ba4c53953c73a727bcd636e18aac4eb8908d16a6258867bbba6179f82a1d45c942e70b61cfa01948776f95871a9b3c34a7c3d5fdf1d8df6261d77dfed7806

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/jalu9uZGunHyUIFAmp9HKAACgkQu9uZGunH
yULoIA//QReCTggeBzzz1NappzCyiSJZl8LuP64fQ3OzvGKTucPSTE2zWqwwsr5t
9S7D1Z1bHUi7AgqcBUkGlGe4BUwxYWrxedQvQiDmWS7NyDFPhw4yxcRL2xTDoqT0
xVZ/WMIDHsSU2NpblWv92YZhjHOrQIlA9lgiZTu/lGmU87fygu04n7W9ChJpm9Hv
/tY/p9RF56YK4pyBNF5Mcmlz4/cXWmTVgCp65RduWVKSLnF6CtLkHCPzH4D39ZPu
Vftv/21CUsdN4tqE2XqWCPZEV+CCUILXd+AYsYA1S9RssV4tgtsjzt3N9EI5AYqK
vOKNK09p2lckYR4+L2i+tnm07Z5/SHNI4KnZh+8HxTrGiBjVYCNe5hOcMu+CIXWa
dq2X/d8CvWaNiUGCEOE8KBzTUrYLR5qVMdyJvtiq+dYPNZ4ZSOEC77OuJYq7m6m3
r4i/V+if7EYWfGqdfB5mZZSYil/+C3jndSm3jFw+flgL9bUS0j8ibHs6+s1ZkYhD
GZ5TjyigZVuhkyzgo/irnEXrD9EYehR9jwpx4pZ+iznpdsBNW/WdZlY0ejfOme7H
se7xSq248qHRLd/WOGBf9HF5m8ypjvjxPpPqE4HX2x0fUorqAoGhwAlWsKxRA7en
B5Lb9JLsCoxPrFMMVIiW6+4nNGhM94Sc5FEhZQy1YIt1T/uHCwY=
=J6jN
-----END PGP SIGNATURE-----