-----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/jalu9uZGunHyUIFAmrAD+8ACgkQu9uZGunH
yUJL5g/9GqDcJ5TqAnh1jWRLKvYVrMIm90O0LYr6tQMnE0cTiYM3ZbLuMYifEDj6
7bgG8SZHLIFX4KsgV/+9vBcVr35/9CfKaGQteUT43uB1XEEIUIq/IM9XevgtL2rt
CfsJ0MgIizkmCstkIJsCNzKHBwziCp1yyHIQ0h8kH1TguGHqW+YvvWBYMyDTjo00
KMmysWuCOZY6uNAWj5rmt7WEvtGK+82b8Z7kn4Lok8M23dfydeb3DHGkENQCT8lA
zhM6WzRiTJ9UysgTFRBmUoEYL2Cw4kB9tohw6YzMFi5kcrgBJI5D9V/JCXEGLdMd
n8qRnbyRzmxNb/FfTHqekvQuFvVpr6j+PkGt4U5k4SY89Jb7Pvedo2rPfT20J7i2
xzMwsmDqQj1dPp3Qv2O5SnDr+HCjPRqK90JcpyQr9S8Hiq30LrIHHwVynTZC3FaT
9O7xI+T2gMTfG80ISAa3QX0DDOSogWgYe7DLS9seEYm0X2c4d/Cu162iX0FJa/Cy
2cV2qS2mECQvqiydolh+rog004sgNcK6CxC6dIbJaaWAtfsba4MXQaksRNGBvejS
NgYwMaPMd9otFL2DGPn4XpAaUdX8ODAUm13E9L5UJxB8nuQoOtm9j3Tyw5C4TlF9
E5tXkuwEE2CstGtMNd7f+5ZjuxzqJvip/QQkjfm6GtyA1z/Uo1I=
=ES+v
-----END PGP SIGNATURE-----