-----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/jalu9uZGunHyUIFAmkicFwACgkQu9uZGunH
yULcTQ/8C+jRzZLuuZelPhq4DVaQ9coYM9e3Nw/eVlIq9ospKL7AoTNeQhHtlkIp
P0VA5hry5UUxubYpvhzRv8RDJ8jpDbpGwpednrpcRWEYo5Wo6t7MdnQAXBgsh+rf
SUi4T77WQAYmPB38CSJUD2dkraiNlZk6xz8NSm3HZ1oIKjVLvdH487QTeldG5HDK
99ccz53/CB7NXoQiM0ql0DFcE7jnK1AAGUEIbKCXtE8SMlusCuRFVlt3b3ivKGFC
0l37b+quLOkph5LSZ+FNx33Zd00en+B/npCxrKbamxuVGPHz5M2fR8aKAi0IpZYU
tlZjaPOz7NMNLWvMCY7fFvaorcwUZU5Y4wQOPeZ0yf/OSehkNEK12gqPHIsjTq0G
yADeFIzReyH8mC6EU64DU7TVMK+R7mChjoeRPv280xVlAsvEjt83OwGAGdS3eG0C
Zao3irC0ozDbefHH6K63nS+vKDPtuhg9hQsM8Akqissb5U2hlc59Rs+SgO5jZRnh
Mup5gFztp2KSnWX/97wW8RKbsMSKkV0j/AFzEBNEXjQGtQJW+mILYUUPxHwRs3Ic
15KD/fz1TUw9qirunpz8B8sVyaOUeU0XdjHoAR/NypPyHrL8w7DH1ux5aTpC8G/+
XmKn0dEqmI8BhU5nIVt0mR0SNWumNWAoYdrTVpeemIPPGRQGhfY=
=IozA
-----END PGP SIGNATURE-----