Jump to content
pps

Windows version 1903 - Registration to Windows Security Center was not successful

Recommended Posts

Hello,

 

This morning all clients that upgraded to Windows 1903 get this warning:

Quote

 

**/**/2019 **:**:** ** - During execution of

%SCANNER% - Module concerned

Kernel on the computer **********, from User: (SYSTEM) the following event occurred:

Registration to Windows Security Center was not successful - Description of a non virus event

Action taken - %ACTION%

 

 

In ESMC console there is no such indications.

 

a. Which is correct the warning or the ESMC console?

b.Is this warning some issue between windows version 1903 and endpoint 7.1.2053.0 and 7.2.2055.0?

Thanks,

Peter

image.png.45e70bdfb56a2d12f14def08af992ed9.png

 

 

Share this post


Link to post
Share on other sites

I assume the message should have been logged in the ESET Event log. Wasn't it?

Share this post


Link to post
Share on other sites

that's correct

5 minutes ago, Marcos said:

I assume the message should have been logged in the ESET Event log. Wasn't it?

 

image.png

Share this post


Link to post
Share on other sites

You can try to uninstall Endpoint and reinstall it so that it re-registers to WSC. Failing this, enable advanced kernel logging under tools -> diagnostics, reboot the machine, disable logging and collect logs with ESET Log Collector. I'd suggest opening a support ticket and providing customer care with ELC logs. However, in cases we've come across the issue was usually with the operating system when a Windows API function returned "DISK_OPERATION_FAILED".

Share this post


Link to post
Share on other sites

As a test, reboot one of the clients and see if the Win Security Center Eset event log registration error entry is generated again.

I have received this log entry sporadically and in most instances, it disappeared after a reboot.

Edited by itman

Share this post


Link to post
Share on other sites

Hello,

I have not receive this error again on this pc after restart.

Is it safe to assume that this error has resolved before the restart or after the restart?

however it could be very handful If the resolution of this error is mentioned in the event log file.

Thanks,

Peter

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...