Skip to main content

Recovery of WMI: Initialization failure error

WMI: Initialization failure error

Question | Does anyone know what could cause WMI: Initialization failure error to start happening:

| WMI: Initialization failure
| Login failed to machine "myserver".
| I noticed that recently that my backups started failing becuase of some| WMI errors, so I tried to connect to these problems servers via WMI CIM| Studio and this is the error that I get. I'm pretty sure whatever is| causing this error is also causing the error in the backups, and these| servers were working properly for quite a while (about two years), I| don't think aything has changed recently, and i know that the WMI| service is running on the servers that are triggering this error.

Solution 1

  • Press Winkey + R or start run & type services.msc & press enter
  • Press Winkey + R or start run & type services.msc & press enter
  • locate "Windows Management Instrumentation" service & stop it
  • locate "Windows Management Instrumentation" service & stop it
  • open command prompt (Press Winkey + R or start run & type cmd & press enter)
  • open command prompt (Press Winkey + R or start run & type cmd & press enter)
  • execute commands below
  • execute commands below
  • cd /d %windir%\system32\wbem 
  • cd /d %windir%\system32\wbem 
  • rd Rep_bak /s /q
  • rd Rep_bak /s /q
  • rename Repository Rep_bak
  • rename Repository Rep_bak
  • for %i in (*.dll) do RegSvr32 -s %i
  • for %i in (*.dll) do RegSvr32 -s %i
  • for %i in (*.exe) do call :FixSrv %i
  • for %i in (*.exe) do call :FixSrv %i
  • for %i in (*.mof,*.mfl) do Mofcomp %i
  • for %i in (*.mof,*.mfl) do Mofcomp %i
  • exit
  • exit
  • Press Winkey + R or start run & type services.msc & press enter
  • Press Winkey + R or start run & type services.msc & press enter
  • locate "Windows Management Instrumentation" service & start it
  • locate "Windows Management Instrumentation" service & start it
Now see if this correctsyour problem.

Solution 2

Create a FIXWMI.CMD batch file from the below script and run it and see if this correctsyour problem.
FIXWMI.CMD
------------------------
@echo on cd /d c:\temp
if not exist %windir%\system32\wbem goto TryInstall cd /d %windir%\system32\wbem net stop winmgmt winmgmt /kill if exist Rep_bak rd Rep_bak /s /q rename Repository Rep_bak for %%i in (*.dll) do RegSvr32 -s %%i for %%i in (*.exe) do call :FixSrv %%i for %%i in (*.mof,*.mfl) do Mofcomp %%i net start winmgmt goto End :FixSrv if /I (%1) == (wbemcntl.exe) goto SkipSrv if /I (%1) == (wbemtest.exe) goto SkipSrv if /I (%1) == (mofcomp.exe) goto SkipSrv %1 /RegServer :SkipSrv goto End :TryInstall if not exist wmicore.exe goto End wmicore /s net start winmgmt :End

You might also like:



For data loss on iPhone/iPad/iPod Touch , iFoneMate iPhone data recovery software can be the useful tool to recover deleted/lost data from iPhone 6s/6/6plus/5s/5c/5/4s/4/3GS efficiently through three simple steps Scan-Preview-Recovery after three clicks.

Comments

Popular posts from this blog

INSTALL CISCO VPN CLIENT ON WINDOWS 10 (32 & 64 BIT). FIX REASON 442

This article shows how correctly install Cisco VPN Client (32 & 64 bit) on Windows 10 (32 & 64 bit) using simple steps, overcome the ‘ This app can’t run on this PC ’ installation error , plus fix the Reason 442: Failed to enable Virtual Adapter error message . The article applies to New Windows 10 installations or Upgrades from earlier Windows versions and all versions before or after Windows 10 build 1511 .  To simplify the article, we’ve broken it into the following two sections: How to Install Cisco VPN client on Windows 10 (clean installation or upgrade from previous Windows), including Windows 10 build prior or after build 1511 . How to Fix Reason 442: Failed to enable Virtual Adapter on Windows 10 Figure 1. The Cisco VPN Client Reason 442: Failed to enable Virtual Adapter error on Windows 10 HOW TO INSTALL CISCO VPN CLIENT ON WINDOWS 10 (NEW INSTALLATIONS OR O/S UPGRADES) The instructions below are for new or clean Windows 10 inst...

How to Disable SSL for Webmin

Webmin is a Web application that enables administrators to manage Linux servers. Webmin runs on a Web server at port 10000. Miniserv is the name of the Web server application that handles the Webmin Web application. By default, Miniserv uses SSL. However, you can disable SSL for Webmin Miniserv by editing the configuration file for the Web application. With SSL disabled, you can access the Webmin application over a standard HTTP connection. Step 1 Open a terminal window on the Linux server. You can also SSH into the server if you do not have physical access to the machine. Step 2 Type the following command at the command prompt and press the “Enter” key: nano /etc/webmin/miniserv.conf This command opens the Miniserv configuration file in the Nano text editor.

Error 651: How to Fix it in Windows 7/8

If you are a windows user then it is possible that you have Face Error 651 Anytime. There are many windows user who get affected by this error code 651 while working online. If you are one of those windows user, then keep reading this article and carefully read out the following Detailed solutions which I have gathered after researching various websites, articles, forums etc. When using Windows 7 built-in PPPoE wizard with a modem working in bridge mode, it fails and error code 651 appears. The similar problem happens on Windows Vista or previous versions as well. For example, Error code 678 on Windows XP is equivalent to error code 651 on Windows 7. Error code 651 usually occurs when user tries to connect it’s broadband in windows 7 operating system. It shows a message that Your modem (or other connecting devices) has reported an error and Usually the message will be “Connection failed with error 651” .Fix Error 651 In such cases user tries to resta...