How To Fix: Bitlocker Recovery Key Prompts On Every Reboot

windows-10-bitlocker-featured

There are few reports of users having Bitlocker issues following the October 2016 patches.

The issue: On every reboot, the Bitlocker recovery key is required which is quite disruptive and cumbersome. As a workaround in order to solve this issue, the following steps can be taken:

On the next reboot and once in Windows, reset Bitlocker by disabling and re-enabling it.
In administraive command prompt, do the following:
manage-bde -protectors c:-disable
then do this:
manage-bde -protectors c:-enable

At this time, I’m not certain on which patch is causing the issue but I wanted to share this info to help. You can also discuss in this TechNet post.

Follow (@Hoorge) on Twitter and join Tech Konnect on Facebook and Twitter (@TechKonnect) to stay current on technology related matters.

System Center Operations Manager (SCOM) Console Crash

scom-gsx-solutions

** UPDATE**
(October 19, 2016)
A fix for the SCOM console crash issue as previously blogged below has been released. See the following KB320006 article to obtain the hotfix.

***************************************************************************************************

**Posted on October 18, 2016**

There is a widespread report of System Center Operations Manager (SCOM) 2012 R2 / 2016 console crashes due to some bugs in October 2016 Cummulative Updates, in particular with the following patches: KB3194798 / KB3192392 / KB3185330 / KB3185331.

The product team has acknowledged the issue on their blog post and is said to be working on releasing a fix soon. The current recommendation is to uninstall the problematic patches as a temporary workaround. According to the blog post, an announcement will be made on the SCOM Team blog when a fix has been made available. So, keep a close eye on it.

Links related to this post:

SCOM Product Team Console Issue Ackowledgement
TechNet Discussion
SCOM Product Team Blog
Microsoft Tech Community Discussion

Follow (@Hoorge) on Twitter and join Tech Konnect on Facebook and Twitter (@TechKonnect) to stay current on technology related matters.

Update – Windows ADK For Windows 10 (Version 1511)

windows10_adk

Update / Warning:

Aaron Czechowski, Senior Program Manager, Enterprise Client and Mobility has issued a warning regarding the latest release of Windows ADK for Windows 10, version 1511:

“…….there is a serious issue with it that blocks the following Configuration Manager OS deployment scenarios:

  • From Software Center, launch a task sequence that uses a Windows PE v10.0.10586 boot image. When the computer restarts into Windows PE, it will fail when “Initializing hardware devices” with the error: “Windows PE initialization failed with error code 0x80220014.”

At this time, we do not recommend that Configuration Manager customers use the 1511 version of the Windows 10 ADK.”

Johan Arwidmark, a System Center and OSD expert had also posted a warning on November 15, 2015 on his blog post “Inside Windows 10 ADK Build 10586“.

Warning: Do NOT upgrade your ConfigMgr 2012 R2 SP1 or MDT 2013 Update 1 environments to this build yet. For ConfigMgr, even though it seems to fix the x64 UEFI / PXE and Powershell/.NET issue, which is great, the new ADK does break Computer Refresh scenarios (Bare metal works). The error code is 0x80220014. Research and discussions with the product teams in progress… MDT 2013 Update 1 yet to be validated, but error comments on twitter does not give me a warm and fuzzy feeling.”

——————————————————————————————————————–
Original post: November 20, 2015.

The Windows Assessment and Deployment Kit (ADK) for Windows 10, version 1511 is now available from Microsoft’s “Download Kits and Tools for Windows 10” site.

The Windows ADK now includes:

Follow me on Twitter (@Hoorge) and join Tech Konnect on Facebook to stay current on technology related matters.