Jump to content

NuclearSSD

Members
  • Posts

    24
  • Joined

  • Last visited

Posts posted by NuclearSSD

  1. 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.

     

  2. 45 minutes ago, WebbyTech said:

    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.....

    OK, so seems it is this service, but it does not remove when you ask it to! Order I took to resolve this issue...

    1. Remove EFSW
    2. Restart Server
    3. Run "sc delete epfwwfpr" in elevated cmd (Should get [SC] DeleteService Success)
    4. Restart Server
    5. 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.
    6. Install new version of EFSW
  3. 4 hours ago, Marcos said:

    Looks like the machine was not rebooted after enabling advanced network protection logging. Anyways, the root cause of the errors is clear. For some reason the old driver epfwwfpr.sys was not removed during upgrade for an unknown reason.

    Please run the following command as an administrator and reboot the server:
    "sc delete epfwwfpr"

    Reinstallation of EFSW should not be necessary, however, should an error still be reported after the reboot try uninstalling EFSW and installing it from scratch.

    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.....

  4. 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!

    image.png.64431e28da23225d2a0dec8eb9a76432.png

    Allow the communication then resolved my issue....

    Adjusting my policy to exclude this from "APPLICATION MODIFICATION DETECTION", or you could turn it off..

    image.png.07a4848afb3f0eedee22c7801490570f.png

    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/

×
×
  • Create New...