Sophos updating policy differs from policy
To resolve this issue, re-protect the computers: in Enterprise Console, select the computers you want to re-protect, right-click, and then click After an upgrade from Windows 8.1 (either 64-bit or 32-bit) to Windows 10, if a computer is started in safe mode, the Sophos Anti-Virus service (SAVService.exe) fails to start.
This is due to a missing Sophos registry key, that has not been migrated during the OS upgrade. After an upgrade from Windows 8.1 (either 64-bit or 32-bit) to Windows 10, the Sophos Healthcheck tool fails with warnings about missing registry keys.
Therefore, if a third-party LSP that is known to be incompatible is already installed on the computer, the Sophos LSP is not installed. Sophos Endpoint Security and Control is supported on Windows XP/2003/Vista/2008/7/8/2012/Windows 10.
Once the client shows up as ‘Differs from policy’ there are two ways to get the client re-aligned with your preferred settings: In one particular scenario, I was working with non-traditional clients of non-persistent VDI clients.
The following errors appear in the firewall system log: Protecting Windows 8 or Windows Server 2012 computers that are in a workgroup from Sophos Enterprise Console 5.1 on Windows Server 2008 or Windows Server 2008 R2 fails with the errors "Failed to launch setup.exe" and "2147942405".