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

md5:
365c280c6cd21a0a0f1b7b1e47cc7e7d
sha1:
1c33f9a2f49d36677e8fa9d5e22de34d094b7534
sha256:
afa4f567f60fa5cf2ae4832c50f475cd98c79d40e8d4479083139ea7e53a8b0f
sha512:
9759cf59707b7f6f315f59661c48d8fc147fb3b50c65ae4ffb2997563bc8c7cedbdb65639fc0fd7ae9cfe849f9bf3c9895cce5de5d56335c7920db83a6763930

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/jalu9uZGunHyUIFAmk0WuQACgkQu9uZGunH
yULTdRAAuF0WLIDVSPsTK5uH9Sz8bKKLrHpkunWKvMrPMNO5TOu2RFPSYUBplxxQ
768qntRp9mb2nbvgFcFiDA84lGIKPBgi2MyNh8Es7E+uSkRzGOrFEws+1MGR3MSy
7YSjhjDrYR+tkxOxbe/blhgVUmluthQ6BiXEVLVx5NXyBsNyn/oMoq1XMerDxV91
UAghcwhL85mDa9dmJA96bSSbNyHAhWmskg0FyAA+IbITblBI/ntfu4I4sFnO2VjZ
OIlS2J6UiqUuUOqKB/xNYRLiSDCj9T5Lz7cjjxSwf/1GSTCuRj228Oq5IplBYRdw
OzOwnT0rzT2209WMkg1hzPslMN1A2Jedc2lNgdt3PbCMq7dkINWCdJM2XZhq1IoY
9jV+DnRHicSkZhs4d0swK+epp24FPIfKTrkhnk51vdpko/G44tKfwdXKuL/SDgPR
4W2sz2XKGJub2FHpGSa+1EkdiT3vbk0TiAW2wKofEwDyV9i6JvnpT3ocHIZ9A3e9
qLIgNJPHjXz/KcFMtgyRwBedzLocRMe+y/4nBpYIbZdl07S8p5jXXh9igU7VbBUb
8zHFfx6vYHgw5524NS1qAiQJszw2PI+yEzI3VTmsr3/9oAd8X0H4A/6CIVEUQD+k
7EYtE4+lZ8QEXZKNfcaNdgjHlz88Tm49J0iJo8tMuGiuxsCHYww=
=hd0H
-----END PGP SIGNATURE-----