Support articles

Find clear, step-by-step solutions to common WithSecure issues across installation, configuration, updates, and product performance.

Exposure Management agent-based scans fail in WSUS-only environments after upgrading to Elements Agent 26.4 showing XM Agent status as "Enabled with errors"

Issue:

After upgrading endpoints to WithSecure Elements Agent 26.4, Elements Exposure Management (XM) agent-based vulnerability scans may fail in environments where Windows devices are configured to use WSUS only and are not allowed to connect directly to Microsoft Update.
When the issue occurs, the XM Agent status in Elements Security Center is displayed as "Enabled with errors".
 

Resolution:

The issue occurs because the Elements Agent attempts to query Microsoft Update directly. In environments where direct access to Microsoft Update is blocked by network or organizational policy, this can prevent the XM agent-based scan from completing successfully.

If you check the local logfile on the affected system C:\ProgramData\F-Secure\NS\default\Log\Radar\wsradartools.log to confim the issue. If the issue is due to blocked access to Microsoft Update, the following error is visible in the log file:

2026-11-09 23:59:53.901 [0870.0006] *E: Radar.SystemCollector.Modes.Implementation.Windows.ReaMode: WithSecure Elements VM/XM System Collector execution has failed. Radar.SystemCollector.CustomExceptions.MissingUpdatesInfoCollectorException: Missing updates searching has failed. ---> System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x80072EFE
   at WUApiLib.IUpdateSearcher.Search(String criteria)
   at Radar.SystemCollector.Utilities.WuaLib.Implementation.UpdateSearcherWrapper.GetSelectedUpdates(String criteria)
   --- End of inner exception stack trace ---

 

This issue will be addressed in an upcoming update for Elements Agent.

WithSecure Changelogs can be accessed here: Changelogs - WithSecure™