NuclearSSD

Seems our link has broken and it will not accept re-entering the credentials, we get the following error.

Cannot load ESET Protect Cloud, not loading, see attachment.

We have our "ESET PROTECT Connections" configured and connected to our Cloud PROTECT, it seems to have pulled in everything initially, but it's not showing any new Dynamic Groups we are creating. It seems to show it being healthy and synced recently. The new dynamic group were created 2 days ago.

Is this still on the radar? or is it implemented now?

As below

Something like this... but it seems that this pulls in stuff that is encrypted as some partitions are "not encryptable"

I'm struggling to get the right combination for detecting devices that are not encrypted. Could someone please advise?

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.