File Share Encryption

 View Only
  • 1.  SSD whole disk encription = unbootable system (windows XP)

    Posted Dec 21, 2012 08:11 AM

    Hi,

     

    In my company for security purposes PGP Encryption is mandatory. Allthough this puts down the laptop (boot time is around 40 minutes for a 2Ghz Core2Duo) not to mention how it works in general. In order to solve this I decided to deploy the windows on a SSD. After installing everything I had to install I was amazed with the performance of the pc. Ok, this is fantastic.

    Now let's start and encrypt this beautiful rage fast disk. Well here comes trouble: after pausing the encryption I rebooted the pc. Guess what? hal.dll missing stroke me in the head and it does that since yesterday, no matter what I am trying.

    The scenario is like this:

    Laptop: Lenovo T61

    SSD: 120GB SSD (samsung)

    OS: Windows XP

    PGP Version: 10.2

    Sata mode: Compatibility (from bios settings)

    2 Partitions (checked and alligned)

    Start encryption-> pause @ 2% -> reboot->pgp input password-> enter-> "Windows could not start because the following fil is missing or corrupt: <windows root>\system32\hal.dll. Please re-install caopy of the above file.

     

    I've looked everywere for a solution, but until nothing. Can someone please provide some feedback on this?

     

    Thanks.

     

     



  • 2.  RE: SSD whole disk encription = unbootable system (windows XP)

    Posted Dec 21, 2012 08:42 AM

    Please see this Knowledge Base Article.



  • 3.  RE: SSD whole disk encription = unbootable system (windows XP)

    Posted Dec 21, 2012 09:05 AM

    yes, I've seen that, however I stil need to encrypt the drive, and  I'll bump in exactly the same situation. Maybe I wasn't clear: I need to boot the encrypted drive otherwise the security audit is gonna make me problems :).



  • 4.  RE: SSD whole disk encription = unbootable system (windows XP)

    Posted Dec 21, 2012 09:22 AM

    I would subsequently try the current 10.2.1 MP5 version of PGP for the WDE.  Although I don't see anything specific to hal.dll, there are inability to boot problems resolved in the builds more recent than 10.2.