Flood göndermek, insanların floodlarını okumak ve diğer insanlarla bağlantı kurmak için sosyal Floodlar ve Flood Yanıtları Motorumuza kaydolun.

Oturum aç

Flood göndermek, insanların floodlarını okumak ve diğer insanlarla bağlantı kurmak için sosyal Floodlar ve Flood Yanıtları Motorumuza giriş yapın.

Şifremi hatırlamıyorum

Şifreni mi unuttun? Lütfen e-mail adresinizi giriniz. Bir bağlantı alacaksınız ve e-posta yoluyla yeni bir şifre oluşturacaksınız.

3 ve kadim dostu 1 olan sj'yi rakamla giriniz. ( 31 )

Üzgünüz, Flood yazma yetkiniz yok, Flood girmek için giriş yapmalısınız.

Lütfen bu Floodun neden bildirilmesi gerektiğini düşündüğünüzü kısaca açıklayın.

Lütfen bu cevabın neden bildirilmesi gerektiğini kısaca açıklayın.

Please briefly explain why you feel this user should be reported.

Easy automated checksum checking on windows?

I know I could probably run a script and use the built in one but I’m usually pretty terrible at that. I just want to basically create a checksum and then verify it every now and then to see if the file got corrupted at some point. I have backups and a cloud copy of the stuff I want to check, but it just be nice to get an email saying hey these files got corrupted.

Benzer Yazılar

Yorum eklemek için giriş yapmalısınız.

3 Yorumları

  1. I have the same use case than you. MD5 checksums just in case corruptions appear, if my HDD gets mad, i want to know what has been corrupted.

    I use a software called “hashcheck”. You can generate all checksums and store them in a file. Then you double click the file and hashcheck will check everything.

  2. A couple options both with a simple command line interface:

    1. crccheckcopy: https://www.starmessagesoftware.com/crccheckcopy
    2. hashdeep / md5deep: http://md5deep.sourceforge.net/


    To create hashes:

    CrcCheckCopy /scan c:my-source-folder

    Will create a file “CRCstamps.txt”. You can rename it as you see fit, just be sure to rename it to “CRCstamps.txt” and put it in same folder as CRCCheckCopy file to use it to verify files.

    To check other files with created hashes:

    CheckCopy /verify c:my-destination-folder

    Requires above “CRCstamps.txt” file but will compare hashes and spit out results.


    While hashdeep / md5deep can be pretty daunting with lots of options, just use MD5Deep:

    Create hashes:

    md5deep.exe -r -e [path to folder i.e. “D:FILES*”] > md5log.txt

    -r = recursive (drive through subdirctories)
    -e = display estimated time remaining
    md5log.txt = name this log whatever you want, will store hashes here

    This will generate a log “md5log.txt” in same folder as the md5deep.exe file from files in the “D:FILES\*” folder.

    To compare hashes from files generated

    md5deep.exe -e -r -m “md5log.txt” “E:BACKUP*”
    md5deep.exe -e -r -x “md5log.txt” “E:BACKUP*”

    -m = show files matching hashes
    -x = show files that do not match hahes (probably most important)

    This will compare files in the specified folder “E:BACKUP\*” to the files in the list “md5log.txt” and `-m` flag will spit out files that match the hashes, `-x` flag will spit out files that do not match hashes (including new files that did not have hashes generated for it). I would highly recommend putting filenames and paths in quotes otherwise it can misinterpret a space from a path or file name.

    There’s more options but those are the basics. Hashdeep can do more including an audit mode allowing for more detailed evaluation of files, but for general stuff, md5deep is simple and effective.

    There are lots of other apps out there, but these two I found were the most robust and didn’t choke on special characters or have other limits that I ran into over time.

  3. If you care that much about data integrity TrueNAS is going to handle all that for you automatically and have less risk of you making mistakes doing it yourself.