Jump to content

Archived

This topic is now archived and is closed to further replies.

Zardoc

PGP Disk and NOD32

Recommended Posts

Hi all,

 

Just updated Symantec Encryption Desktop 10.4.2.MP3 (PGP Disk) on three machines. After each install I get Issues with NOD32 Antivirus. If I uninstall and reinstall NOD 32, issues go away. I'm not sure if the problem is related to PGP PGPWLD pwflt.dll.

One machine out of three updated without the problem of module updates not working.

I cleared the update cache to no avail.

Marcos, got any ideas why this is happening with this update of PGP and did not with other updates ? SEE Images

Thanks.

Eset 001 2019-08-11_19-00-42.png

Eset 002 2019-08-11_19-00-42.png

Eset 003 2019-08-11_19-00-42.png

Share this post


Link to post
Share on other sites

Please provide logs collected with ESET Log Collector. Just for a test, try disabling protected service and rebooting the machine and see if it makes a difference.

Share this post


Link to post
Share on other sites
18 hours ago, Marcos said:

try disabling protected service and rebooting the machine and see if it makes a difference.

Nope.

Share this post


Link to post
Share on other sites

Live grid also locked out. Here is another report.

I have to go back to regular service. This is my main machine.

eav_logs_Part2.zip

Share this post


Link to post
Share on other sites

Marcos,

Any idea about the problem ?

Thanks.

Share this post


Link to post
Share on other sites

I see that PGPlsp.dll is registered as LSP in Winsock. Also you have Windows 10 installed where ekrn runs as a protected service by default.

We have recently found out that under unknown circumstances (probably after some Windows update), ESET gets removed from Winsock. Subsequently the system attempts to load a 3rd party dll into ekrn which obviously fails, causing Winsock initialization to fail as well.

What you can do is reinstall ESET so that it gets re-registered in Winsock.

Share this post


Link to post
Share on other sites
On 8/16/2019 at 12:32 AM, Marcos said:

I see that PGPlsp.dll is registered as LSP in Winsock. Also you have Windows 10 installed where ekrn runs as a protected service by default.

We have recently found out that under unknown circumstances (probably after some Windows update), ESET gets removed from Winsock. Subsequently the system attempts to load a 3rd party dll into ekrn which obviously fails, causing Winsock initialization to fail as well.

What you can do is reinstall ESET so that it gets re-registered in Winsock.

Good call.

That's what I did initially.

Thanks.

Share this post


Link to post
Share on other sites

After installing ESET, please make sure that ekrn is registered under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog (should be in one of the subkeys). If I remember correctly, it was missing on your machine which is why erkn was unable to establish network communication.

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...