Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 5 subscribers
  • Views 14106 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

Why Sophos Safeguard Enterprise 6.0 Breaks MBR?

furtadov

We use sophos safeguard 6.0 and once in a while we get a PC with a corrupt MBR where we have to use the sophos boot disc to fix it, and its very time consuming as we can't re-image the device. My question is why this happens, and is there a way to prevent this , is there  a quicker fix?

Thanks,

:44067


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

    The error occurs when an encrypted machine boots straight into the Windows Recovery Environment (due to an unexpected shutdown) and launching the automatic repair function.

    Due to the fact that the disk is encrypted and the Windows Recovery Environment cannot access OS information, the Windows Recovery Environment cannot complete all operations and unfortunately leaves the BCD (Boot Configuration Data) store in a chipped state, which results in the error on boot.

    The following Knowledge Base Article describes the issue and how to resolve it:

    SafeGuard Enterprise Client fails to boot, Windows error: Recovery from "File: \Boot\BCD Status: 0xc000000f" or File: Boot\BCD status 0xc0000098

    http://www.sophos.com/en-us/support/knowledgebase/112846.aspx

    With the release of SafeGuard Enterprise 6.10, with the installation (or upgrade) of SafeGuard Enterprise, we will inject drivers into the Windows Recovery Environment, so the Recovery Environment has access to the encrypted disk after booting the machine through POA and so the issue will no longer occur.

    The attempt of injecting drivers into the Windows Recovery Environment is also available for versions < 6.10. Please contact Sophos support and request information from KBA 117092.

    Regards,

    ChrisD

    :44091
Reply
  • 0

    The error occurs when an encrypted machine boots straight into the Windows Recovery Environment (due to an unexpected shutdown) and launching the automatic repair function.

    Due to the fact that the disk is encrypted and the Windows Recovery Environment cannot access OS information, the Windows Recovery Environment cannot complete all operations and unfortunately leaves the BCD (Boot Configuration Data) store in a chipped state, which results in the error on boot.

    The following Knowledge Base Article describes the issue and how to resolve it:

    SafeGuard Enterprise Client fails to boot, Windows error: Recovery from "File: \Boot\BCD Status: 0xc000000f" or File: Boot\BCD status 0xc0000098

    http://www.sophos.com/en-us/support/knowledgebase/112846.aspx

    With the release of SafeGuard Enterprise 6.10, with the installation (or upgrade) of SafeGuard Enterprise, we will inject drivers into the Windows Recovery Environment, so the Recovery Environment has access to the encrypted disk after booting the machine through POA and so the issue will no longer occur.

    The attempt of injecting drivers into the Windows Recovery Environment is also available for versions < 6.10. Please contact Sophos support and request information from KBA 117092.

    Regards,

    ChrisD

    :44091
Children
No Data
Unfiltered HTML