WinMgmt could not initialize the core parts. This could be due to a badly installed version of WinMgmt, WinMgmt repository upgrade failure, insufficient disk space or insufficient memory.

Details
Product: Windows Operating System
Event ID: 28
Source: WinMgmt
Version: 5.2
Symbolic Name: WBEM_MC_WBEM_CORE_FAILURE
Message: WinMgmt could not initialize the core parts. This could be due to a badly installed version of WinMgmt, WinMgmt repository upgrade failure, insufficient disk space or insufficient memory.
   
Explanation

Windows Management Instrumentation (WMI) could not start. The startup process creates many Component Object Model (COM) objects, allocates memory, accesses registry keys, etc. A failure in any one of these steps can cause WMI not to start.

   
User Action

To determine why WMI could not start

  1. Open the log located at %windir%\system32\wbem\logs\wbemcore.log.
  2. In the log, look for messages containing the word “error” and examine these messages for information about failures in CoCreateInstance (when constructing a COM object), missing registry keys for COM objects, and so forth.

If the problem is with a COM component, reregister the DLLs.

To reregister the DLLs

  • At the command prompt, type:

for /f %s in (‘dir /b /s %windir%\system32\wbem\*.dll’) do regsvr32 /s %s

If the problem is insufficient memory, close some programs.

To close programs while WMI is running

  1. At the command prompt, type net stop winmgmt, and then press ENTER.
  2. Confirm that you want to stop WMI and any dependent services.
  3. Close any unnecessary programs.
  4. At the command prompt, type net start winmgmt, and then press ENTER.
  5. Restart any dependent service that you stopped in Step 2.

If the problem is insufficient hard disk space, free up some space on the system drive.

If you have tried the preceding solutions and WMI still does not start, some files in the %SystemRoot%\System32\Wbem\Repository folder might be corrupted. Correct this condition by restoring the WMI repository. Possible ways to restore the repository are:

  • If you have a good backup of the WMI repository, restore the repository from that backup. This is the preferred method.
  • Force WMI to rebuild the WMI repository from the original Managed Object Format (MOF) file. To see this procedure, go to the Microsoft Knowledge Base search page and search for a KB article by ID number 319101.

Note: If you force WMI to rebuild the repository, all static data or other changes to the repository that are not captured in the original MOF file will be lost. You should keep a copy of the corrupted file in case you need to either restore it or have Microsoft Product Support Services evaluate the corrupted files.

Related:

Leave a Reply