(Not exactly an answer to the question, but rather to your described situation. Could be useful for others facing the same issue):
What ZABBIX does out of the box with the standard Windows OS templates, is to create items and triggers (by auto-discovery) for all windows services that are set to start Automatically, and then trigger problems when they are not running.
So, this is a case of Microsoft doing semantically dubious things with some special Windows services. (The same happens on Windows 2022 Server (non-core), by the way.
What you typically do with these kinds of intermittently-running services, such as StateRepositoryService, edgeupdate, cbdhsvc_.+ is to include them in the regex of services to exclude from auto-discovery.
In the template, in the Discovery rule called Windows services discovery
, there are some Filters. One of them being:
{#SERVICE.NAME}
does not match {$SERVICE.NAME.NOT_MATCHES}
.
The former being the discovered service macro, and the latter being a "regular" host macro defined on the template itself.
So, to exclude from monitoring of these Auto-start services that are not continuously running, include them in the {$SERVICE.NAME.NOT_MATCHES}
macro (found on the template -> Macros list.