Member Avatar for RWhunt99

Had some computer problems, replaced M/B and processor and had another problem probably related to the M/B problem (CPU fan died, then Processor died)where I did a wndows repair and seemed to fix the problem. Now I hooked it into the network, but now while it can see everyone on the domain, no one can see it. Logs in fine. I did a network diagnosis and got several things that displayed the same message > unable to find WMI service '\\.\root\cimv2'
Should I do another windows repair or should I be able to install the WMI service by itself?
it's an intel Pentium D with WinXP sp2

  • 2 Contributors
  • 2 Replies
  • 201 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by RWhunt99

Dani AI

Generated

As described, the network diagnostics failure reporting "unable to find WMI service '\.\root\cimv2'" points to broken or stopped WMI rather than a general network/AD visibility issue. was right to start at Services, but the core checks are: confirm the Windows Management Instrumentation service (winmgmt) and Remote Procedure Call (RPC) are running, and verify the machine’s firewall/port rules aren’t blocking RPC/DCOM (WMI uses RPC/DCOM — initial contact on TCP 135 and additional dynamic RPC ports). (learn.microsoft.com)

Quick diagnostic steps (in order): check Services.msc for Windows Management Instrumentation and RPC; scan System and Application logs in Event Viewer for winmgmt errors; run WBEMTEST (connect to root\cimv2) to see whether local namespace access succeeds; and run a repository check with winmgmt /verifyrepository where available. On older XP systems, Microsoft recommends using WMIDiag or manual checks because some newer winmgmt switches aren’t present. (learn.microsoft.com)

If the repository is inconsistent, follow a staged repair rather than immediately reinstalling Windows. For Vista+ the non‑destructive commands are winmgmt /salvagerepository then winmgmt /resetrepository if needed; for XP the supported approach is a manual rebuild: stop WMI, rename the %windir%\system32\wbem\Repository folder, re-register WMI binaries and recompile .mof/.mfl files, then restart WMI and reboot. Rebuilding can remove third‑party WMI classes, so attempt salvage/re‑register first and keep backups. ()

Minimal commands to try first (run from an elevated command prompt on the target machine):

winmgmt /verifyrepository
winmgmt /salvagerepository

If those report failure on XP, follow the manual rebuild sequence documented by Microsoft (stop winmgmt, rename Repository, re-register providers and run mofcomp on .mof/.mfl files, then reboot). If problems persist after these steps, a Windows Repair or restore from backup is the last resort; expect that some third‑party software may need reinstallation after a repository reset. ()

Recommended Answers

All 2 Replies

Member Avatar for fuzzyduq

go: settings> control panel> administrative tools > services - this will open up a list of services available under the xp op sys and also shows the service status. scroll down to near bottom of list. look for wmi performance adaptor; check status. if not started then start service - highlight service, description of service and start/stop/restart options are displayed under left side of blue services (local) banner, click on start. make sure startup type is set to automatic - double click on service, change startup type to automatic, apply, exit. hope this helps

Member Avatar for RWhunt99

Thanks, I'll try that, kind of concerned because the firewall seems to need that too.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.