0x8004100f Provider Load Failure (WMI)



This post is a little more technical than most, but I felt it important to post this because I could not find anything online to help me fix it. I would get this error when trying to pull up instances of the Win32_NetworkAdapter. To trace the problem I used this notification query string in WBEMTEST and asynchronously:

'Select * From MSFT_WmiSelfEvent'

Once run, I then repeated the error, and found an error occurred from a provider called BRCMGroup.

In short, all I had to do was uninstall a Broadcom provided CIM from add/remove programs (Broadcom Drivers and Management Pack, I removed CIM only). I hope this will help anyone out there dreading the idea of rebuilding their WMI repository.

UPDATE: My colleague has a more in-depth explanation of how to address this type of problem. Click here to read the entry related to my post.

Comments

Anonymous said…
Many thanks!

Had the same problem on a Dell notebook
and solved it in this way!
(Had been searching for a resolution a long time)

David
October 23, 2008 at 4:49 AM
James said…
Brilliant! Just about to give up and re-install XP.

This problem actually gave me an 0x80041013 error, and I managed to force the 0x8004100f error somehow by accident about 15 minutes ago which led me here.

I also have been searching for a long time, and I also have a Dell notebook! Hmmmm?!?!

Thanks again
James
June 11, 2009 at 12:27 PM
Eamonn said…
Thanks - just had this exact issue with a Toshiba laptop featuring those notorious Broadcom management programs.

Eamonn
January 19, 2012 at 1:47 PM
Anonymous said…
You saved my life with this one. Had a dying windows 2000 machine that this fixed the issue to get it virtualized.

Rob
July 17, 2012 at 3:29 PM
Anonymous said…
Fantastic. Thanks for this :). Solution fixed it right away.
December 14, 2012 at 11:32 AM
Post a Comment

Popular posts from this blog

NSX-T: Release associated invalid node ID from certificate

Image
Summary: Basically had an expiring certificate registered in NSX-T that was associated to a node_id that is no longer valid.  Long story short, there wasn't anything obvious in API to delete or disassociate a certificate from a node_id for 3.2.2.  Not sure how things got in this state, but annotating for future reference.  This may change in future revisions, so always check API for latest. Details: Effectively had a stale node associated w/ a certificate that was expiring.  Could not delete certificate until that node was disassociated from the certificate. To get certificate details and associated node_id's, you can use the following curl call (UI works too): curl -k -X GET -H "Content-Type: application/json" -u admin https://<manager ip>/api/v1/trust-management/certificates/<cert UUID> Above will return something like this: Below must be run from one of the manager nodes via elevation to root: ONLY RUN THIS IF YOU ARE ABSOLUTELY SURE OF WHAT YOU ARE DO...
Read more

NSX-T: vCenter and NSX-T Inventory out of Sync (Hosts in vSphere not showing up in NSX-T)

Image
Summary: NSX-T loses synch w/ vCenter inventory, but statuses don't appear to show an issue.  Basically, you add a host to a vCenter cluster, NSX-T bits should start to automatically installing on new host.  Assuming you've created a Transport Node Profile and associated w/ the cluster.  The problem is that NSX-T doesn't see the new host and its link to the compute manager (vCenter) looks fine. Looks fine, Y U NO WORK!? So what's going on here?  This appears to affect NSX-T 2.5 and 2.5.1.  Cause is unknown. Workaround: Restart the cm-inventory service on each NSX-T mgmt/controller node using API or CLI. Details: If you were to query the status of the cm-inventory via API or CLI, you could query all 3 manager/controller nodes and get a status of running.  Even if the primary node associated w/ the VIP, if configured, is not necessarily in charge of inventory.  So you could restart the cm-inventory service till you are blue in the face ...
Read more

MacOS: AnyConnect VPN client was unable to successfully verify the IP forwarding table modifications.

Image
The VPN client was unable to successfully verify the IP forwarding table modification.  A VPN connection will not be established. Summary: I started running into issue utilizing Cisco AnyConnect on my Mac basically complaining about not able to overwrite IP forwarding tables.  This was on 4.6.x.  Since my VPN endpoints were not providing me w/ an updated client and w/ no access to Cisco Anyconnect downloads, my only option was to try openconnect.  It was totally worth it, here is why and how to set it up. PreReqs: Homebrew Installing OpenConnect: Launch MacOS Terminal brew install openconnect Getting VPN IP's/DNS Endpoints from AnyConnect: The information is typically located in your profile xml files located here: /opt/cisco/anyconnect/profile/somethingsomething.xml In the xml file, you are looking for "<HostAddress>typicallyaDNSName.com</HostAddress>" entry.  These are your VPN endpoints that you would need to pass to openconnec...
Read more