Jump to content

Report of Issue in Eset Endpoint Security - Graphical Interface GUI


Recommended Posts

Step 1: Computer Analysis

1. Open Eset Endpoint Security and navigate to "Computer Analysis." Select "Scan your computer" on the left side.

   Note: Up to this point, all elements, including the duration clock and analyzed objects, function correctly.

Step 2: Issue Detected in Custom Analysis

2. The problem arises when opting for "Custom Analysis" with the following options:

   - Smart Analysis
   - Thorough Analysis

   Choose the following parameters:

   1. Operating memory
   2. Start sectors / UEFI
   3. WMI database
   4. System registry

3. Perform the analysis by selecting all disks.

 

Identified Issue: During this process, it is observed that the duration clock and analyzed objects become paralyzed, adversely affecting the smoothness of the analysis.

Steps to Reproduce the Issue:

1. Open Eset Endpoint Security.
2. Navigate to "Computer Analysis" and select "Scan your computer."
3. Choose "Custom Analysis" and select the mentioned options.
4. Initiate the analysis with the option to scan all disks.

By following these steps, you can reproduce the problem and observe the interruption of the duration clock and analyzed objects. This report is posted on the forum in the hope of receiving assistance in identifying and resolving this issue. Any collaboration in addressing and solving this problem is appreciated.

Link to comment
Share on other sites

  • Administrators

Please check if you can reproduce it with the registry and WMI not being scanned, otherwise it's expected that the counters are refreshed not every second.

Link to comment
Share on other sites

Issue Persisting in Eset Endpoint Security GUI: Request for Development Team Intervention
 

Message:

Hello Marcos,

I trust this message finds you well. I want to discuss the ongoing challenge related to the lack of updating counters during registry and WMI scanning in Eset Endpoint Security.

Reasons for Development Team Involvement:

1. Persistent Nature of the Issue: Despite following recommended steps, the problem persists, suggesting a potential fundamental issue within the software.
2. User Experience Impact: The absence of real-time updates to counters and the duration clock affects the user experience and compromises the software's effectiveness in providing accurate progress information during scans.

3. Possible Systemic Software Glitch: The persistence of the issue, even after excluding registry and WMI scanning, hints at a systemic glitch that may require a detailed analysis by the development team.

4. Call for Comprehensive Resolution: To ensure a thorough resolution and address any underlying software intricacies causing this behavior, involving the development team's expertise is crucial.

 

Proposed Steps:

1. Development Team Analysis: Seeking the development team's involvement for a detailed analysis could unveil coding irregularities or underlying issues contributing to the lack of real-time updates.

2. Software Optimization Potential: Insights from the development team may lead to optimization measures, ensuring a smoother and more accurate display of progress indicators during scans.

3. Enhancing Overall Product Reliability: Addressing and resolving this issue at the development level would significantly contribute to the reliability and effectiveness of Eset Endpoint Security.

I believe escalating this matter to the development team is essential for a comprehensive understanding of the issue and effective solutions. Your support in facilitating this escalation would be greatly appreciated.

Thank you for your time and consideration.

Best regards

 

 


 

Link to comment
Share on other sites

  • Administrators

We have already answered above. Please let us know if you experience the issue when WMI and the registry are not selected for scan.

Link to comment
Share on other sites

Hello Marcos,

Thank you for your prompt response. I have conducted additional tests by excluding both WMI and the registry from the scan, and the issue persists. The lack of real-time updates to counters and the duration clock continues to be present.

I appreciate your ongoing assistance with this matter. If there are any further steps or insights you recommend, please let me know.

Best regards

Link to comment
Share on other sites

Hey Marcos 

From second 00:00 to minute 04:30, I've recorded both scans where the issue occurs. However, from minute 04:35 to minute 07:08, the analysis runs smoothly without any problems. This division provides a clear distinction between the problematic and normal phases of the analysis

Link to comment
Share on other sites

Dear Marcos,

Thank you for your prompt response. While the duration of the scan appears to be increasing correctly, there persists an inconvenient issue. During certain moments of the custom scan, I experience a freeze in the duration clock and analyzed objects.

This problem can be quite discomforting and impacts the user experience. I am willing to provide more information or details if necessary for a better understanding of the issue. Any additional guidance you can offer would be greatly appreciated.

Thanks again for your assistance.

Link to comment
Share on other sites

Dear Eset Staff, I hope someone can help me with this problem and for once understand this problem, waiting for a response, thank you

Link to comment
Share on other sites

  • Administrators

The problem with the duration counter should be fixable, we're tracking it.

P_ESSW-17800

Link to comment
Share on other sites

So, the duration counter, as well as the object analysis counter, has also been included in its tracking. 

On the other hand, let me know if you need more information

Link to comment
Share on other sites

  • Administrators
1 hour ago, Hardq said:

@Marcos Waiting for some news please

The problem with the duration counter is tracked as I have mentioned. There is no ETA for a fix yet since it's a very minor visual issue.

Link to comment
Share on other sites

@Marcos 

Okay, it is a minor problem, I understand that there is no estimated time, so this affects the scheduled analyzes on the other hand, although the option of

Analyze, your computer is doing well while you verify the personalized analysis, is there an alternative solution for this?

Link to comment
Share on other sites

@Marcos

So if you have everything clear, I think that the information I pass is enough. Also take into account that this takes several hours if in

Custom analysis


This ticket is actually from the developer, right.

(P_ESSW-17800)

Link to comment
Share on other sites

  • Administrators
22 minutes ago, Hardq said:

@Marcos Waiting for a response or some help I really need it okay thanks

As I have already mentioned, we track it as a minor visual bug. There's nothing else to add.

Link to comment
Share on other sites

  • 2 weeks later...
Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...