Hello,
Thank you for keeping us updated.
It seems that the issue is resolved.
I appreciate your efforts and time.
Please do let us know if you need any assistance in regards to Windows.
Thank you
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
My System is Windows 7 SP1 Home Premium. Recently the Event Viewer has shown the following Audit failure after every fresh startup after the system has been powered off:
Record Number : 145537
Log Type : Security
Event Type : Audit Failure
Time : 28/06/2016 18:57:39
Source : Microsoft-Windows-Security-Auditing
Category : 12290
Event ID : 6281
User Name :
Computer : Chris-PC
Event Data Length : 0
Record Length : 352
Event Description : Code Integrity determined that the page hashes of an image file are not valid. The file could be improperly signed without page hashes or corrupt due to unauthorized modification. The invalid hashes could indicate a potential disk device error. File Name: \Device\HarddiskVolume3\ProgramData\Trusteer\Rapport\store\exts\RapportMS\baseline\RapportIaso.sys
I have been in touch with IBM Trusteer Support but they have been unable to help - their initial suggestion was as follows:
In order to resolve this issue, please follow the steps below:
1. Run → Enter secpol.msc in the search box.
*Please note, that an error message may appear. Disregard it and wait for a few seconds until the "Local Security Policy" window appears.
2.Open “Local Policies”.
3.Open “Audit Policy”.
4.Enter “Auditor privilege use”
5.Verify both check-boxes are unchecked.
6. Restart your computer.
However Windows 7 Home Premium does not have the the group policies editor 'secpol.msc' so I am unable to carry out their suggestion. Because of this they advised I contact Microsoft.
I have ruled out 'disk error' by running HD Tune which found no errors on the hard drive. IBM appear to have ruled out a problem with my malware protection (Avast 2016 anti-virus and Comodo Firewall) after I had sent the details to them.
The problem has occurred over the last few days (starting Monday 27 June 2016).
Any advice and suggestions would be much appreciated, thank you.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hello,
Thank you for keeping us updated.
It seems that the issue is resolved.
I appreciate your efforts and time.
Please do let us know if you need any assistance in regards to Windows.
Thank you
Hi Ratandeep,
The Sigverif log looked as if it would be too big so I have put in my Dropbox account with the following link: https://www.dropbox.com/s/9h84t8a1jcazlie/SIGVERIF%20report.TXT?dl=0
I don't know if you will find anything significant, perhaps you'll let me know.
Thanks and best regards.
Hi Ratandeep,
Thanks for your reply and the links contained.
I'll be busy for a few days so won't be able to carry out all your suggestions for a while. I did, however, run Sigverif exe and it gave this message: "Your files have been scanned and verified as digitally signed." The logfile makes the message too long so I will post it separately .
Regards.
Hello,
Thank you for the reply.
I am sorry for late response.
I appreciate your patience.
I would suggest you to perform advanced clean boot and check.
Refer:
https://support.microsoft.com/en-us/kb/316434
(Also holds good for Windows 7)
Important Notes:
Serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
https://support.microsoft.com/en-us/kb/322756
Modifying BIOS/ complementary metal oxide semiconductor (CMOS) settings incorrectly can cause serious problems that may prevent your computer from booting properly. Microsoft cannot guarantee that any problems resulting from the configuring of BIOS/CMOS settings can be solved. Modifications of the settings are at your own risk.
Thank you
Hi,
Sorry to report it but after having a couple hours break and then restarting the computer, the problem is back. It would seem that the clean boot cleared the problem for the next normal boot but shutting down and rebooting afterwards has brought it back. Work to do then in trying to find which services are conflicting if that is the cause.
Cheers.