-----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/jalu9uZGunHyUIFAmouiRIACgkQu9uZGunH
yUIGjhAAnA1d0US4GzwgNOVZ0Pnx8bjvsCTaPrce75rEqEL7rsH+Yi2NxdhCh31o
u4QjS9i+csaS2ZhyNtu/pAsNwD4PZ4Bymp8WLrngrK/xKT0LbhXVuIkFc4tqlE0b
QJqicnN4DifxhAKERvviZn8xymMwDVYgauqCZNZWQyCnohskSxh1nyk7OeQWzwSM
+c4ezrIoUfFzK/YiYf5lmKSFU8ClV8z57Hz1p0V+6iBr1l9Iwhp8IpeJuPWCrgfN
NYMt5g0eRIijQRU6WAqZlj1VGkL82s297dx3yqO7n5KzxkhuKB2n5eadngBuQHWC
VAKeuvJ4033euSnftl0aQDEBaRAZONZJsTg9VOtzPB1qz2PegpnM66T8p6BElmYj
64MhofMMT6RKdmhpoqwGa3gkvRqzbbjbQLGYjDZLzZ6m8exurmGVTnwFJDIEWzwi
CWmW2jypl6LYKVPiwsEztFlp9tPossWVxQv/B/nkBNExzZ3XfTkVxqezgE2o4rTh
0P2gIMWzO80IUPVRSkLK9ct59dA180nPK6CK2vyzB9dbw1i9vqXSSVluHo1He4Ot
yfX7ZWauoOCXwHgz00zKC6FjVn5W2u6ZZTfwZNf8vd3xrshs5lv1mTqDMwsKDtRZ
TeVisGzfmhQBq06is2pW2pfJkX8IFabOqs+J13t/b3nq26Xegdk=
=Ew5M
-----END PGP SIGNATURE-----