WMI not working on win10 - all related services broken

Anonymous
2025-02-11T12:37:41+00:00

Hello all,

1)

PS C:\Windows\System32> Get-WmiObject -Class Win32_Product

Get-WmiObject : Invalid class "Win32_Product"

At line:1 char:1

  • Get-WmiObject -Class Win32_Product
  • 
        + CategoryInfo          : InvalidType: (:) [Get-WmiObject], ManagementException 
    
        + FullyQualifiedErrorId : GetWMIManagementException,Microsoft.PowerShell.Commands.GetWmiObjectCommand
    
    

winmgmt /verifyrepository results in a return of WMI repository is consistent, so it doesn't appear to be corrupt.

  1. Another test
    my pc:
    Get-ComputerInfo -Property "*version"

WindowsCurrentVersion : 6.3

WindowsVersion : 2009

BiosBIOSVersion :

BiosEmbeddedControllerMajorVersion :

BiosEmbeddedControllerMinorVersion :

BiosSMBIOSBIOSVersion :

BiosSMBIOSMajorVersion :

BiosSMBIOSMinorVersion :

BiosSystemBiosMajorVersion :

BiosSystemBiosMinorVersion :

BiosVersion :

OsVersion :

OsCSDVersion :

OsServicePackMajorVersion :

OsServicePackMinorVersion :

coworker similar pc:
Get-ComputerInfo -Property "*version"                                                                

WindowsCurrentVersion              : 6.3
WindowsVersion                     : 2009
BiosBIOSVersion                    : {LENOVO - 1400, N30ET57W (1.40 ), Lenovo - 1400}
BiosEmbeddedControllerMajorVersion : 1
BiosEmbeddedControllerMinorVersion : 17
BiosSMBIOSBIOSVersion              : N30ET57W (1.40 )
BiosSMBIOSMajorVersion             : 3
BiosSMBIOSMinorVersion             : 2
BiosSystemBiosMajorVersion         : 1
BiosSystemBiosMinorVersion         : 40
BiosVersion                        : LENOVO - 1400
OsVersion                          : 10.0.19045
OsCSDVersion                       :
OsServicePackMajorVersion          : 0
OsServicePackMinorVersion          : 0

Issue seem similar to:
WMI registry issues that can't be resolved by resetting the WMI - Microsoft Community

Any inputs how to recover PC (without reinstalling windows)

Any inputs are welcome - thanks

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Anonymous
    2025-02-12T12:59:53+00:00

    Hello,

    According to your description, WMI is having problems on Windows 10, probably due to a corrupted repository or a service that doesn't start properly. Here are some workarounds you can try:

    1. Make sure the WMI service is started. Press Win + R, type services.msc and press enter to open the Service Manager. Find the Windows Management Instrumentation service in the list of services, make sure that its status is Running, and that the startup type is set to Automatic. If it's not running, right-click on the service and select "Start".
    2. Recompile the specific .mof file and see if the problem can be fixed.

    mofcomp C:\windows\system32\wbem\win32_Msi.mof

    1. If a large number of objects are lost and the missing classes cannot be queried, rebuild the WMI database by following the steps below:

    Note: Rebuilding the WMI library will only rebuild the WMI information registered by the system by default, and the software installed later may also register its own WMI, in this case, the function of these software may be affected, and generally the affected software can be reinstalled to solve the problem.

    Open the CMD window with administrator privileges:

    a. Disable and stop WMI services:

    sc.exe config winmgmt start= disabled

    net stop winmgmt

    b. Switch to the WBEM directory:

    cd %windir%\system32\wbem

    c. Rename to back up the original repository folder

    rename repository repository.old

    d. Change the WMI service back to automatic:

    sc.exe config winmgmt start= auto

    e. Run the following command to manually compile all default WMI .mof and .mfl files:

    cd %windir%\system32\wbem

    for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s

    1. Ensure that the current user has sufficient privileges to access the WMI object. Check your firewall settings to make sure that the firewall isn't blocking traffic from the WMI service.
    2. Open the command prompt with administrator privileges and enter the following command: sfc /scannow to scan and fix errors in system files.
    3. WMI relies on other services, such as the Event Log Service and the RPC Service. Make sure that these dependent services are started.

    I hope this information helps.

    Best regards,

    Jingjing Wu

    0 comments No comments