2 Format code
source | link

On my system, this was caused by the "hardening" for VirtualBox. There was a DLL injected by Sophos into the winsock stack and virtualbox would not support it.

netsh winsock resetnetsh winsock reset - was a temporary fix.

But to permanently fix I had to update my machine's root certificate list so that the DLL (a genuine one) was now recognised by virtualbox as valid.

On my system, this was caused by the "hardening" for VirtualBox. There was a DLL injected by Sophos into the winsock stack and virtualbox would not support it.

netsh winsock reset - was a temporary fix.

But to permanently fix I had to update my machine's root certificate list so that the DLL (a genuine one) was now recognised by virtualbox as valid.

On my system, this was caused by the "hardening" for VirtualBox. There was a DLL injected by Sophos into the winsock stack and virtualbox would not support it.

netsh winsock reset - was a temporary fix.

But to permanently fix I had to update my machine's root certificate list so that the DLL (a genuine one) was now recognised by virtualbox as valid.

1
source | link

On my system, this was caused by the "hardening" for VirtualBox. There was a DLL injected by Sophos into the winsock stack and virtualbox would not support it.

netsh winsock reset - was a temporary fix.

But to permanently fix I had to update my machine's root certificate list so that the DLL (a genuine one) was now recognised by virtualbox as valid.