Bit Locker Recovery Key Requested at Boot Time

I installed yesterday the update package of 10 Dec, which included a firmware update. After completing the installation, the Surface 2 made a reboot, but it failed to reconstruct the Bitlocker key.  After I reentered the key, the reboot completed successfully. The battery report showed no issues.  The Bitlicker-API log showed, as it did earlier, an error with event-ID 842, and a warning with event-ID 843.

This morning I wanted to see if the Surface 2 could survive a cold reboot. So I switched it off completely, and restarted. Again reconstruction of the Bitlocker key failed.  After I entered the Bitlocker key once more, I got an error which I had earlier, and which also others reported: “Your PC ran into a problem and needs to restart. We're collecting some error info, and then we'll restart for you. (0% complete) If you'd like to know more, you can search online later for this error: PAGE_FAULT_IN_NONPAGED_AREA". It never completed and only a hard boot could solve it.

Rebuilding the Surface 2 as Microsoft seems to have suggested to some of you isn’t going to solve the problem, as I made a rebuild earlier. Microsoft is not intending to get involved either, because they don’t come with any useful suggestions despite the fact that they have got a lot of useful information from us. Continuing this thread is therefore not really productive. One just has to accept that the Surface 2 has some built-in problems that can be corrected if you know how, but for which Microsoft is not able to give a permanent solution. I can live with that, but persons who have no real practical experience with handling Windows errors in PCs, should not buy a Surface 2.

Thanks for now,

/Wim

Hello  BrianneMetzger

Sorry to hear you are having problems with your Surface2 and difficulty getting your bitlocker recovery key.

I found some details that may help point you in the right direction Here.

Let us know if this helps.

Best regards

Thanks for the help that seems to be the only thing I can find in my searches as well. Which means my only option is to reset my Surface to factory settings. Which isn't the worst, I suppose, since I don't have anything important saved on it. Just annoying because I have spent a long time customizing it the way I like.

I installed yesterday the update package of 10 Dec, which included a firmware update. After completing the installation, the Surface 2 made a reboot, but it failed to reconstruct the Bitlocker key.  After I reentered the key, the reboot completed successfully. The battery report showed no issues.  The Bitlicker-API log showed, as it did earlier, an error with event-ID 842, and a warning with event-ID 843.

This morning I wanted to see if the Surface 2 could survive a cold reboot. So I switched it off completely, and restarted. Again reconstruction of the Bitlocker key failed.  After I entered the Bitlocker key once more, I got an error which I had earlier, and which also others reported: “Your PC ran into a problem and needs to restart. We're collecting some error info, and then we'll restart for you. (0% complete) If you'd like to know more, you can search online later for this error: PAGE_FAULT_IN_NONPAGED_AREA". It never completed and only a hard boot could solve it.

 

Rebuilding the Surface 2 as Microsoft seems to have suggested to some of you isn’t going to solve the problem, as I made a rebuild earlier. Microsoft is not intending to get involved either, because they don’t come with any useful suggestions despite the fact that they have got a lot of useful information from us. Continuing this thread is therefore not really productive. One just has to accept that the Surface 2 has some built-in problems that can be corrected if you know how, but for which Microsoft is not able to give a permanent solution. I can live with that, but persons who have no real practical experience with handling Windows errors in PCs, should not buy a Surface 2.

 

Thanks for now,

 

/Wim

Well, this is a community forum. It is not really monitored by Microsoft support staff. The community of users help each other. This is a great deal of information and I do not doubt Microsoft may be a ware of this issue and are working on a fix. Sometimes no answer is the answer.

Now to be sure Microsoft sees and hears us, we need to post on their surface feedback page. They read and monitor their feed back pages. No, this is not a review page... Even better is twitter. We are going out with pitchforks, just state the problem and frustration... The more post, the more we force them to acknowledge the fix and response...