Forum Discussion

Aventador06's avatar
Aventador06
Copper Contributor
Jul 12, 2021
Solved

WMI Win32_BitLockerEncryptionDetails crashing

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 W...
cm current branch
Garth Jones's avatar
Garth Jones
MVP
Jul 13, 2021
Did you look at the underlaying MBAM class for inventory? Have you check to make sure that the MBAM client has been installed?
jlefebvreGlobensky's avatar
jlefebvreGlobensky
Copper Contributor
Oct 27, 2021

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?

Thanks!

Jonathan

 

Resources