-----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/jalu9uZGunHyUIFAmn5wmcACgkQu9uZGunH
yUI2LRAAjcvbKmiAZa21XassymCs7KClVCXkLGinN6yQ5glK5NbsHCwRZxMHhwB6
jvcnWdoz0SYXfXDh6Hrd7qzk8M4IKXaPVeE2TgCnwOPVDChHqMqw1hefR0f/uDf8
tqDjbljt196bL0TQ8fK3FG6DwwkahvxItYTlSCnZ2wSBCN0lv3hrkTlk7DMICHad
e+W3iwBtu6Nn0H4+AtJIm8v/ba8TTF1v/rrEo+ODtmoBo/bZLW8rTzHe98XgD4dZ
nmaHbn+oz2UTIVMSoBiaWmLPPFbHYep8Pv4zg5FOplUliMIhhbBhxv/YS6ruYaWn
ipA1EkL//Q87UFkP5SigSQjq4TM0pHcKLAryl7qa6xSp8gVXxQekmdHWlZ2GW9Gq
1WnoAcHRqJXREW4pxm0IS917WZFAKQpk4n5VzYD7oldarMdftwa/seJ1GV/Q9J4U
/Y0CVJIUInl5FHMxcFI3+vcQ/mTE6ERu7py7eawQ077XWBJoCCrwWX4QEYuuj6Hf
+JpGRyUP1jS1OI9PNBsTgn2a7z0thiNqPg/v9wLADWh4ryS6EJkde5IYwsho4mmb
E6N3BYSYlHkYJVgr4od/mIbstEMsuunvgo0fGA7p+3U9nubUMFkIqzcRxmJCtHiG
6n/tPe+KhrYTRhCveEQb7Vh4pcu1DiwKy0BPBl/wfWGqPaWL1N8=
=dO5u
-----END PGP SIGNATURE-----