NobelDwarf
-
Posts
27 -
Joined
-
Last visited
Kudos
-
NobelDwarf gave kudos to Marcos in Issue with our ESET Endpoint & Server Security for ESET PROTECT Advanced
It might be related to the synchronization issue that we notified about at https://status.eset.com/.
Should the problem persist after the issue has been resolved, please raise a support ticket.
-
NobelDwarf gave kudos to AAndrejko in ESETFDE dlpfde.sys causing issues
Hi @NobelDwarf
It seems actually the issue is a combination of things. So if you turn off fast startup and hibernate on these devices temporarily then it should resolve the issue until the new version comes around.
Kind regards
Ashley
-
NobelDwarf gave kudos to AAndrejko in ESETFDE dlpfde.sys causing issues
Hi @NobelDwarf
This issue has been fixed internally in both ESET Full Disk Encryption and ESET Endpoint Encryption.
A fixed version of EEE we are due to release roughly the start of December. EFDE we expect to release around the January time.
This issue as you've pointed out is just an issue with 24H2 so I'd suggest you don't update the rest of your systems with EFDE or EEE on just yet.
Kind regards,
Ashley
-
NobelDwarf gave kudos to igi008 in Protect Cloud Interface Changes
We will also consider bringing back the "Worst Functionality Problem" as a column in the main device table. The reason is that we have completely rewritten the Computer's section, enabling us to implement more effective features in the future. Some features were reduced because they were somehow redundant. However, we appreciate your feedback and are considering bringing it back.
For now, we also suggest using the "Advanced Filter" to filter out computers where specific problems occur. This method is better because it includes not just the worst, but all problems on all computers. In combination with the STATUS, you can identify the most pervasive problems in the network.
Last but not least, the exact list of all problems on a specific computer can be found by clicking on the computer name. In the side panel under the Alerts section, there is a list of all problems for that computer.
We are also working on an improved Status Overview dashboard, which will provide a tile with the top functionality problems to promote this information and provide a drill-down action to fix them.
-
NobelDwarf gave kudos to Kstainton in Surface Pro 9 FDE
Hi @NobelDwarf,
Yes it sounds exactly the same in that case, and we are still currently researching this with MS to see what can be done in future. But for now, 'Secured Core' will have to be disabled to function with EFDE / EEE.
Thank you,
Kieran
-
NobelDwarf gave kudos to Kstainton in New Surface BIOS update breaks FDE and renders laptop unbootable!
Yes, seems to only affect what we believe to be Firmware Version 9.101.143.0 at this time for the Surface Laptop 5 specifically and not the former Firmware Version 7.10.143.0. So some people may notice their Surface Laptop 5 machines be fine initially and then once updated to the latest firmware start experiencing the issue and need to disable 'Secured Core' as mentioned previously.
-
NobelDwarf gave kudos to AAndrejko in New Surface BIOS update breaks FDE and renders laptop unbootable!
Hi @FTL
Thank you for sharing this information with everyone. Indeed we are currently experiencing an issue with the Surface Laptop 5 with Secure Core enabled when booting a fully encrypted system on Full Disk Encryption & Endpoint Encryption. The current and only workaround for this is to turn Secure Core off as you've stated above.
We're currently still investigating the issue, but we do actually have a Surface Laptop 5 which we're able to replicate the issue on so I am hopeful we can find a solution to it soon. I can see some investigation work has already been carried out on the matter, however I imagine a fixed version wouldn't be available until after the new year the very least. I'd like to also note other devices with Secure Core enabled don't seem to be affected so it seems targeted towards that BIOS update of the Surface.
I'm sorry for any inconvenience this has caused to yourself or anyone else affected.
I will speak to my team to see if we can publish something in the meantime.
Kind regards,
Ashley
-
NobelDwarf gave kudos to Marcos in PUA Blacklist Block
Should be unblocked now. If not, it will be shortly.
-
NobelDwarf gave kudos to AAndrejko in Full Disk Encryption ignoring policy
Hi @NobelDwarf
Thank you for your report.
This has already been fixed internally and we'll be releasing a fixed version to combat this issue within the next couple of weeks.
Kind regards,
Ashley
-
NobelDwarf received kudos from Sebastiaan in Endpoint Encryption and BitLocker
This happens all the time with me with laptops that have secure boot enable bitlocker encryption the drive int he background but doesnt full turn it on. Once I have turn it on, save the key then remove the encryption it fixes the issue and you can use ESET Encryption.
-
NobelDwarf received kudos from Kstainton in Endpoint Encryption and BitLocker
This happens all the time with me with laptops that have secure boot enable bitlocker encryption the drive int he background but doesnt full turn it on. Once I have turn it on, save the key then remove the encryption it fixes the issue and you can use ESET Encryption.
-
NobelDwarf gave kudos to JPritchard in ESET Full Disk Encryption Recovery Passwords
Hello,
As far as I know, it is not possible to remove recovery passwords from the ESET Protect console.
I suspect the computer in question has been decrypted and re-encrypted several times. Each time you encrypt a computer (even if it's the same computer) a Workstation ID is generated. This is likely why you're seeing three recovery passwords, but each have different Workstation ID's.
When reseting a User's password in this manner, always match the index number and the Workstation ID with what the User see's on their computer in the recovery screen.
Kind regards,
Jay Pritchard
Encryption Technical Support Engineer III / Team Lead
-
NobelDwarf gave kudos to Marcos in Detections Actions Error
The issue is caused by an older version of the Translation support module. On Monday we should start with upgrade, however, it will require a restart of the ESET PROTECT Cloud instance.
-
NobelDwarf gave kudos to Marcos in Detections Actions Error
Please raise a support ticket with your ESET UK. It's probably caused by the update of the Translation support module yesterday, however, I don't have this problem myself so there must be also something else that triggers the issue.