Re-register the OMI WMI bridge provider:
cd %ProgramFiles%\omi\bin
omireg.exe --register-wmi-bridge
net stop omi
net start omi
You can check what classes are actually registered in the OMI repository to confirm if the provider is active.
When working with OMI (Open Management Infrastructure) — the open-source alternative to Windows Management Instrumentation (WMI) often used in cross-platform environments like Linux-based System Center agents, Azure monitoring, or certain UNIX/Linux to Windows management bridges — you may encounter a puzzling error: win32operatingsystem result not found via omi new
"Win32_OperatingSystem result not found via OMI new"
This error typically appears when an OMI client or command attempts to query the Win32_OperatingSystem class using a method like omi new (which initializes a new instance of an OMI session or operation) but fails to locate the expected WMI class on the target system. You can check what classes are actually registered
Below, we dissect what this error means, common root causes, and how to fix it.
omi new --namespace root/cimv2 Win32_OperatingSystem "Win32_OperatingSystem result not found via OMI new"
If you omit root/cimv2, OMI may default to another namespace.