Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 5 subscribers
  • Views 5997 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos Drive Encryption removes windows boot settings

ChrisMenai

I currently have 2 desktop computers and 2 laptops which need Sophos Disk encryption installed. Both the laptops install the software and encrypt the disks fine. One is a Dell Latitude E5500 and the other a Dell Latidue 13.

Unfortunatelly i cannot get the software to install properly on the two desktop computers. Both are Microsoft Stone DH55TC systems. they are using Intel H55 chipset motherboards. The problem occurs when the systems first reboot after installing the encryption client software. On the first reboot, the computers initialise Sophos correctly, but then fail to load the operating system. After some research i found that the boot settings for the operating system are being deleted when Sophos runs on the startup of the computers.

Version is 5.50.0


Is there any way to solve this issue?

 EDIT:

After MORE research, i found that the boot settings were only deleted on one of the computers (faulty obviously) but on the other, Sophos encryption just fails to find the OS at all. Its asif Sophos starts, and just cant find any OS to boot, and so restarts.

Having used winPE 3, i can access the OS files on the hard drive while running winPE from a CD, i can do this while Sophos is still installed and doesnt allow the hard drive to boot.

I dont know what else to do.

thanks

:4694


This thread was automatically locked due to age.
Parents
  • 0

    Hi Chris,

    as you already mentioned in your post the advisory just and only (!) applies to Dell machines. At the moment we are still analyzing the root cause.

    With regards to your issue you are talking about a non DELL machine. In this case please note that we are talking about a different issue showing the same behavior.

    In such a case a different type of analysis (here: having a direct look at the machine) is required. The only common thing here is that both machines show the same behavior but the root cause is very likely a different one - therefore the machine mentioned by you must be treated completely separately. 

    For sure you can request via the local help desk using your case reference number at any time.

    Regards

    Dan

    :5203
Reply
  • 0

    Hi Chris,

    as you already mentioned in your post the advisory just and only (!) applies to Dell machines. At the moment we are still analyzing the root cause.

    With regards to your issue you are talking about a non DELL machine. In this case please note that we are talking about a different issue showing the same behavior.

    In such a case a different type of analysis (here: having a direct look at the machine) is required. The only common thing here is that both machines show the same behavior but the root cause is very likely a different one - therefore the machine mentioned by you must be treated completely separately. 

    For sure you can request via the local help desk using your case reference number at any time.

    Regards

    Dan

    :5203
Children
No Data
Unfiltered HTML