md5:
fc30cc454a04391580dc0e6183cb9ae9
sha1:
f9e1630733d8e92fc6fd69d13fc150645c51d315
sha256:
4b9fbb3377aaaa537b6d90eba98ea4675353a4f5ae86dc0d93f8fa98745213a2
sha512:
482b3119164d0d6386fca232e551efe9a1d68ef56412426026088f3a6839b4421f0b13fa61e09e6de10575084ef3bccdab2bf6f58d0743ade2f7089a3b125959

Use https://sourceforge.net/projects/quickhash/ 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.