"BitLocker couldn't contact the Domain" error during activation (Non-Domain system)


dcan

New member
Local time
4:11 PM
Posts
1
OS
Windows 11
I get the error in the title when trying to activate BitLocker on my non-domain joined, Windows 11 Pro workstation (fully patched). I've researched the issue and most threads suggest changing Group Policy; however, both "Store Bitlocker Recovery to Active Directory Domain Services" and "Configure use of Passwords for Removable Data Drives" policies are disabled. The workstation should meet BitLocker system requirements and has TPM 2.0. It should be noted that the system has been hardened, but I don't see any other policies in BitLocker Drive Encryption that would cause it to reach out to a domain controller. Any help would be greatly appreciated.

Edit: Changing the "Choose how Bitlocker-protected operating system drives can be recovered" policy fixed the initial issue. It was trying to store Bitlocker recovery info to an AD. However, now the error message reads "There are conflicting settings for recovery options...When a recovery password is required backup to active directory should be turned on or the user should be required to save the recovery password." I assume this is a specific policy that needs disabling or enabling.
 
Windows Build/Version
Windows 11 Pro
Last edited:

My Computer

System One

  • OS
    Windows 11

My Computers

System One System Two

  • OS
    Windows 11 Pro 23H2 Build: 22631.3374
    Computer type
    PC/Desktop
    Manufacturer/Model
    Sin-built
    CPU
    Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz (4th Gen?)
    Motherboard
    ASUS ROG Maximus VI Formula
    Memory
    32.0 GB of I forget and the box is in storage.
    Graphics Card(s)
    Gigabyte nVidia GeForce GTX 1660 Super OC 6GB
    Sound Card
    Onboard
    Monitor(s) Displays
    4 x LG 23MP75 1 x 24" LG M38H 1 x 32" LF6300 TV Monitor 1 x Wacom Pro 22" Tablet
    Screen Resolution
    All over the place
    Hard Drives
    2 x WD something Something 8TB HDD's / 2 x WD something Something 4TB HDD's / 1 x EVO 1TB SSD / 2 x QVO 1TB SSD's / 1 x EVO 250 GB SSD / 2 x QVO 1TB (External Hub) / 1 x EVO 1TB (Portable Backup Case)
    PSU
    Silverstone 1500
    Case
    NZXT Full Tower
    Cooling
    Noctua NH-D15 Elite Class Dual Tower CPU Cooler / 6 x EziDIY 120mm / 2 x Corsair 140mm somethings / 1 x 140mm Thermaltake something / 2 x 200mm Corsair.
    Keyboard
    Corsair K95 / Logitech diNovo Edge Wireless
    Mouse
    Logitech G402 / G502 / Mx Masters / MX Air Cordless
    Internet Speed
    100/40Mbps
    Browser
    All sorts
    Antivirus
    Kaspersky Premium
    Other Info
    I’m on a horse.
  • Operating System
    Windows 11 Pro 22621.2215
    Computer type
    Laptop
    Manufacturer/Model
    LENOVO Yoga 7i EVO OLED 14" Touchscreen i5 12 Core 16GB/512GB
    CPU
    Intel Core 12th Gen i5-1240P Processor (1.7 - 4.4GHz)
    Memory
    16GB LPDDR5 RAM
    Graphics card(s)
    Graphics processor is an Intel Iris Xe
    Sound Card
    optimized with Dolby Atmos®
    Screen Resolution
    QHD 2880 x 1800 OLED
    Hard Drives
    M.2 512GB
    Other Info
    …still on a horse.
I had this same issue, are you using a second hand device by any chance? What the issue was for me was that despite being factory reset, at some point in the devices lifecycle it was enrolled in an MDM solution, in this case Intune + Windows Autopilot. Even though the device was deleted from Intune, the sysadmin at the company who previously owned the device did not disable it on windows autopilot. Reach out to whoever you purchased it from with the serial number and ask them to remove it from their autopilot enrollment list
 

My Computer

System One

  • OS
    Windows 10
Back
Top Bottom