Share via

Bitlocker-Drive Error

Anonymous
2011-04-01T21:34:25+00:00

Hi, recently I have been getting 2 error messages in Event Viewer at every startup, Event ID 24620, indicating that the volume info on 2 volumes cannot be read. The problem is that I don't use Bitlocker, I have Home Premium which doesn't support it. I don't have any encrypted volumes and haven't used any removable media with encrypted volumes.I also checked services and bitlocker isn't running.I googled this and found that others have had the same problem but I couldn't uncover any explanation for it. I would appreciate it if someone could tell me how to resolve this issue. Thanks in advance.

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Anonymous
    2011-04-02T14:06:38+00:00

    Hi Irfan, The problem is not with a crash and a clean boot doesn't help because the error occurs while the OS is loading and before anything else loads. When the computer boots, after POST it displays a list of the system drivers its loading, then it briefly displays a screen with system info.It then displays 2-4 error messages indicating that 2-4 bitlocker-encrypted drives cannot be read. These messages later appear in event viewer with the source indicated as Bitlocker-Driver.This is a well-known error message that normally occurs when you have bitlocker-encrypted volumes and need to enter a password.See this TechNet entry http://technet.microsoft.com/en-us/library/dd363874(WS.10).aspx . But I don't have bitlocker-encrypted volumes. Home Premium doesn't support bitlocker.I can't identify the volumes referred to because the system uses a lengthy alpha-numeric ID string to identify them, sequential strings,{0a3fe32c-ab1a-11de-82dd-806e6t6e6963},)a3fe32d,etc.This has happened to others but I couldn't find any explanation for it. Its unusal and confusing.But the underlying question seems straightforward, why is it referring to encrypted volumes  and, essentially, saying that it needs a password for them ?. And doing this at every startup. I have run Chkdsk and SFC /Scannow, no problems detected.I've used Win 7 for a long time and I have never seen this error before, so I would be very interested to hear what could cause this error and how it could be resolved.

    I'm editing this because I juist discovered that the TechNet article says that this applies to windows server 2008 but I'm using Win 7 Home Premium.Which just makes it all the more unusual.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2011-04-02T11:25:41+00:00

    Hello Dxmc,

    1.      Have you seen what is the faulty module on the event log?

    I suggest that you look at the event log and see what it the faulty module that is causing the crash on the computer.

    Also suggest that you set your computer to clean boot:

    a.      Click Start, type msconfig in the Start Search box, and then press ENTER.

    b.      If you are prompted for an administrator password or for a confirmation, type the password, or click Continue.

    c.        On the General tab, click Selective Startup.

    d.       Under Selective Startup, click to clear the Load Startup Items check box.

    e.      Click the Services tab, click to select the Hide All Microsoft Services check box, and then click Disable All.

    f.         Click OK.

    g.       When you are prompted, click Restart.

    After the computer starts, check if the issue is fixed, then follow the steps mentioned in the following KB article to narrow down the exact source:

    http://support.microsoft.com/kb/929135

    You can also set the computer to normal startup once you determine the service causing the issue. See the section on how return your computer to a Normal startup mode by following the steps under “Reset the computer to start as usual” in the above article.

    Thanks,

    Irfan H, Microsoft Answers Support Engineer.

    Was this answer helpful?

    0 comments No comments