Topic: Audit Failure, System Integrity, Code Integrity Checker detected ... klhkum.dll has been closed prematurely & marked as solved, it's not [On Following]

[Flood and Flood's wife]

For some reason Topic Audit Failure, System Integrity, Code Integrity Checker detected ... klhkum.dll has been closed and marked as Answered/Solved - why? 

1. The “answer” was not selected by me. 
2. The “answer” has not resolved the issue. 
3. Why close a Topic prematurely? 

Thank you​​​​🙏

Flood🐳

[Berny]

I followed up the same issue in the French Forum Section.
Member @Bibblos shared with us following exchange with Kaspersky Lab France :
----------
“Cher client(e)
Merci d'avoir contacté l'assistance technique de Kaspersky .
Je m'appelle xxxx et Je m'occupe personnellement de votre requête .
Après analyse, il apparaît qu'il s'agit d'un bug (4110058) connu des développeurs Kaspersky qui travaillent en ce moment pour le résoudre.
La solution est attendue à Partir du 14 Avril 2020 avec le patch "J" de l'application Kaspersky .
Je vous contacterais dès que la solution sera mise au point.”

----------
English translation :

“Dear Customer
Thank you for contacting Kaspersky  technical support.
My name is xxxx and I personally take care of your request.
After analysis, it appears that this is a known bug (4110058)  and Kaspersky developers  are currently working to solve it. The solution is expected around April 14, 2020 with the patch "J" of the Kaspersky application . I'll contact you as soon as the solution is finalized.”
----------

Also , actually the Moderator Team is reviewing and evaluating several  Forum Topics backwards .
 

[Flood and Flood's wife]

@Berny 

• Patch J did not fix the issue & it doesn’t explain why my topic was closed & given a status of answered/solved by @Bibblos, his answer is not a Best answer, the issue is not fixed and not solved. 
• & I have no idea what “reviewing and evaluating several  Forum Topics backwards “ means🤔

Thank you​​​​🙏

Flood🐳

[Berny]

To all :
If you are still encountering the klhkum.dll issue under Kaspersky 2020 Patch J
please contact K-Lab Technical Support : https://center.kaspersky.com

@FLOOD 
I will  in no way unlock a Topic that has been closed  by a colleague Moderator,
Anyway , this Bug can  only be fixed by Kaspersky Lab
and K-Lab Collaborators can always interfere in a closed Topic.

Clarification : The Moderator Team  is actually checking and  evaluating  some previous Topics.