Guest User!

You are not Sophos Staff.

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

Boot error with Sophos

DatexDSM

hello,

I have a problem with an encrypted disk (using sophos). When I start my computer, a black screen is showing "Sophos is starting, please wait" and a few second after that, a blue screen appears (not the Windows bluescreen!!), it is a blue background, probably the background of the Sophos software... and then, the computer reset again and again (doing the same thing all the time)... I have my users access, but I can identify my because Sophos does'nt start...

I tried to use a bottable CD with special version of windows with sophos and then repair the MBR but it did not work... 

Ps: Sorry for my english but I'm a french person :)

Can you help me please?

Thanks you in advance,

Best regards,

Guillaume. 

:26531


This thread was automatically locked due to age.
  • 0
    Sounds like you're not using the latest version. A lot of issues were fixed in SafeGuard 6.0 and you'll have a white background screen by default not blue. My advice is upgrade, a lot of the older versions are going into legacy and support won't be there forever for it. As to what to do in order to fix this, find a windows 7 bootable DVD (yes even if it's windows xp it will still work), boot to a command line repair console and use the following commands: bootrec /fixmbr bootrec /fixboot that will remove POA, sounds like you have a failed install that didn't encrypt. If it's encrypted you will need to decrypt the hard drive first (use a USB to SATA kit) and assign your user the BOOT_{HOSTNAME} key to be able to access, make sure you give your user decryption rights. Decrypting a drive from USB removes POA but the system is NOT BOOTABLE UNTIL YOU FIX THE MBR AND BOOT ENVIRONMENT!! Now do whatever it takes to upgrade your environment to 6.0, even if that means spending money/time you didn't intend. You'll thank yourself later. Make sure to use the latest POA confix xml file with your install, it helps a lot. If this issue still happens make sure to run a full chkdsk /R on the drive, and use the manufacturers drive testing utility. The MOST COMMON reason for this is either incompatible SATA chipset (more common when using older safeguard versions which is why you upgrade) and POA gets installed on one or more blocks of bad sectors that should have reported by the SATA drive controller board but wasn't (it also probably should have passed SMART either). This has been a common issue with drives near end of life as well as lower end 2.5 in drive manufacturers. The most common brand name failures in order of failure rates (most common failures being 1st) I have experienced personally for 2.5 in SATA drives. 1. Toshiba/Fujitsu (Fujitsu sold their manufacturing of hard drives to Toshiba) 2. Hitachi 3. Samsung Hope that helps. Not a quick fix but the german engineers really did do a great job with 6.0 and there's so many minor fixes, speed improvements, etc, that you're shooting yourself in the foot wasting time with anything else.
    :26561
Unfiltered HTML