WMI Win32_BitLockerEncryptionDetails crashing

Copper Contributor

Hi everyone,

I have a weird problem at a customer.

The following error occurs on every computer when trying to inventory this class.

Unknown error encountered processing an instance of class WMI Win32_BitLockerEncryptionDetails: 8004100E

The only article I've found is this one : Missing MBAM WMI classes on client computers – Dan Sonnenburg – Platform Manager @Organic Valley

Unfortunately, everything is correctly setup on the client computers and the configuration.mof file contains the needed information.

I don't understand what I can do about it. I've tried changing the configuration.mof file without any success.


This happens also on brand new mastered computers so it's a MECM problem.

Does anyone have any idea I could use to solve this please?

12 Replies
Thanks, I'll check right away and test this on a computer
It would be helpful for others if it will work?
Good luck Andrew

The part where they ask to disable the firewall cannot be an option for me as the VPN will stop if I do this...
I need to check this IIS core requirement as I'm installing all my servers the same way and maybe, at this customer, I missed something...
The mof recompile option can be quickly tested.
I'll let you know of course what this gives


EDIT : nothing on the IIS side / mof recompile and WBem rebuilding didn't change the problem.

Still looking for a solution if you have an idea

When you say everything correct on the client, does that mean that you have viewed the WMI class and see data?

@Garth Jones Here's what I mean:

- WMI class is obviously loaded on the computer but there's no data





- InventoryAgent.log is throwing this error


- Configuration.mof (rename .docx) on the MECM server is OK (2103)

I don't know where to look elsewhere at this stage.

Thanks for your help

best response confirmed by Aventador06 (Copper Contributor)
Did you look at the underlaying MBAM class for inventory? Have you check to make sure that the MBAM client has been installed?
Ho my god.....
How could I have missed this????
MBAM Client wasn't deployed :(
I completely forgot it in the process.
Thanks Garth for your guidance.

@Garth Jones 

Hey Garth, I'm facing the same issue with my HINV, but for this client, MBAM isn't used. So it can't be missing right?


This shows up no matter the BitLocker status.

I noticed that someone had created a BitLocker Management policy to test, without properly configuring all the other requirements. So it was not working... Since then V_GS_BitlockerEncryptionDetails only has 2 rows (the 2 test devices with the BitLocker Management policy) Which seem related to MBAM with what is available in the details.


I've removed the policy and did a BitLocker rollout with Intune(co-managed).

The funny thing is v_GS_ENCRYPTABLE_VOLUME does work properly, so I kind of have an idea on who's encrypted because of that. The number of reports in that table makes sense with the actual rollout of BitLocker. 


BitLocker-related classes are enabled in the Default Client Settings. Nothing custom in the configuration.mof.


that was all done with MECM 2010, but currently at 2103. I begin to wonder if because the MBAM policy was created, it kind of screwed up the standard BitLocker inventory, or simply a bug when MBAM support was added to MECM.


any other ideas on what could be attempted to fix this inventory issue?




So there Error within the inventory agent.log is saying that the WMI class does not exist or their are problem accessing it. So I would test it with wmi explorer or wbemtest.

This might mean that you need to have a MBAM policy to install the agent and therefore collect the data via mbam.

This is where I would start.

@Garth Jones Thanks, I'll try to install the MBAM agent to see the result without any management since it's offloaded to Intune already. I just wanted the extra reporting from ConfigMgr.


Seems the integration of MBAM broke something that was working for sure before...

The class is indeed empty, no matter the status of BitLocker, so even a manual query fails. But the class for EncryptableVolume does work fine. 

1 best response

Accepted Solutions
best response confirmed by Aventador06 (Copper Contributor)
Did you look at the underlaying MBAM class for inventory? Have you check to make sure that the MBAM client has been installed?

View solution in original post