Jump to content

ESET FDE Version 1.4.62.0 update problem


Mromeroq
Go to solution Solved by Kstainton,

Recommended Posts

Hello i have recently upgrade ESET FDE to version 1.4.62.0 in a couple computers to test the update. i have presented the following alert on that module:

 

 Screenshot_1.png.6296f031620e9906078591af9a71dfcf.png

Is this a known error on the update? how can i solve it

 

 

Link to comment
Share on other sites

  • ESET Staff
Posted (edited)

Hi @Mromeroq,

Can you acquire the following logs for me: https://support.eset.com/en/kb3466-collect-logs-with-eset-log-collector-for-windows

As well as zipping the following folder for us:

C:\ProgramData\ESET\ESET Full Disk Encryption\Updater

Once both of these have been obtained, can you submit a support ticket via https://www.eset.com/int/support/contact/ attaching these please.

Thank you,

Kieran

Edited by Kstainton
Link to comment
Share on other sites

I also have this issue on a couple of devices. Rest have upgraded fine

 

Did you manage to find a solution to it in the end?

Link to comment
Share on other sites

  • ESET Staff
  • Solution

Hi @Mromeroq and @Andy Kida,

Ideally I would like to see logs as requested above from an affected machine, just to confirm it is the same issue we saw previously. But I suspect the following should resolve your issue.

Delete both:

  • EFDEUpdateService.cfg
  • EFDEUpdateService.log

Under C:\ProgramData\ESET\ESET Full Disk Encryption\Updater

Thank you,

Kieran

Link to comment
Share on other sites

On 4/4/2024 at 2:11 PM, Kstainton said:

Hi @Mromeroq,

Can you acquire the following logs for me: https://support.eset.com/en/kb3466-collect-logs-with-eset-log-collector-for-windows

As well as zipping the following folder for us:

C:\ProgramData\ESET\ESET Full Disk Encryption\Updater

Once both of these have been obtained, can you submit a support ticket via https://www.eset.com/int/support/contact/ attaching these please.

Thank you,

Kieran

Sorry for the late response. I couldn't sent the log files do to the size of one of them. But this solved it on the endpoints that I was getting this error.

Link to comment
Share on other sites

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

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