Guest User!

You are not Sophos Staff.

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

SGE 5.6: After successful POA Logon Windows7 boots into Recovery Console

Hi,

we're experiencing a number of cases where our Safeguard 5.6 protected machines (Lenovo) do not start Windows7 anymore.

When booting it is possible to perform the POA Logon as usual, but afterwards Windows fails to start.

The Microsoft Recovery Console shows up and the automatic repair fails. Command line access to drive C: fails "no known filesystem".

Is there an option to repair this ?

:28903


This thread was automatically locked due to age.
Parents
  • Thanks for your quick response, but it's not any issue related to BCD.

    POA authentication works normally, after that OS is loading...

    So far so good.

    Immediately afterwards Windows shows a text screen that Windows could not be loaded due to hard-/software change.

    There are two options available: start normally or start recovery console. Whatever you choose you are ending up in Microsoft Recovery Tools Console. Automatic Repair does not help.

    If you select command line promt and try to access drive C: it says: "The volume does not contain a recognized file system"

    We are facing this issue on multiple machines now. Sometimes the error returns shortly after a complete client reinstall.

    :28913
Reply
  • Thanks for your quick response, but it's not any issue related to BCD.

    POA authentication works normally, after that OS is loading...

    So far so good.

    Immediately afterwards Windows shows a text screen that Windows could not be loaded due to hard-/software change.

    There are two options available: start normally or start recovery console. Whatever you choose you are ending up in Microsoft Recovery Tools Console. Automatic Repair does not help.

    If you select command line promt and try to access drive C: it says: "The volume does not contain a recognized file system"

    We are facing this issue on multiple machines now. Sometimes the error returns shortly after a complete client reinstall.

    :28913
Children
No Data