As it currently stands, if you have an environment with Windows-servers running with different default locales (languages), you need to create templates for all the different languages.

The idea of using the different perflib ID's fails as soon as you have features that might have different ID's between different versions of Windows, sometimes, for Hyper-V for example, I've seen the same version of Windows Server have different ID's  for the same Hyper-V check. Their names in English however has stayed the same for almost all versions of Windows.

Instead of hacking all the different servers Counter-key for "CurrentLanguage" or having one template per language, it would be FAR superior if the Agent could translate a check written for English to the servers CurrentLanguage.

I.e, "translate" the check from 

\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009\Counter

to 

\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\CurrentLanguage\Counter

And by doing so, work for those of us who works with Zabbix in Windows-environments would be so much simpler, and we could create far better templates for all Zabbix-users without having to care about the locale for the server!