Sophos Anti-Virus on-access scanning: Conflict with Lenovo Access Connections

  • Article ID: 116968
  • Updated: 29 Mar 2012

This article explains how to resolve a conflict that exists between Lenovo Access Connections Verbose Logging and Sophos Anti-Virus on-access, on-write scanning being enabled. This conflict causes boot times to be significantly delayed - up to 20 minutes on top of expected behavior.

This issue is more apparent with the release of Sophos Anti-Virus version 10 with a fresh install and the default scanning policies applied due to default AV policies now including on-access, on-write for new installs.

This issue will also be seen with older versions of Sophos Anti-Virus versions when on-access, on-write scanning is enabled alongside Lenovo Access Connections Verbose Logging.

What is Lenovo Access Connections?

Access Connections provides detailed connection information and a set of diagnostic tools to help you troubleshoot faulty network connections. 

Lenovo Access Connections Verbose Logging writes network information to a local file for detailed troubleshooting. As this information is being written during boot up, it has a direct impact on boot times with Sophos Anti-Virus on-access, on-write scanning enabled.

Known to apply to the following Sophos product(s) and version(s)
Sophos Anti-Virus for Windows 2000+ 10.0

What To Do

Lenovo Access Connections verbose logging needs to be disabled.

To view the detailed connection status and configure the diagnostic tools, do as follows.

  1. Open Lenovo Access Connections.
  2. Go to Advanced view.
  3. Click the Tools tab.
  4. Select Diagnostics. The Diagnostic Tools window opens. This window has the following five tabs: Connection Status, Ping, Trace Route, IP Configuration, Event Log.
  5. Select the Event Log tab to view the setting for the verbose logging. To disable the event logging, click disable logging.
  6. The event log is used to help diagnose problems with network connectivity, and a log can be created of all network activity managed by Access Connections. This feature should only be used if instructed to do so by the customers network administrator.Once the event log has been disabled, the customer should reboot the system to see if this has resolved the boot timing issues.

If the problem persists, and you suspect that this application is still the cause of the issue, you can use the following steps to troubleshoot this further:

  1. Remove Sophos v10 and Access Connections from the machine.
  2. Install Sophos v10 as new with the default configuration. Can the issue be reproduced without Access Connections?
  3. Install Access Connections (it would be worth installing the latest release if possible).

These troubleshooting steps should highlight to the Sophos support professional and the customer if this application is the cause of the reported issue.

Further information

The following link contains a similar solution as described above:



If you need more information or guidance, then please contact technical support.

Rate this article

Very poor Excellent