-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

md5:
7717c2c1a11c37f3e828445c8b19ec42
sha1:
82c2978255444fb7a824eefb1b39a59920e1eb52
sha256:
984e8838c7e363f29b0e59cb601aa35b18f941337e388eaccc9e355e49c90f43
sha512:
538a8b595c44f3380e43fd077fb3ab5c1a1f9a07ac8ad0e08c95fcb627f44a619f35fc02d8af9cf0bf15e3f44b5d36a5133f1a0cb419b937ec0bb88d36131731

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/jalu9uZGunHyUIFAmrLBJkACgkQu9uZGunH
yUInUA//TDGw4UF5Uq/YfQdfm2Qkv+VQXTPJKP60UJzzWEvmcqseiOMO6LS5y6GT
SE9/1Uu/Zu2R82Wea3GZCFK6XoDf6FtiPTAOYuPlHeq1q7pHCURkN0TY5iulH4Wm
16meHdq5umkpC3vZNoTVghqS1VAl76qtDrLKYxdCwqwpneKbYqBcNApW3nhcitQu
Be0B4UzPuqJFFq5Qsw4cNi6wo2M9nBp3ERW0UmoUlKB1wNWcwDQB/39lf6Aj4DuX
RX38bEuwEOMO3AQUIbt4WgFiCieqLGS5a3DPyD2efjZRXxUMx1AopvRBblJKjgr9
yEUMDASF2BuWpHBLhgFRaC90lWEicbZpmGT7zOL+0jriAmdzEKzEtIl2TP7UKgm3
Jh3Ap0tDIjsuKQDUqd6xiPO0Vo3MfA1i9B3Q784soVIJpT+9WTHYI4m/RcBOxFrP
FVPnxe0d4bz25zzWR2SR8G2PPjJSiuJko8YyTtPIcGoGJW5kh1baDwrH5X0X50se
bRPS2e/iqIXHQUKdG/ZnYFk8Z81GJXFwZSJR8nLvnav2J7vWAAroBP/jF2lvHSQP
mKUh9XYJ7Or4t0xtFtwxCtOr9s8j/OqO6JW/nL4+Lm2sbKUHJfS5v95dVof/41nJ
au62uWsJNoA56ao8asUJKGc5wgUnPE1xEKs+5xgkHiILpGWfLTc=
=Ca8T
-----END PGP SIGNATURE-----