Could not get Windows Performance Counters since Metricbeats 7.3.0

I use Metricbeats to send Windows Perfomance Counters, like processor time and private bytes to elasticsearch. Until Metricbeats version 7.2.0 it runs well, but the same configuration doesn't run in version 7.3.0 and 7.3.1. If I run "metricbeats.exe test modules", I get an error that the performance counter does not exist. But it exists and the Metricbeats 7.2.0 can access this performance counter.
The error message, that I get from "metricbeats.exe test modules" is: metricbeat.exe test modules
Error getting metricbeat modules: module initialization error: 1 error: initialization of reader failed: failed to expand counter (query="\Process(bbGateService)% Processor Time"): Das angegebene Objekt wurde nicht auf dem Computer gefunden.

The content of the windows.yml file:

- module: windows
  metricsets: ["perfmon"]
  period: 1s
  perfmon.counters:
# CPU
    - instance_label: "ECM_Gate2"
      instance_name: "gate2"
      measurement_label: "ecm.gate2.gateservice.cpu"
      query: '\Process(bbGateService)\% Processor Time'
      format: "float"
# Memory
    - instance_label: "ECM_Gate2"
      instance_name: "gate2"
      measurement_label: "ecm.gate2.gateservice.memory"
      query: '\Process(bbGateService)\Private Bytes'
      format: "float"

hi @jbeyer ,

The configuration in your windows.yml file seems to be correct. Can you provide us with more details on the operating system version, processor type in order to test this scenario out?
Also, it is strange that the query value in the error is missing a backslash \ before the percent sign. Might not be related.
: initialization of reader failed: failed to expand counter (query="\Process(bbGateService)% Processor Time")

The missing Bakslash was eliminated from the website, in original the error message includes the Bakslash before the % sign.
Here are the details of the machine: It is a bare metal machine with Windows Server 2016 (Version 1607 (Build 14393.3181)) with 2x Intel Xeon CPU E5-2620 2.00 GHz and 32 GB RAM.
On another machine with the same OS- version and 2x Intel Xeon CPU E5-2620 v2 2.10 GHz + 64 GB RAM, there is the same result.

The problem are existing also in Metricbeat version 7.3.2.