NuclearSSD

I think that Marc wanted was to install the additional keyboard. https://help.eset.com/efde/en-US/add_remove_keyboard_layouts.html This should do the trick

I am getting the same on a Dell, not sure how to resolve this one apart from completing rebuilding Windows.

Alrightly then, if anyone else gets this, it seem if you have the dreaded Windows \ Office 365 TPM Issue, like this one https://answers.microsoft.com/en-us/outlook_com/forum/all/error-code-80090016-trusted-platform-module-has/c0588197-a33a-423f-bcb0-4ab5cda58928 then you need to fix that first.

I have just noticed this is the wrong forum, but cannot see one for EFDE

Maybe no, this passed the 2nd user screen to reboot again, with the instructions for the user, but once it came back up, failed.

Ok, it seems one has now worked after updated the BIOS Lenovo V130-15IKB

Struggling to get a few laptops encrypted, with the error in the subject Log files shows the following: [inspector] [error] [4724] Failed to take TPM ownership Then it will state the following on subsiquent reboots [inspector] [error] [4852] Encryption has failed previously so we will not continue I have removed the agent, cleared TPM, restarted, attempted to encrypt again and still the same.

All of our tasks were delayed by the amount of time in the agent policy to connect back in. If you are saying that this is not the case, then why have this setup ? We used to set install tasks and could clearly see nothing happening until the check in time.

I have noticed but chose not to question that some tasks when run seem to be instant, when before we used to have to wait for the PC to check in (every 15 minutes in our current policy). Has something changed? Or do I need to investigate further?

Thanks

Seems to have been asked before, but we have had it for some time now, on initial login it can take forever to login, can clearly see ERA PID file hitting 100% CPU. Is there anything we should be look at to help increase the performance? Quad Core 8 GB Ram

I Can see this one has been archived off a few times now, anyway to help find out what is doing this? Microsoft Office 365 - 16.0.12430.20264 ESET Endpoint Security - 7.2.2055.0 Seems Disabling Read and Received email stops this, but not really a solution, would appreciate some guidance please

OK, so seems it is this service, but it does not remove when you ask it to! Order I took to resolve this issue... Remove EFSW Restart Server Run "sc delete epfwwfpr" in elevated cmd (Should get [SC] DeleteService Success) Restart Server Run "sc delete epfwwfpr" in elevated cmd - Yes again to make sure it has gone, you should get a different message... if you get "[SC] DeleteService Success" again then back to step 3.. this has to go before you install again. Install new version of EFSW

Definitely did this in the order you requested, enabled, rebooted, collected logs and sent them to you. I have done the same as above but still getting error. I am just going to try it is a slightly different order... Remove EFSW, Delete Service, Reboot then Reinstall.....

I have followed the guide but then removed 6.5 and install 7.1.12008.0 File Security... However still getting an issue with non-functional modules.

I see this has been archived off... But I see there is no resolution, could someone please advise. It does look like that when disabling "Read Email" under "Email Client Protection" that this issue no longer happens.

Simple question, can we share Dashboards? We have a dashboard that we would like to share with other users. Thanks

Yes... This has been the routed I have taken, unfortunately, this by default is not enabled in the policy, or by default install on the client so I am having to do this manually but getting there

Superb find Sir ? Credit to you on this post

any idea on how to do this by CMD ? going to take forever

Might have come across another post which got me thinking! Looks like my issue is different as the ESET itself was blocking the agent from communicating, it made initial connection then stopped! making me think it was the server, but it seems once the policy had come across, ESET then detected a change to the application and blocked the replication! Allow the communication then resolved my issue.... Adjusting my policy to exclude this from "APPLICATION MODIFICATION DETECTION", or you could turn it off.. Unfortunately I am having to go around and allow it first before it can update the policy Credit to https://forum.eset.com/profile/20566-finams/

Linux?

Still the same, oddly though it look like one has checked in today at 3 in the morning, but bit actually given any information to what's installed... It's like it said hello then goodbye and not given any further information other than its name!

Same here, Have about 20 that haven't reported since upgrade on the 19th August! Reboot not helpinghere