mfehidk Warnings with VSE8.8 installed

[Former Member]

i have the same problem, my system is windows 2008 r2,and WscAv.dll is also grayed out like you and the image on posting No.52,so i think that is the point. but i dont know how to fix that.

[bretzeli]

Hi Rib,

* VSE 8.8, Windows XP SP3 German

* Framework 4.6 latest Version

* Enteo Frontrange V7.0 Agent migrated since 5.X

Same problem with one customers. But i also have the event on Server 2003R2 and we have have absolute no Frontrange on Servers.

This is the Time period when the Event 516 happens.

Gruss aus der Schweiz

Nachricht geändert durch bretzeli on 12.10.11 07:47:32 CDT

[Former Member]

Hi bretzeli,

try the tool InjectedDll from www.nirsoft.net to see all hooks together, no need to trace for it.

Greets

rib

[bretzeli]

Windows XP Service Pack 3 and Server 2003R2

Hello,

This is due to a MS bug in Crypt32.dll / Memory Leak.

Request and Install MS Hotfix: 959658 which should solve the problem:

http://www.butsch.ch/post/Windows-XP-Sp3-Event-516-mfehdik-SLL-API-memory-Leak-crypt32dll.aspx
http://support.microsoft.com/kb/959658

Nachricht geändert durch bretzeli on 12.10.11 06:34:16 CDT

[Former Member]

Downloaded and tried this.  Upon reboot Event 516 alerts continued to populate the logs.....

[wwarren]

Hi Everyone,

I know a great many of you are looking forward to making the Event 516 "noise" go away.

Unfortunately the Patch 1 release for VSE 8.8 will not give you that. However, we plan to release a hotfix for a specific issue that was identified which is responsible for the "noise".

The VSTSKMGR.exe process is executing code routines that will inevitably result in the Event 516 occurring frequently.

The hotfix will solve this and is expected to be available by the end of October (it will be freely available once it's released).

When the noisy aspect of these events is resolved, what will remain are legitimate Event 516 occurrences. Meaning, the VSE product is warning you that there is 3rd party code inside our process(es) interacting with our kernel level drivers. For these legitimate events, if you know it's not due to malware, and if you wish for those events to cease, then there is a mechanism to allow that.

A comprehensive knowledgebase article is being written to cater to the various scenarios and to better educate our customers on this particular event, including how to fix the noise and how to make them stop altogether. The first step though will be to get the hotfix out that solves the "noise".

The article will be KB71083, but as yet the new and revised content has not been published so it still has old content for now. I'll let you know when it's live.

[Former Member]

And what is about the expired certificate of VSTSKMGR.exe ?

[wwarren]

rpeters wrote:
And what is about the expired certificate of VSTSKMGR.exe ?

You should update your DAT files.

[Former Member]

wwarren schrieb:

You should update your DAT files.

Same here, DAT file is 6519.0000, IMHO its up to date.

Any suggestions?

[akl71]

Same here, certificate is outdated.(occours with VSE 8.7 and VSE 8.8)