Hi,
Your configuration looks fine. To identify the exact issue and troubleshoot further, please check the agent’s ossec.log file. You can find it here:
C:\Program Files (x86)\ossec-agent\ossec.logMake sure the agent is active and running.
When you review the log, you may see an error saying that the file monitoring limit of 100000 has been reached. This happens because the File Integrity Monitoring (FIM) module can only monitor up to 100000 files by default. If you try to monitor an entire drive, the number of files becomes much higher, which can impact performance.
If this is the case, you need to either extend or disable the file limit using the <file_limit> option:https://documentation.wazuh.com/current/user-manual/reference/ossec-conf/syscheck.html#file-limit
<!-- Maximum number of files to be monitored -->Note: The value for <entries> can range from 1 to 2147483647.
If you see an error like: file limit has been reached (200)Then check this file:
C:\Program Files (x86)\ossec-agent\internal_options.conf
Look for:
# Logcollector - Maximum number of files to be monitored [1..100000]
logcollector.max_files=1000
If the value on your system is 200, that is what is limiting the agent.
You can override it by creating or editing:
Add the correct value there, then restart the agent.
If there is no error related to file limits, please share the ossec.log from the Windows agent and the agent version so I can review it.
Also, while monitoring an entire drive is technically possible, it is better to monitor only specific folders instead of watching the whole C: drive in real-time or who-data mode, as this can consume significant resources.
Let me know once you check the log.