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

md5:
d71db59e76e908f2810b6dcf9b742ca1
sha1:
3713c76a9a230d30d2d28ccc0e1c164eb73916ca
sha256:
363f5edef02500bb9faf5a557bb5b77c463e3b7f11fcee283ff4d0614d1e88d8
sha512:
9b2ced771ecae2175569d0a6cfd02278ddd1d1d2398e48a5d9de31b7a66cbaf831ed8652cc101a1cff46a9176ffe9b835fc728fe1484a1e7c853ca2c4d9d813d

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/jalu9uZGunHyUIFAmq0b+YACgkQu9uZGunH
yUJoGxAApqxF9H6ZQcW81/3pUElgmNlwffee9MeeSyK0Nok5Jo02/5RgT2uG1UCn
iZvfBsdacrhiZhS5geyl8n8qxEGWohFJbOUc42OLGoP5nrTJf9Enq1dHFkfzbwwT
Bs6PwDGIjlsIC2Cv9r2cFB6UoAYT5SHgQnRvdQoUo/QQfSJ3vW/ZR71WR+laP4l1
DlbjjD4Jm15q88Mtd7jeRzGLrgmNRwBLabZ49mp2IGkQA7CkeP1YkKcOmRQevbwS
+q12k8Isv4nvxbGOm9rv8BPWjtmUF0OE+dnddlYzRf1uKRii63/hjWwDmPfZuw4G
if1uLoZwR5aozc/xCz3zYyJ0FcPFeJVe9YPjTTzfFQEMSnJhEVuBlYt9y3uPBf28
4P+WOmGyXAvFNULxJSq7UTam/ayY0c++ffMklwxls4jy2iqpotT0+f7gDDoHihf3
Z0zF3ilFGeLXmN5XmlGh1LoHsIsjybUsJVsnZ6X1NUX490BpGRjBylbp9X33TXyw
z6VGxzuydhVxgQqeQLjYB0SB+QGAijHZNDqxCNe0P1hyn+Fd/cdfdUrTq0NPGLba
cAIBmeRH69jVxadr2TlV4KmqGZxvujnIUVlFpWi1NZxg1odFuymJxg4J/57VH8Fa
UQWclz8Ls6T7S5RVWvCdBlRYKQmwf7Ue08KbguVj3W/BxchdeAc=
=fT/4
-----END PGP SIGNATURE-----