Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 1 subscriber
  • Views 471 views
  • Users 0 members are here
Options
Suggested
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

Code a0200006

tej_gee

Code a0200006 - The folder "C:\Progr~1\Sophos\AutoUpdate\Cache\savxp\ClassFilterDrivers\AMD64\" doesn't exist.

I get the above mentioned error on one of my desktops in EM after the 9.5 version of SAV was installed.  I've tried to install it via EM, and have also uninstalled the SAV manually on the client, and reinstalled via EM.  Both times the machine listed as requiring a reboot, and each time the same error message appears after reboot.

All desktops are clones with WinXP SOE installed, however this one computer does not seem to like the 9.5 install, or an element of the installation.

Is there something that I can do to resolve this error?

:8937


This thread was automatically locked due to age.
Parents
  • 0

    HI,

    Is the path actually:

    "C:\Progra~3\Sophos\AutoUpdate\Cache\savxp\ClassFilterDrivers\AMD64\"

    That would exist on a Vista+ machine if "Progra~3" represented ProgramData for example.  

    Your path is missing the "a".  Maybe that's just a typo when copying the error?

    I think these errors are timing related.  For on-access the filter driver requests the SAV service to scan a file but between those 2 events, the file could dissapear which would cause this error.  It could also happen with Suspicious behaviour, I think in that case, an event is fired that looks suspicious, the SAV service is then requested to scan the file that created the event. Again there is a window between those 2 events where the file could be removed.  It's more likely with temp files I would think.

    One way to differentiate between the 2 possibles would be to add a "directory" exclusion under on-access settings for the path you see in the error (remember the training backslash).  This way the driver will not make any requests to scan files in this directory.  If the error goes away, at least we know it's on-access that's generating it.

    Hope that offers something.

    Thanks,

    Jak

    :8943
Reply
  • 0

    HI,

    Is the path actually:

    "C:\Progra~3\Sophos\AutoUpdate\Cache\savxp\ClassFilterDrivers\AMD64\"

    That would exist on a Vista+ machine if "Progra~3" represented ProgramData for example.  

    Your path is missing the "a".  Maybe that's just a typo when copying the error?

    I think these errors are timing related.  For on-access the filter driver requests the SAV service to scan a file but between those 2 events, the file could dissapear which would cause this error.  It could also happen with Suspicious behaviour, I think in that case, an event is fired that looks suspicious, the SAV service is then requested to scan the file that created the event. Again there is a window between those 2 events where the file could be removed.  It's more likely with temp files I would think.

    One way to differentiate between the 2 possibles would be to add a "directory" exclusion under on-access settings for the path you see in the error (remember the training backslash).  This way the driver will not make any requests to scan files in this directory.  If the error goes away, at least we know it's on-access that's generating it.

    Hope that offers something.

    Thanks,

    Jak

    :8943
Children
No Data
Unfiltered HTML