Azure AD join error code 8018000a

Recently when attempting to perform an Azure AD Join with a Windows 10 v1511 computer I got the following error:

“Something went wrong. The device is already enrolled. You can contact your system administrator with the error code 8018000a.“

That didn’t make sense because I had recently disjoined the computer from Azure AD. I could find no reference to the object in the Azure portal either.

A Bingoogle search yielded only one relevant result… the ConfigMgr client is installed.

I knew this wasn’t the case.

So… read the error again. “the device is already enrolled”.

Checking Settings -> Accounts -> Work Access revealed the obvious: the computer was still being managed via OMA-DM (Intune), but associated with a different user.

Ok. Log off, then back on as the other administrator account.

Navigate back to Work Access and sure enough, the MDM enrollment was there. Un-enroll and bingo, Azure AD Join worked!

I recently had a nasty issue with my seriously awesome laptop (Lenovo ThinkPad P50 with a Samsung 950 Pro NVMe n.2 SSD). After a full shutdown (hold Shift when shutting down Windows 10) on the next power on I got a BitLocker recovery prompt.

That’s happened before, so I just powered off and back on like I’ve always done. However, this time I was greeted with a foreboding BCD error:

Error Message
Recovery.  Your PC/Device needs to be repaired.  The Boot Configuration Data files is missing some required information
File: BCD
Error code: 0xc000000d
You'll need to use recovery tools.  If you don't have any installation media (like a disc of USB device), contact your PC administrator or PC/Device manufacturer.
Press Esc for UEIF Firmware Settings

I pulled out my handy-dandy USB drive that just happened to still be configured as boot media for Windows 10 v1511 and used the F12 boot selection to boot to it. When prompted to install Windows, instead I typed Shift+F10 to get a command prompt.

I ran the following commands to confirm that the SSD did still exist.

DiskPart
List Drive
List Volume

All seemed fine there.

Time to rebuild the BCD… so I ran the following to scan for the instance of Windows

BootRec /ScanOS

Hmm… no Windows OS found. Ah, BitLocker is enabled. Of course BootRec can find anything. Let’s unlock the drive with the following commands:

Manage-BDE -status
Manage-BDE -unlock <drive letter> -RecoveryPassword <long number that I had saved on a non-encrypted drive on another device>

Great! Let’s try BootRec again:

BootRec /ScanOS
- found 1 instance
BootRec /FixMBR
BootRec /FixBoot
BootRec /RepairBCD

Time to see if it worked… reboot… success! Windows loaded right up. Awesome, I’m back in business.

I decided to suspend BitLocker on my Windows partition for now just to be safe. I’ll re-enable it after I’m sure everything is working.

Now let’s get back to work… booting up my ConfigMgr lab…

Doh! The VM guest failed to start because the hypervisor is not running.

Checking Services confirmed that the HV Host Service was stopped but still set to Automatic. Attempting to start the service threw another error:

Windows could not start the HV Host Service service on Local Computer. Error 31: A device attached to the system is not functioning.

That’s right… I destroyed the Hypervisor configuration in BCD. Let’s go fix that:

BCDedit
BCDedit /Set {current} hypervisorlaunchtype auto

P.S. PowerShell doesn’t like the ‘{current}’ syntax so I used a standard Administrative Command Prompt

BCD configuration before and after the change:

The home stretch…

Reboot again and Hyper-V is now running my VM lab! Whew. That’s wasn’t much fun!

Thanks to a few blogs and forum posts that helped out a ton.

I just noticed this today when I was building screen shots for a training class. If you right mouse click on the icons in the “waffle” App Launcher you can now resize them to Small/Medium/Wide and arrange your App Launcher to be more logical. Neat new feature.

You can now resize your App icons on the waffle App Launcher