Ever since the policy to disable TLS 1.0 was pushed down to the local machines, we started getting the error “an authentication error has occurred(code 0x80004005)” when accessing few of our Windows 2008 R2 servers. It was interesting because we have a bunch of other servers with no problems accessing. This seems to be a very generic error code as google results were showing multiple problems and multiple solutions for this.
We removed all traces from the registry, Sophos failed to install. We contacted Sophos support, allowed a tech to remote in and run their removal script for the failed Sophos installation, attempted to re-install, this attempt also failed. We attempted that method maybe a dozen times across a few machines. Hi Rey, Unfortunately those instructions don't match what's available on the Fire. The nearest equivalent I can find is: Tap the settings icon; Tap Apps & Games. Free sophos home antivirus download includes a 30 day trial of Sophos Home Premium, with ransomware security, advanced phishing protection and more.
Sophos 0x80004005 Software
Apparently, in my case, the patch to add RDS support for TLS 1.1 and TLS 1.2 was not installed in 3 of the servers with this problem. So I had to download the patch from this Microsoft website and install and reboot them remotely. Once installed and rebooted, voila!!
Edit: There are multiple reasons for this problem, and there are multiple ways to fix it. I am just sharing what worked for me, and it may not work for all. Saying this because this post is now in the first page of google results and I am getting lot of traffic to this, and I do not want to disappoint you. Thanks
Files left behind after the uninstallation of PureMessage:
The quarantine directory INSTALLDIRQuarantine is left behind on the server. This enables you to retain quarantined items during uninstallation and reinstallation of PureMessage. If you no longer need the quarantined items, delete this directory.
On an SCC cluster, the Quarantine folder can be found on the shared drive under SHAREDDRIVESophosPureMessageQuarantine.
The logs directory INSTALLDIRLogs is left behind on the server. If you no longer need the log files, delete this directory.
On an SCC cluster, the Logs folder can be found on the shared drive under SHAREDDRIVESophosPureMessageLogs.
The file PMClustResTypeXXXX.dll is left behind in the C:WINDOWSsystem32 folder. This is the PureMessage cluster resource DLL that can be deleted from all nodes in a cluster after PureMessage is uninstalled from all the nodes.
On an SCC cluster, the following folders are left behind on the shared drive:
Sophos 0x80004005 Vs
These folders can be deleted after uninstalling PureMessage from all nodes.