-----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/jalu9uZGunHyUIFAmnL6h4ACgkQu9uZGunH
yUJIvw//ZFeRDKZC7PwprDo8Nnd12l+HZyyRigxCKp8NyG4Ajn80unkSq/u5z4vS
VSPZrHsD6EatHk+t0/2wWXd3B3b2V8vvrxz0jmtXiEoAhm9xf/+byg+B2B+ZyT0f
nEm68y4zNQVCCBW6rxngRwPH/TQqR8f0M8xdbwPRd4mk+B3qhL7wCoSFk7Zn23Bp
WrOoBa+oYkPxcJqGGAvzHZ0DQw0lBou8C2JVEu2Qln/BYSc25WBOC6BSFOx2FEBo
WkYY+6ZbM/KojuIhjwT92193cCXgrlNM0GuJkucoCjYd1nxvkhiXk9gKXMN3hUBE
vmDSrqufd/hfiQav2qaOUxnGmS8XiXATVnke/ogrm3jH3CK6PK3XXsoCvz6ducOy
3zMejf3GQ9SWSlkrt7jd4UnTnohWG+xZ7sb1xdhTaAEV36RPh2KzuRQL9tfxV696
+S5vBndy2PolE9NOZRJMx4hppRo8nUcd4fd448lz4bU1Db7p8uOizmIGB1hvLiol
35QGdwAhvE4LPdgO3QN+0079F9xEBxJx3NAdj+fR7KHkaHPnHF2vN2Ju+7i4Q2vc
QSw8tpTE23MBYnS54BHIGoZs+IZNhT0DY/rFrqNUgtK0LJNuELle2K0QEHHhMPCl
1gB0Vjbju+dULzFOT6fMXJv/JLEZBYu+KwTc1JHqRX8xcPdiQYg=
=sum2
-----END PGP SIGNATURE-----