Win32operatingsystem Result Not Found Via Omi New May 2026
The error indicates that OMI’s internal class provider lookup failed. Possible reasons include:
Sometimes explicitly including the namespace helps:
omi new root/cimv2:Win32_OperatingSystem
The "Result Not Found" error is not a bug in OMI; it is an issue of missing data context. OMI on Linux is an empty shell until providers are installed. Unlike Windows, which has Win32 classes baked in, Linux requires you to explicitly map system data to the CIM schema by installing the appropriate OS Provider package.
The error "Win32_OperatingSystem results not found via OMI" typically indicates a communication or permission failure between your management platform (such as FortiSIEM) and the target Windows host. Primary Troubleshooting Steps win32operatingsystem result not found via omi new
Authentication Method: Switching from NTLM to Kerberos authentication often resolves this specific OMI result error.
User Permissions: Ensure the credentials used belong to the local Administrators group on the target machine. For Domain Controllers, the user should be in the Domain Admins group.
Port Requirements: Verify that the following ports are open between the collector and the host: TCP 135 (RPC/DCOM) TCP 5985 (HTTP WinRM) or 5986 (HTTPS WinRM) UDP 137 (NetBIOS) Verify with CLI The error indicates that OMI’s internal class provider
You can test the connection directly from your collector’s command line to see if it’s a global connectivity issue or a specific tool failure:
/opt/phoenix/bin/omic -s /opt/phoenix/config/smb.conf -U DOMAIN/USER%PASSWORD // Use code with caution. Copied to clipboard
If this command fails with the same error, the issue is likely rooted in WinRM configuration or WMI health on the Windows machine. Windows Host Configuration The "Result Not Found" error is not a
WinRM Listener: Ensure WinRM is listening on all interfaces. You can force this via Group Policy (GPO) if the collector and host are in the same VLAN but still failing.
WMI Service Health: The Win32_OperatingSystem class relies on a healthy WMI repository. You can verify consistency by running winmgmt /verifyrepository in an administrative Command Prompt on the Windows host.
Restart Services: Sometimes simply restarting the Windows Management Instrumentation service and installing pending Windows Updates can resolve the "result not found" error. FortiSIEM AIO - Collector questions and WMI/OMI issues
On the Windows target, verify that the OMI service is running and the WMI bridge is enabled:
sc query omi
Check OMI logs at %ProgramData%\omi\var\log\omi.log for errors like:
Provider [WMI Bridge] failed to load class Win32_OperatingSystem
