Windows service in Paused state cannot be managed

When a service is in the Paused state; it's 'ensure' property cannot be managed by Puppet

Note that for our own services that use nssm; nssm has a characteristic that it uses the "Paused" service state for a service that has reached a fault state (see https://nssm.cc/usage )

To reproduce:

• Install puppet-agent
• Ensure pxp-agent service is stopped in services.msc
• Ensure the ProgramData/PuppetLabs/pxp-agent/etc/pxp-agent.conf file is renamed or deleted
• Run puppet resource service pxp-agent ensure=running

The service will now be in the paused state.
Attempting puppet resource service pxp-agent ensure=stopped will echo back ensure=stopped , but services.msc will show the service as still paused.
Attempting puppet resource service pxp-agent ensure=running will return an error:

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Puppet>puppet resource serv

ice pxp-agent ensure=running

Error: Cannot start pxp-agent, error was: Execution of 'C:/Windows/system32/net.

exe start pxp-agent' returned 2: The requested service has already been started.

More help is available by typing NET HELPMSG 2182.

Wrapped exception:

Execution of 'C:/Windows/system32/net.exe start pxp-agent' returned 2: The reque

sted service has already been started.

More help is available by typing NET HELPMSG 2182.

Error: /Service[pxp-agent]/ensure: change from stopped to running failed: Cannot

 start pxp-agent, error was: Execution of 'C:/Windows/system32/net.exe start pxp

-agent' returned 2: The requested service has already been started.

More help is available by typing NET HELPMSG 2182.

Outside of Puppet, the service can be stopped by simply using the Stop option in services.msc

Expected behaviour:

• The "Paused" state should be understood by Puppet for a Windows service resource. Or at least; Puppet should actually stop a service in the "Paused" state when ensure=stopped is applied.