Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I want to make sure that I can stop a machine, on Hyper-v with windows VMs, and then I can start it, being sure that nothing changed inside the VHD.

Is this possible? Can I make like an MD5 of "C:\Windows\System32\config" SAM, System, etc, and then start the VM's (after one month or more) making sure that nothing changed?

Is there other way, a more "pretty" way?

Perhaps an export off all drives like: "DIR c:\*.* /s/one >c:\before.txt" and then a "DIR c:\*.* /s/one >c:\after.txt" then a file compare?

share|improve this question

Microsoft provides an MD5 utility, though it is unofficial. It's called "fciv" (File Checksum Integrety Verifier). It can output directly to console or to an XML file depending on what you're doing with it, and even has the ability to recursively dive into a directory if you want to check and entire hierarchy of VHDs.

Details here:

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.