The error win32operatingsystem result not found via omi new means that the OMI client successfully connected to the remote host’s OMI endpoint, but the Win32_OperatingSystem class either:
—often specifically noted as "NEW" in logs—it usually indicates a breakdown in communication between an Open Management Infrastructure (OMI) collector (like FortiSIEM or SCOM) and the target Windows machine.
Isolate the issue from the platform user interface by running a direct check from your collector's command line interface using the backend binary: win32operatingsystem result not found via omi new
Open command prompt (admin) and run: winmgmt /verifyrepository
You can manually test the connection from your collector (e.g., FortiSIEM Supervisor) using the omic tool to bypass the GUI and see raw error messages: The error win32operatingsystem result not found via omi
Here is the "story" of how this error typically unfolds and how it is resolved. 1. The Setup: The "First Discovery" Attempt
omi new root/cimv2 Win32_OperatingSystem --verbose The Setup: The "First Discovery" Attempt omi new
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.
cd %windir%\system32\wbem regsvr32 cimwin32.dll mofcomp cimwin32.mof mofcomp cimwin32.mfl wmiprvse /regserver Use code with caution.
group on the target host or have explicit "Remote Enable" permissions for the Root\CIMV2 namespace. WMI Repository Corruption
If your network and accounts are fine but the manual test still fails, the WMI data inside Windows itself might be corrupted.