Guest User!

You are not Sophos Staff.

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

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

Snooman

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.
  • 0

    Hi Snooman,

    could you please specify what "do not start Windows7 anymore" exactly means? Do you receive an error, i.e.  "File: \Boot\BCD Status: 0xc000000f" or "File\Boot\BCD Status: 0xc0000098" ?

    If above is true, you might want to have a look into: http://www.sophos.com/en-us/support/knowledgebase/112846.aspx


    Cheers,

    ChrisD

    :28905
  • 0

    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
  • 0

    We had the same problems with some HP Notebooks here.

    Only solution till now is reinstall the clients. I tried my luck with bcdedit but that ended with POA not showing anymore.

    Greets

    Stephan

    :28917
  • 0

    I'm aware of one issue where machines with a series of specific SSD drives was affected from the exact same issue. The problem was the hardware (firmware, in particular the garbage collector function) of the drive, that had an issue which led to system errors after the system was in use for about two to three months.
    Before the boot problems started to occur, the machines were affected by a BSoD with the following Stop code "Page Fault in a Non Paged Area"  Stop: 0x00000050.

    You might want to check if you are using SSDs with an old firmware version on it (issue in our database was logged in 2010) and if there is a new firmware version available update it.

    Just an idea though...

    ChrisD

    :28925
  • 0

    Thanks for your answers!

    In our case the affected machines had classic harddrives / no SSD-Drives, so much i can say.

    :28953
Unfiltered HTML