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

SG8/Win10 - Sector-based initial encryption of drive C: failed and closed. Reason: 12496897 (0x00BEB001).

Lloyd Jones

 We are receiving this error when trying to perform initial BitLocker encryption after installing the agent and settings. I can only find reference to this error code in the SGN7 PDF located here: https://www.sophos.com/en-us/medialibrary/PDFs/documentation/sgn_7_h_eng_admin_help.pdf?la=en

It shows the details as "Encryption not possible due to error during kernel initialization." What does this mean?



This thread was automatically locked due to age.
Parents
  • 0

    I have got this from older support, see if that would help:

     

    Issue
    Initial encryption doesn't start. Symptomps (not always all are present)
    • SGN user state = pending
    • application event log shows: kernel initialization has failed. Internal code: 0x00007562
    • SGN trace log: Error occured: code=[1351], text=[The kernel volume couldn't be opened]
    if SGN trace log shows: EncryptVolume]=reason=[48]-  Description0[BDC_ERR_WRONGVOLUMESIZE],result=[0x54a] - please follow the KBA 112906
    Known to apply to the following Sophos product(s) and version(s) SafeGuard Enterprise Device Encryption
    All supported operating systems All supported OS
    What to do
    This issue is known to be caused by several factors, here is the summary:
     
     
    Possible cause What to do
    Disk Errors If the preinstall steps were not executed:
    • remove SGN Client and SGN Client Configuration
    • reboot
    • run chkdsk %systemdrive% /f /x /v /r
    • 4. reinstall SGN Client and SGN Client Configuration
    BIOS hard drive protection
    • Check BIOS settings - disable relevant settings if exist
    • reinstall SGN Client and SGN Client Configuration
    AntiVirus/endpoint security software, software deployment solutions, backup/imaging software
    • Disable the software in question
    • reinstall SGN Client and SGN Client Configuration

    -----------------------------------------

    Unfortunately none of these seem to apply to my case. I do a check disk and a bootrec /fixmbr on all the machines before I install SGN. I don't know of any bios setting that would fix this. I have encrpyted my pc (same model and type of T520), but it was installed from scratch. So, I already made a new image, but there are some laptops that have already been imaged and I am trying to avoid re-imaging them.

    Any suggestions on what I could do would be greatly appreciated.

Reply
  • 0

    I have got this from older support, see if that would help:

     

    Issue
    Initial encryption doesn't start. Symptomps (not always all are present)
    • SGN user state = pending
    • application event log shows: kernel initialization has failed. Internal code: 0x00007562
    • SGN trace log: Error occured: code=[1351], text=[The kernel volume couldn't be opened]
    if SGN trace log shows: EncryptVolume]=reason=[48]-  Description0[BDC_ERR_WRONGVOLUMESIZE],result=[0x54a] - please follow the KBA 112906
    Known to apply to the following Sophos product(s) and version(s) SafeGuard Enterprise Device Encryption
    All supported operating systems All supported OS
    What to do
    This issue is known to be caused by several factors, here is the summary:
     
     
    Possible cause What to do
    Disk Errors If the preinstall steps were not executed:
    • remove SGN Client and SGN Client Configuration
    • reboot
    • run chkdsk %systemdrive% /f /x /v /r
    • 4. reinstall SGN Client and SGN Client Configuration
    BIOS hard drive protection
    • Check BIOS settings - disable relevant settings if exist
    • reinstall SGN Client and SGN Client Configuration
    AntiVirus/endpoint security software, software deployment solutions, backup/imaging software
    • Disable the software in question
    • reinstall SGN Client and SGN Client Configuration

    -----------------------------------------

    Unfortunately none of these seem to apply to my case. I do a check disk and a bootrec /fixmbr on all the machines before I install SGN. I don't know of any bios setting that would fix this. I have encrpyted my pc (same model and type of T520), but it was installed from scratch. So, I already made a new image, but there are some laptops that have already been imaged and I am trying to avoid re-imaging them.

    Any suggestions on what I could do would be greatly appreciated.

Children
  • 0 in reply to AhmedIbrahim

    Hi AhmedIbrahim,

     

     We removed the SGN client and configuration, rebooted, and then ran chkdsk. After reinstalling the client and configuration, we see the attached message. If we try to turn on BitLocker manually though, it asks for a PIN (and presumably passes the TPM check). Any thoughts?

Unfiltered HTML