Microsoft fixes Surface 2 BitLocker prompt error

Microsoft fixes Surface 2 BitLocker prompt error

Summary: Microsoft has issued a fix for a BitLocker prompt error affecting users with second-generation ARM-based Surface 2 devices.


Microsoft has issued a fix for a BitLocker-related problem affecting Surface 2 users.


Some users of Microsoft's ARM-based Surface 2 devices have been complaining that when resuming or restarting their devices from sleep, they have been prompted to enter their BitLocker recovery keys. For some, the problem was occuring every time they attempted to power up their Surface 2s; for others, the problem was intermittent.

On January 6, Microsoft released an update to fix this problem. The update is available for download via Windows Update.

According to a Microsoft Support page, this update does not replace any previously released Surface 2 updates. Users may be prompted to restart their devices after applying this update.

First-generation Surface RT devices and Intel-based Surfaces were not affected by this BitLocker problem/glitch.

Surface Pro 2 users still do not have a patch or update for the battery-life drainage issue caused by a December 2013 Surface Pro 2 firmware update. Microsoft subsequently pulled that faulty update and said a fix would be coming after the holidays.

Next week is Patch Tuesday, so maybe we'll see a fix by then. So far, no fix and no update from Microsoft as to when the Surface Pro 2 battery issue will be resolved. (I asked again today in case there's new word. If I get an updated statement, I will add it.)

On the bright side, however, some users who have been returning Surface Pro 2 devices due to the faulty firmware update have been provided with replacement models with slightly faster Haswell processors.

Topics: Microsoft Surface, Microsoft, ARM, Business Intelligence, Windows 8


Mary Jo has covered the tech industry for 30 years for a variety of publications and Web sites, and is a frequent guest on radio, TV and podcasts, speaking about all things Microsoft-related. She is the author of Microsoft 2.0: How Microsoft plans to stay relevant in the post-Gates era (John Wiley & Sons, 2008).

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


Log in or register to join the discussion
  • What About Bitlocker Prompts After a BSOD?

    On Windows 8.1, because WinRE is enabled by default, I get a BitLocker prompt whenever my computer crashes, improperly shuts down, etc. Obviously this is caused by Windows changing the boot configuration to start the recovery environment, but it is very annoying. I have to keep emailing myself the recovery key so that I have it handy on my encrypted cell phone. Occasionally, I will forget to re-email it to myself and will have to call the help desk when this happens.

    The most annoying part about this is: I don't even want to use WinRE. I just want my computer to attempt to reboot normally after a crash. WinRE does it's scan/check, and then determines it can't do anything to help. My only option is to "Shut Down". After shutting down, the computer boots up fine.

    So, while it's a good idea in theory, all this WinRE-induced BitLocker annoyance is pointless.
  • Wow

    If there really isn't a fixed firmware update tomorrow, that is absolutely ridiculous. We've already had the battery broken (reporting 50% capacity) for a month, and if they expect me to wait indefinitely (another month, or maybe more) for a fix, that's just sad.

    I mean, not just saying this because I'm affected, but the power users and system admins who are manually checking for updates immediately on Patch Tuesday (as opposed to users who wait for automatic updates, which with a pulled update, were much more likely to not have this issue) are the people that Microsoft can least afford to upset.

    Personally, if it's not fixed tomorrow, I'm definitely going to be heading right over to the Microsoft Store after work with the hopes of getting it swapped out for a brand new unit.
    • Oops

      Oops, I meant next Tuesday, not tomorrow. Got confused by the date for a second. :D
      • no worries

        no worries, it's already ridiculous that they couldn't fix it by tomorrow. All that we've asked for was a rollback to previous functionality. Given that a working sleep mode is probably very high up on importance for most users, MS's unwillingness to provide that put a dent into my plan to sell the pro 2 end of this year and buy a pro 3. I will probably stick to the first part of that plan.
  • one down

    zillion more to go.

    waste of time.