Steps to reproduce:

1. Run query, for example "wmi.get["root\microsoft\windows\defender","select RealTimeProtectionEnabled from MSFT_MpComputerStatus"]" towards classic agent (in my case it was 4.4.10) No matter if you use zabbix_get or create an item. 
2. Run same query towards agent2 on same host (in my case it was version 6.0.13)
3. I guess you can use any other wmi query where answer is either True or False

Result:

from classic agent you will get "True", from agent2, you will get "true". Note the case...

Running query in host in powershell, gives you "True".

Running any other query, which returns for example "Disabled" or "N/A" or "Unknown" works without any issues, no modifications to returned value.

Expected:

I would expect query to return values with same case. This has no connection to windows version. In my case both 2016 and 2019 behaved same way. 

We discovered this during upgrading our environment from classic to agent2, when after agent change several triggers, which used "find(/host/item/.."like", "True")<>1", suddenly fired. Workaround was implemented, "like" replaced with "iregexp". But still, it would be nice to get answers from agent without any case changes.