If you continue to encounter the issue after exhausting the steps above, consider opening an issue on the Open Group’s OMI GitHub repository with your omi.log and the output of omiserver –version . : win32operatingsystem result not found via omi new, OMI troubleshooting, Win32_OperatingSystem empty result, OMI new fails, WMI class not found OMI, fix OMI Windows query.
If you omit root/cimv2 , OMI may default to another namespace. Query a simpler, non-security class:
# Correct form (namespace class) omi new root/cimv2 Win32_OperatingSystem omi new --namespace root/cimv2 Win32_OperatingSystem win32operatingsystem result not found via omi new
: On the Windows target, run:
: On the Windows target, run as Administrator: If you continue to encounter the issue after
Then test from the client:
By systematically isolating the issue—testing local WMI, checking OMI logs, validating namespaces, and adjusting permissions—you can resolve the error and restore reliable cross-platform OS inventory. Once fixed, OMI becomes a powerful, lightweight alternative to full WinRM or SSH for managing heterogeneous environments. Query a simpler, non-security class: # Correct form
omi new root/cimv2 Win32_ComputerSystem If this does return a result, the problem is specific to Win32_OperatingSystem . If it also fails, the issue is broader (namespace, permissions, or WMI corruption). Log on to the Windows machine directly (or via RDP) and open PowerShell as Administrator :