What!!! Sometimes it pays to read the last few posts before you post something! The OP was given several suggestions including the one you say, but posted back saying that all failed. Therefore it is common sense to first of all establish that his .esd file is not corrupted.
Just think of how much that tool would be passed around if we initially made it with a GUI instead of a cmd screen. I still can't get over the irony of a MS forum mod recommending MDL decrypt tools. *facepalm*
Huh! You mean your ESD fails to match it's published hash? As mentioned and as others have told you - start at the beginning and first of all verify you have a sound .esd by hash checking.