Skip to main content
Start a Conversation

Unsolved

C

CoreITsupport

1 Rookie

 • 

6 Posts

39

May 14th, 2024 20:58

Precision 5560 ERROR: An error occurred (code 0x8004100e): Invalid namespace.

Hi,

We have around 14 laptops and so far, we have three devices documented that had this error. We had to rebuild WMI Repository, we think is related to freezing the machine multiple times, because usually occurs to people that don't shut down their machines often and just close lid. But this is happening in only this model, a lot of people do this, and they have no issue.

This is causing us a lot of issues machines that suddenly become non-compliant because BitLocker encryption is not detected (even when is encrypted). We found a way to fix it but I am concern of this happening and blocking users because the device cannot access company resources because of conditional access related with Bitlocker not being detected.

Adding some images of the errors (We already have a procedure to fix this issue but takes around 2 to 5 hours to be run, a lot of downtime for users, is happening once in a week now): 

KASPAWHALE.COM

1 Rookie

 • 

3 Posts

May 16th, 2024 20:08

Are all workstations on the most up to date bios?

CoreITsupport

1 Rookie

 • 

6 Posts

17-05-2024 17:29 PM

@KASPAWHALE.COM​ I am not sure if the machines had the latest BIOS when the error started, but certainly remember that installing the latest BIOS on a machine after the error didn't fix it. Once the error appear, you can either wipe the machine or run certain commands in order to fix it without having to fix it. I think at some point we used the DELL warranty to change the laptop, but we found out how to fix it in the third machine.

CoreITsupport

1 Rookie

 • 

6 Posts

17-05-2024 17:32 PM

@KASPAWHALE.COM​ We didn't know how to fix it the first two laptops, i think we used one warranty to replace that one, second one we wiped and the third one we found the fix.

CoreITsupport

1 Rookie

 • 

6 Posts

May 17th, 2024 17:46

This is the complete fix procedure; you can replicate it. In case you need to fix something with this model it might help you to troubleshoot. If you are trying to replicate it probably will fix it really fast in less than 1 hour, but machines that are actually used by user for a long period of time could be around 2-5 hours. I can create a support ticket with dell, we have warranty but don't require technical support for fixing it, and we will not give you our disk to test it, we have retention disk warranty. If you can make this, get to the developer team to fix it, i think you should save a lot of wasted time with technicians and shipping laptops. I attached the word document with how we do it.

CoreITsupport

1 Rookie

 • 

6 Posts

May 17th, 2024 17:53

Overview

Due to a corrupted repository on Windows Management Instrumentation (WMI) service, BitLocker fails to enable and encrypt the drive while it prompts an error Invalid Namespace.

Identifying BitLocker error

To identify the BitLocker error, open Command Prompt as Administrator then type the command manage-bde -status. The encryption status will throw an error code ERROR: An error occurred (code 0x8004100e): Invalid namespace.

The same error will be displayed when enabling BitLocker and checking Trusted Platform Module (TPM).

 

Rebuilding WMI Repository

 

Decrypt the disk before starting

This procedure will re-register the dlls and recompile .mofs in the wbem folder by re-registering the WMI Service.

  1. The first step to rebuild the WMI Repository is by stopping the WMI service. Open Command Prompt as administrator then type net stop winmgmt and select Y to continue the operation which would also stop the IP Helper service.

Next is to disable the WMI service by typing the command sc config winmgmt start=disabled.

 

Note: If you receive an Access Denied message when renaming the repository folder, check the WMI service if it is stopped by looking up services.msc then navigate to Windows Management Instrumentation. The service's status should be stopped and disabled, if this is not the case, re-run the net stop winmgmt command.

, net start winmgmt and net start iphlpsvc.



6. Last step is to encrypt C:Drive by following the encrypt procedure (Encrypt bitlocker XTS-AES 256)

(edited)

CoreITsupport

1 Rookie

 • 

6 Posts

May 17th, 2024 17:54

Looks like didn't allow me to post the images in the procedure that make it easier to understand.

View More

View All

No Events found!

Top