This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

scan error on non existent folder C:\Documents and Settings\User\Local Settings\Application Data\Google\Chrome\User Data

The below was returned from our scheduled scan (config via the Enterprise Console):

User: NT AUTHORITY\SYSTEM
Scan: New scheduled scan
Machine: <hostname>

Scanning "C:\Documents and Settings\User\Local Settings\Application Data\Google\Chrome\User Data\Default\Extension Rules\LOCK" returned SAV Interface error 0xa0040202: Scan failed.

Scanning "C:\Documents and Settings\User\Local Settings\Application Data\Google\Chrome\User Data\Default\Extension State\LOCK" returned SAV Interface error 0xa0040202: Scan failed.

Scanning "C:\Documents and Settings\User\Local Settings\Application Data\Google\Chrome\User Data\Default\Session Storage\LOCK" returned SAV Interface error 0xa0040202: Scan failed.

The above folder clearly does not exist! "C:\Documents and Settings\User\" so why is Sophos trying to scan it?? How do I tell it to not bother scanning it!!!

I have requested assistant from Sophos technical support via email. However they are less than useful (to be polite) and is giving me the run around and doesn't even appear to be even reading the info I sent to them.

I'm hoping someone on here can help me with this.

Thank You.



This thread was automatically locked due to age.
  • We are also now experiencing the problem. I do not see a resolution for this issue? Is there a fix that has been identified? Does this represent an actual threat or is it safe to ignore? When we run a scan on machines, with Chrome installed, the log indicates failures for paths such as c:\users\"usersersname"\AppData\Local\Google\Chrome\User Data\Default\"multiplefileslisted"\LOCK" returned SAV Interface error 0xa0040202: Scan failed. Please post an update. Thanks
  • I still have not heard back from Sophos with a fix for this issue! I haven't had time to chase this up.
  • I just got a call from Sophos to say that they've now isolate the problem and has implemented a fix. It will will be in the next version which will get released in a few months as it goes through QA etc