SECUREREPAIR: Failed to CreateContentHash of the file

[thill]

We see this message on every file during installation: "SECUREREPAIR: Failed to CreateContentHash of the file ...".

Can't find much information on the web. Installations continue past that section.

Just wondering what that's about and if we should be doing something we're not.

[Daniel]

Hello,

I'm not sure, but this line could be written in the log when Windows Installer fails to compute the hash value of an installation file. Did you encounter any error during installation or the installation succeed? If so, please check the KB2918614 article and see if matches with your installation errors.

All the best,
Daniel

[thill]

That KB does not appear to apply. We're running the installer logged-in and as Administrator.

Yes, the install continues to success. But we get asked about those messages.

Is there an option to disable checking the hash of the files? Or a way to create the hash and satisfy it?

Thanks a lot. Have a great weekend.

[Daniel]

Hello,

Is there an option to disable checking the hash of the files? Or a way to create the hash and satisfy it?

To disable the hash file check you should make sure the [Hash Files] button, from "Files and Folders" page (you can see it in the "Files and Folders" ribbon section), is not enabled.

Also, can you tell us if your setup package is digitally signed? This log entry may appear when the digital signature of the setup is not recognized by Windows Installer. So, please check if on the UAC prompt, spawned during installation by Windows Installer to request elevation, the digital signature/publisher of your setup is successfully recognized.

All the best,
Daniel

[thill]

The Hash Files option is not enabled. And we do not digitally sign anything.

Ours is a server-based product. Because we install a Windows service we have the "Run as Administrator" flag enabled and instruct people to also right-click the installer EXE and Run as Administrator.

Not sure when this started to appear in the installer log but we do get questions about it.

[thill]

Here is a piece of log on this:

Code: Select all

MSI (s) (14:00) [16:44:27:889]: SECREPAIR: Hash Database: C:\Windows\Installer\SourceHash{9854DBF4-A807-413A-90BF-418D0DEE006B}
MSI (s) (14:00) [16:44:27:889]: Note: 1: 2262 2: SourceHash 3: -2147287038 
MSI (s) (14:00) [16:44:27:904]: SECREPAIR: New Hash Database creation complete.
MSI (s) (14:00) [16:44:27:904]: SECREPAIR: CryptAcquireContext succeeded
MSI (s) (14:00) [16:44:27:920]: SECREPAIR: CryptAcquireContext succeeded
MSI (s) (14:00) [16:44:27:920]: SECREPAIR: Failed to open the file:C:\ProgramData\Full Circle Systems\DocVue Enterprise\10.1.1.7533\DEE006B\sql\auditmodule\01.AA_PreConfigReports_table.sql for computing its hash. Error:3

They do not affect the installation which completes successfully.

Was hoping it would be as simple as disabling that option in Files & Folders but it wasn't enabled.

[Daniel]

Hello,

To further investigate this, can you please send us the .aip (project file) and a full verbose log of the installation to support at advancedinstaller dot com so we can take a closer look over them?

All the best,
Daniel

[Daniel]

Hello Todd,

After running several tests on our side it seems the related log lines ("SECUREREPAIR: Failed to CreateContentHash of the file") are written in the log files when installing the setup on Windows machines which have the KB2918614 update installed. On all machines without this update installed the related lines are not written in the log. So, it seems the KB2918614 is the culprit. I've done a small research trying to find out why Windows Installer tries to compute the hash for the installation files when the KB2918614 is installed, but I didn't find any useful info. Maybe this is just another undocumented glitch caused by the KB2918614 update, but considering that your product installation succeeds you can safely ignore those lines.

If there is anything we can assist you with just let us know.

All the best,
Daniel

[donalwa]

Just wondering was a conclusive solution found for this issue? I am seeing a similar issue where KB2918614 is not installed on windows server 2012 R2?

[Daniel]

Hello,

Unfortunately we didn't find any conclusive resolution for this behavior. Did you get any installation issues? If so, can you please send us the .aip (project file) to support at advancedinstaller dot com so we can investigate its settings?

All the best,
Daniel

[MLiss@Cetrus.com]

I am experiencing a similar error -
see viewtopic.php?f=5&t=35054

[Daniel]

Hello Mike,

You can see my colleague reply on the referenced thread.

All the best,
Daniel