I have trouble installing any .NET Framework on my Windows 7 x64 machine, I keep getting the following logfile, what might cause this?
OS Version = 6.1.7601,
The solution provided by Thaoden (uninstalling KB2918614, KB3000988 and KB3008627) didn't work for me. I got the same errors after uninstalling these updates.
What did work for me was the whitelisting workaround suggested by JohnL999 here.
So, what I had to do to make it install:
Create a DWORD named SecureRepairPolicy
with value 2
in HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer
Create Key SecureRepairWhitelist
in HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer
In SecureRepairWhitelist
, create a String with the product ID you want to whitelist as name. In my case this was {3911CF56-9EF2-39BA-846A-C27BD3CD0685}
. You can find out the product ID in the msi log file, some lines before the error
SECUREREPAIR: Failed to CreateContentHash of the file: 1030\SetupResources.dll: for computing its hash. Error: 997.
It looks like this:
SECREPAIR: Hash Database: C:\windows\Installer\SourceHash{3911CF56-9EF2-39BA-846A-C27BD3CD0685}
or this:
SOURCEDIR product ==> {3911CF56-9EF2-39BA-846A-C27BD3CD0685}
Might be a different product ID depending on the MSI you want to install.
I still kept getting this error even after uninstalling KB2918614, etc., and what finally fixed it for me was to rename C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18
to C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18.bak
for example. Only then when retrying the failing installation will it succeed! :)
The failing installation will recreate that folder.
I found this solution in the comments section of this blog post:
Gerd Hübner 4 Sep 2015 6:15 AM #
In short: Rename the folder C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18
After some long days of fruitlessly searching, I stumbled across https://forums.lenovo.com/t5/ThinkVantage-Technologies/Install-of-Sytem-update-fails-with-MSI-installer-Error-997/td-p/1802731. It says there to uninstall KB2918614, KB3000988 and KB3008627. That did the trick for me.
Apparently, the culprit is KB3008627 as I didn't uninstall that one in my previous attempts.