Windows 10: Ran powercfg /energy and found this... Any ideas?

System Availability Requests:System Required Request
The device or driver has made a request to prevent the system from automatically entering sleep.
Requesting Driver Instance
Requesting Driver Device

This was an error on the report, any ideas of what this could be or how I can find it?

looks like a malicious driver or something of the sort.

:)

 

POWERCFG /ENERGY doesn't work anymore

??? have you read my post ???

there's no executable called POWERCNFG.EXE

FWIW here's what POWERCFG -ENERGY yields with no other options:

PS> powercfg -energy

Enabling tracing for 60 seconds...

Observing system behavior..

Exact same problem: returns immediately and doesn't create the output file.

.

 

Powercfg /energy immediately exits

When running "powercfg /energy" the command outputs the following:

PS C:\WINDOWS\system32> powercfg /energy

Enabling tracing for 60 seconds...

Observing system behavior...

It immediately returns me to the command line and does not generate a report. I had reinstalled 10 from a restore image (on my surface pro 4) and it was broken. I reset Windows and it started working properly. Now a few days later it's broken again. No updates
or software has been installed since the last time it worked. It just stopped working.

Anyone have know how to fix? There are no errors in the event viewer when I try to run.

 

POWERCFG /ENERGY doesn't work anymore

On one of my computers POWERCFG /ENERGY doesn't function (anymore).

It returns immediately and doesn't create the expected output file.

I have created a PowerShell test script that helps reproducing the issue.

Here's the script:

#requires
-RunAsAdministrator
$starttime
= (Get-Date)
$outputfile
= Join-Path
-Path
$env:TEMP -ChildPath
"pcet.html"
& powercfg
/energy /duration
30 /output
$outputfile
$rc = $LASTEXITCODE
Write-Host("POWERCFG /ENERGY returned with exit code {0} in {1} seconds"
-f $rc, ((Get-Date)
- $starttime).TotalSeconds)
if (Test-Path
-LiteralPath
$outputfile)
{
Write-Host
-ForegroundColor Green ("Output file '{0}' WAS created"
-f $outputfile)
Remove-Item
-Force
-LiteralPath
$outputfile
}
else
{
Write-Host
-ForegroundColor Red ("Output file '{0}' was NOT created"
-f $outputfile)
}

Here's the output on a computer without the issue:





and here's the output on the offending computer:





Both computers are running Windows 10 build 17763.503 (latest RS5/1809 build).

Where do I go from here?