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

md5:
e278028e50b73b55cd6a06d0c5bb3524
sha1:
dc11ccf4657fa4ac008ee5ddb89c27e40b7477c9
sha256:
2ba029d1c84724f79740c0296244fd6056f12aa1be1925134d9141f9d036ac0b
sha512:
279bd76c4abda7efcfc181ce35ac993a99a11d60d34283d0e7b0d15443a6ca1e1c6b75444193c075f865bfa0f8b574189e6e91e6980b89ee767ee5874b7f5b4a

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/jalu9uZGunHyUIFAmcwH/gACgkQu9uZGunH
yUJC9w//TOD35rv8VcZ/UMnXnkFWgbwGojYTPuesqFVnIGcF4kCnUEq9Gz9Gxn5V
edhXQwxBUBf0sgv5woHbszgguRtj6hnB8woCBPS6zPrXUZHZv+3guacVQ6uG96Dl
c4rWxqQ7/JPgqMfVDq2VVDgINeUfvq3NdBg0knWwV1yNsUtghU6SDof2DcbHbcKD
k3xvLxuFsZ99tIBbiWK2n5jlyYsKWPoen0U7ABJsSFZAfVwoo0IT9oEij3GdvbZ9
Gf4fjU6/WGr/2Y+N4HoSVCssfZC7AE7W5AMv0xS8KthWxz+uAgVPonev6TKD/VT3
EshCK3ilG2oFhu50ebcCJui7veyx2kaZk3Q3cwbqHX6wwnd0TIH9pMNrtH44vYcL
wyMb3rJWusPbx+mkBI3D+fM/Sge0UaVhk4fU1PNuXpEmBVffApNta/2q1YpVBCzF
T7W3zvks27J2bYxunH6lSsHwSMKAiuKgSPnSfcbTP/p3O8dFLiC8YScEiySwIhBK
oHa84EC37toZd+QjU2wkA20WjIInBE6N1Xt31rme51rv5LiSrEUN5RkcsZmDJztP
skafnaB/Tvy1T+sEjQOyvJUbxazfam8ccv4xH1/6NL+UFS5rPofkpOvkqLgC1LjU
g9qMnFwj3F5fMC1/uUj4pYHdUJleGu8ZtyNQ7jJxfj7pxkpx0HQ=
=q4HI
-----END PGP SIGNATURE-----