Hi Edward Moolman 

I believe the client was not BitLocker-encrypted prior to adding to central. Can you please share us the client computer OS details.

Also, can you unassign and assign Device encryption for the client once and let us know if you are still facing the same issue? Please refer the following KBA for more details.

Sophos Central: How to assign and unassign Endpoint software to computers

Hi Gowtham Mani

Machine OS is Windows 10 Pro

The machine was successfully Encrypted when rolled out. BitLocker was enabled on the machine and Sophos Endpoint Security was installed. The machine was then added to the Encryption Policy, after a restart the machine started the encryption. 

The machine is encrypted and has been for the past year so that is not an issue, its about the fact that the Recovery key for volume is missing in windows.

I have trying your suggestion on un-assigning and assigning Device encryption for the client once and found that the issue still occurs. 

Hi Gowtham Mani

Machine OS is Windows 10 Pro

The machine was successfully Encrypted when rolled out. BitLocker was enabled on the machine and Sophos Endpoint Security was installed. The machine was then added to the Encryption Policy, after a restart the machine started the encryption. 

The machine is encrypted and has been for the past year so that is not an issue, its about the fact that the Recovery key for volume is missing in windows.

I have trying your suggestion on un-assigning and assigning Device encryption for the client once and found that the issue still occurs. 

Hi Edward Moolman 

Thanks for the update, can you please enable Remote assistance in Central and DM me the license number?

Also, May I have some additional details?

• Was any USB stick connected when the device was encrypted?
• How many clients have this issue?

Hello Edward,

If you acknowledge the alert, does it come back? 

Regards,

JR