Support Center > Search Results > SecureKnowledge Details
After inserting new HDD to an encrypted system, BSOD occurs after initial reboot Technical Level
  • After inserting a new HDD to an encrypted system, the machine boots and once in the OS, it prompts for a reboot to initialize the encryption, but after the initial reboot a BSOD (bluescreens) occurs.

The HDDs do not have the same configuration. This causes the failure.

  1. Once you first insert the new HDD, boot the system.

  2. When in the OS, open the Disk Management and confirm the following: Match the new HDD's settings to the HDD that is already encrypted.

    File system

    MBR or GPT

    RAID not supported 

    Partitions that are part of stripe or volume sets are also not supported

  3. Open SmartEndpoint console > Policy > FDE  and Edit Properties on the first setting > Volume Encryption

  4. Under Additional Settings, select "Allow encryption of volumes that were detected after the initial installation".

  5. Install the policy.
This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.

Give us Feedback
Please rate this document