Green Key won't show after initial FDE Encryption SG Enterprise 5.50

---

RTB wrote:

One of my customers reports back that after initial encryption that appear to be successful, the green key won't show up on boot partion in Explorer. SGNState reports back that the disk is encryption, so does the Management Center. Everything seems to be correct, but the icon won't show. I've also confirmed that the "Show overlay icons in explorer" is not set to NO. The green key appears on other machines using the same policy,

Are there any tricks to getting the "green key" back, as this might confuse the user?

RTB

---

Hi RTB,

Thank you for posting your question in the SophosTalk community forums.

The only time I have seen something like the behavior you are describing in the past was when anti-spyware falsely identified our classID as Win32.Adverts.TrojanDownloader malware :mansurprised: and moved the referenced DLL (bedevctlps.dll) to a quarantine queue. When all the details were worked out, we had the anti-spyware company exclude our DLL and we now use a registered classID.

You may want to start there and if my advice does or doesn't yield any useful results, please open a case with Sophos Technical Support. If the bedevctlps.dll is being falsely accused of being malware again, we will work with the software manufacturer to resolve this misunderstanding. :smileyhappy:

---

RTB wrote:

One of my customers reports back that after initial encryption that appear to be successful, the green key won't show up on boot partion in Explorer. SGNState reports back that the disk is encryption, so does the Management Center. Everything seems to be correct, but the icon won't show. I've also confirmed that the "Show overlay icons in explorer" is not set to NO. The green key appears on other machines using the same policy,

Are there any tricks to getting the "green key" back, as this might confuse the user?

RTB

---

Hi RTB,

Thank you for posting your question in the SophosTalk community forums.

The only time I have seen something like the behavior you are describing in the past was when anti-spyware falsely identified our classID as Win32.Adverts.TrojanDownloader malware :mansurprised: and moved the referenced DLL (bedevctlps.dll) to a quarantine queue. When all the details were worked out, we had the anti-spyware company exclude our DLL and we now use a registered classID.

You may want to start there and if my advice does or doesn't yield any useful results, please open a case with Sophos Technical Support. If the bedevctlps.dll is being falsely accused of being malware again, we will work with the software manufacturer to resolve this misunderstanding. :smileyhappy: