Share via

Stuck terminating Power shell threads

Anonymous
2024-04-08T17:58:12+00:00

Hi,

we have a Windows 2016 Server that is not happy at all, over a few days the CPU usage gets higher and higher to the point where it needs a reboot to fix the issue.

the issue seems to be a set of PowerShell threads that are started by the system that are stuck in a terminating state and use around 20 % of the CPU each.

I can not work out what is creating can anyone offer a way to find out what is causing them?

Windows Server Remote and virtual desktops PowerShell

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-04-09T07:23:26+00:00

    Hi,

    Windows Server does not start PowerShell threads by default. Have you checked what PowerShell scripts are these threads running? Open Task Manager as administrator, switch to the Details tab, right click on the column headers, select "Select columns", and select "Command line". Then the scripts can be found in the "Command line" column.

    0 comments