-----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/jalu9uZGunHyUIFAmqrvMwACgkQu9uZGunH
yULk+BAAsEYYD9yenjbKL00NrroxsL53UARURiPtYHGe9419WTke8GIeU4ekQdZC
dz6my5yftS1qLxZmEYhkYBpDTMwTS5Mq5IVFPSfmxyrDtC4mvZASUT3c44/vx94M
/iCbcQCkTmqt2Qngo0Z1vYvnwktba+3aMV1kVc/00FvmOkwwRYKxpmArJjMxYx6R
MR9xcN+SKj1ijfj5c0zPLIgcB/4bmxnYWuj/02JLtKUlQFyOCWLWu9ARTGxCJJ2u
6xxV4MsMA4SksjTfNvrcWur/WqWCdpMFGrQAo+lBSxB6vq6sgMcSJRPQxDOSzMRe
aWwIlNgzijvyVrRhwGvaa3l/u8ppgTPH13cwTwtc8jFODcIAHM7WEVGxyyoujfgk
BOeXm8O5BfepUBA9paEtx9wP2bL7NIzpnrNXSRlKtbVYAB3QhvM9iesjx1t7aNNQ
GfI1cD68MJeTyklPg1Fo0qN0RmGyb4vEqZKmj+3egNVgG26zz8ggNd6bsb2v5x+g
9oQd0YiggebQhJCyksiZlmTleysawFPRhvJJN2Xc7JkFSTkFFO8FxkhFxIR9F8Qr
fat5x0PaeqRP0w9jgdOI/bPfp/d8Dsaibmx5RlLsiHLg/8pyhCf7WH6utP/R5ZVP
jrCymP9ulqQKNMY4+THChJAkMKO6ziID7KyXMaDrXWXNzeDxxZw=
=bC3E
-----END PGP SIGNATURE-----