-----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/jalu9uZGunHyUIFAmqK55wACgkQu9uZGunH
yUIUZw/9GVL+qhXzZcqGY4fYDJnxmusX81wnQd0HeLnsxbpBaCGLUZ9oVSm5N5XK
Qi9qbob3zuh4tTv6bbEUIBrZzwZTBKFWtMvzbZ5TAqrYtvu/8hF93AQma3Zo9RCP
zr53b9G7EY/nLOeycn597c7FOKRgWsVT1Bxf05eCmrOeKL0FLA+KTZNjXGNpow5W
YUWN1La4xj0UORmIj95jvw6VJWcCloUehJMmI/id8M3BNsFBMw3GDpN1Vl7UY7rw
Yr1c4SqxaJfnG2r8bAPl0JQxsNOOv53RJVGJ9tGxgQhu91aFbBv8fzFuec0RKbyw
TMXFxVkRgsHucwbDtmb4Iuy1Z/lkw/qiHKzFoTAKYio82tc1i/NUUXp+xAa+uP5s
WduevV5cE7DRPDF83gS4RgmAM+U1kTIQGWCT9NpZdDmRXEP8XxmUKbd4PAuN9RHV
duccxBmTjjWbqJk3YMCmG3pzWGgCZIlr9p6NncXP1/XkWUQEAu5iM5A0a1Di2gvI
PH/uNMili3fxfOqdSngPYg2z+1UWg/FjVX7QPJWsmrPggiFXD1swM+wjgYB93MLj
6N4ctLIxS7JUTY4Shv6R8K+AcpBknzAoysrZIlP+8/41vIwGVDWZpwmCLn0WxgRG
uGHiHJ8Z1hKZDIO6FmVarqtBVkMMBx4BaXghMzWXhDurJP1Kku4=
=qkQm
-----END PGP SIGNATURE-----