Fix Unable to Connect to WMI Error 0X8004100E

Not so long ago Microsoft disabled SQL Server Management Studio from installing SQL Server. This makes it possible to release new versions of SSMS faster. SQL Server 2016 template in Azure comes with this new version of SSMS. Many other service programs are also included when installing SSMS, including SQL Server Configuration Manager. This leads to the installation of two versions of SQL Configuration Manager on one computer. Each uses files in a directory depending on the version number of SQL Server they support. Based on reading various other troubleshooting blog posts, I assume that the .mof file needed for version 2017 has not been compiled and therefore will not work properly.

These several versions can confuse administrators. Personally, it made me work differently. I usually click the search button on the toolbar, and then type in the name of the application I want to use. In this case I need to be very careful because I may accidentally run the wrong version. This is not a success or a break, but I need to know about it now that I am working on this server.

So, here it is. The answer was simple. In this case it was a user error. Although I like that nothing special was involved in its repair, I also feel a bit stupid that I didn’t have it right away. Simply running the version corresponding to my installation will solve the problem.

Here are a few options that you can use to try and repair WMI on a client computer. After each step, reboot the client computer and check if the problem is solved by rescanning the computer. One way to re-scan is to click the “Assets” link at the top of the web console, check the box in front of the asset and click the “Re-scan” button on the left. Wait for the date of the “last scan” or “last attempt” specified on the “Summary” tab of your computer’s web site to update it to indicate that a new scan attempt has been made.

Disable the Firewall

Enter a command line with elevated privileges:

netsh firewall set service remoteadmin enable

Delete the Repository Folder

Use Windows Explorer to delete all the files in the %SystemRoot%\System32\Wbem\Repository folder and restart your computer.

The Windows management toolkit service launches and the files are restored

Stop WMI Service

Net Stop winmgmt
RD /S /Q %systemroot%\system32\wbem\Repository
Net Start winmgmt

cd /d %windir%\system32\wbem
for %i in (.dll) do RegSvr32 -s %i for %i in (.exe) do %i /RegServer)

Start> Run> services.msc> Windows Management Tools Service> right-click it and click Stop.

Use the Elevated Command Prompt

Execute the following commands from the command line with elevated privileges on the client computer, which causes the WMI corruption error. This is another way to reset the WMI repository as it was the first time you installed the operating system.

  • Winmgmt.exe / offline host
  • Winmgmt.exe / resetrepository

Use the SFC Scannow command

Perform the following command from the command line with elevated privileges on the client computer, which creates WMI corruption errors. It checks the integrity of Windows operating system files and tries to fix all found errors.

sfc / scannow

If nothing helps, reinstall the Windows operating system on the client computer where WMI corruption errors occurred.

Fix infections and eliminate malicious programs on your computer

How do you judge whether your system is infected with malware and viruses?

On the one hand, some applications can behave badly.

You can also see the appearance of 0x8004100e.

Infections and malicious programs are the result:

  • Access the Internet with open or unencrypted public Wi-Fi connections
  • Downloading applications from unknown and untrustworthy sources
  • Deliberately introduce viruses into home and work networks

Fortunately, its effects can be contained.

  • Enter the safe mode by pressing the F8 key a few times when rebooting the device. In the Advanced Boot Options menu, select Safe Mode with Networking.
  • Make a backup of all data on your device in a safe place. Preferably, it is a storage device that is not connected to your existing network.
  • Leave the program files unchanged. This is where infection usually spreads and there is a potential risk.
  • Perform a full system scan or a scan on demand. If you have already installed an antivirus or malware protection program, let it do all the hard work.
  • Once the process is complete, restart your computer.
  • Finally, change all your passwords and update your drivers and operating system.