-----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/jalu9uZGunHyUIFAmn7xx0ACgkQu9uZGunH
yUIrww/+O+3BwRs2VZdbsSO4fSVUi/OjuFT1wsM4T8Us+iUMn8CuUM4y90+V3JuK
4stNuUnrUr+cZ2lrZuOJ6GqOeGyk38e1kdP2cZ5MELHFQbg7FV9eQ1S51IWrIXQb
NMhuTVLFuflYLqtKpf/ZBthpcSPL/zIIv/Z9p5871XEIqfwo+ToZzRFfwFqMlcCo
0xt4IK8Y7setjIsvUaT9mZqJ+A8MnCtduoiDx5ZxdvhlMGFrkv54SiDNL6HApoqe
XfWDVsNE0ny+RWGZOZqMwGDHdSChPnxEfZkDDQOryzaqGm9ApX9IQgpSF1wQIndt
3LR5Qq6lvO+5Bzsgx0Q+FS1Ik07WSkk7KE9Dx7tDs1RwhUwG47ekUqi85rnG+4m6
fEEJ8mC2p9Kvrg+a4F0a41KzgQYoNtEWQv/V2LmWiX2VxggiiN3HFt4tmVNYOEZA
b9xgmyy0AKRrmhfyUD5AfbuhFWSD3TwLy/RoesTDV3Jq2uGmxcDcWPYs3ONx7fB8
Gf2P6rs9xf781w0gpmPGRHeqT857WSPVWCiezrqc+rJf/GsnSFFEuadoZQFjma9C
hs6Hs21+arLBtcL0KXkEWg+HnHWryS3RVlfLH7Ovze/fLkTqe1K/ohAzrLZ+tqj3
XFvUlunzDi65OFXkWIKxmVvsIY/UOExaZy2H2G96CYYVlyQFqXU=
=r6Dx
-----END PGP SIGNATURE-----