The Sophos Community will be offline for scheduled maintenance this Saturday, May 27th, at 13:00 UTC for approximately 1 hour. Apologies for any inconvenience caused.
"Wanna" ransomware outbreak. Please see this Sophos article sophos.com/kb/126733 for advice on how to protect your organization. Immediate action recommended.
After installing Sophos software which includes the Sophos Management Communication System (MCS) component, e.g. a UTM or Sophos Central managed client, you experience a delay in system start-up between 3-5 minutes. In the Windows event log, the following message can be found:
MCS Client service hung or starting
First seen in Sophos CloudUTM Managed Endpoint (Windows 2000+)
During start-up of the 'Sophos MCS Client' service (McsClient.exe) with auto-proxy detection enabled (default), it determines the relevant proxy for each server. The first time WinHttpGetProxyForUrl() is called, it can take a considerable amount of time to return; this makes it appear to the Windows Service Control Manager that the MCS client service had hung.
This issue is fixed in Management Communication System (MCS) version 1.5.3 and later, which was released to customers on Friday 24th January 2014.
Note: Prior to the fix being made available, the following workaround was recommended. Set the 'Sophos MCS Client' service to have a start-up type of 'Automatic (Delayed Start)'. To set this follow the steps below:
Every comment submitted here is read (by a human) but we do not reply to specific technical questions. If you need technical support please post a question to our community. Alternatively for licensed products open a support ticket.