-----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/jalu9uZGunHyUIFAmn5DtQACgkQu9uZGunH
yUIOcg/+K8CIw6jNVELHdr84czhU7BZfSYZSKYBjCMbQGOhQXcDZpyQFj2FaihAJ
GHY/ytCJcEhU99W5dtWMZOjNVitwjvko52oRc/fyAbTpRLsJ1sCiQc6N12Ii4tOm
uIYs/xmDLaFS3Yx9MAtE2UEuy5NV6kHQv3jt7fAu61jy7Afl05zFyqAlG4uPte17
NY8ypAR6DwouI7qfKt05R19jOLEY9Vx00fI9DrQy2pKWKjy9100whu78b72QmPgc
l5SJPuw52+4U5dkYRtOJVrQiSIxVmt28TSKtKgtvk5BXhKASLxuCyfty7cvuAJ8K
npnzo5s/SSLQD0ZtogLvNZvT0OQZbagssAGtKQxjVW/C9f3bKd1wvKgT7UQAwzXg
hP5ioYLxa5XF7csiXdWp4eh5mOT0NIxWDWGPfbUpAEc2YjRXc8Kbm6TE9+y1jFKU
xVgFhMsmhXBn6blNG9mYZRHJ1aV62xRUAo1ZlS5U9wYiE4n5X73s2f/YAo31y/ZD
Kw8lR39T5nCpC5Lsaq3piSyppJ0pGGVgFDOsmN0yXxqZJZMJndbFemOVwpF3p5Yb
AdTHssvoo4qMbU9W4OXXWbC84f6SqTCoTLllYTHd14D9NVosMgpRsI7+QdGiOm+Y
yTkIR47Gv0TsEeZXm//CyxTkVcuCCCZx1NyErAiVm7yjiFyiQIU=
=GVdP
-----END PGP SIGNATURE-----