Solved Cannot repair member file [l:12{6}]"mf.dll" of Microsoft-Windows-MediaFoundation

[tom982]

Yeah, I'm still not entirely sure how hard-links work because the hashes of explorer.exe in C:\Windows is different to it's WinSxS (supposedly hardlinked) equivalent.

That's a very good point actually, thanks. I'm going to give that a go at the weekend I'll post back here to let you know how I get on. As for the hash (or as it's also known, digest) algorithm, this is in the manifest:

      <dsig:DigestMethod xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" Algorithm="http://www.w3.org/2000/09/xmldsig#[COLOR=#ff0000][B]sha256[/B][/COLOR]" />

So we know it's based on a SHA256 hash. The next part I can't take credit for (thanks to niemiro for this information!), but as the final product ends with an = sign, which is a padding character for Base64, we can conclude that the manifest hash is a Base64 encoded SHA256 hash. But, I've never managed to match the hash in the manifest by taking a SHA256 hash then encoding that in Base64, but I must be doing something wrong.

Tom