Windows 10: Stuck terminating Power shell threads

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?

:)

 

Shell (terminal) options

Hello. I just want to understand a precise distinction between 3 shell systems:

1) CommandPrompt,

2) Power Shell,

3) Windows Terminal

Could you please explain it to me, and what is functional purpose of each shell system.

And in addition could you advice which one is the most appropriate to use to run commands for Intergated Developing Environment (for programming)?

 

Shell (terminal) options

Hello. I don't know why the robots reply respond if the robots do not know the answer. Yes I apologize for the robot generic answers pointing to another website.

The Proper answer is:

CommandPrompt = is shell.

conhost = CommandPrompt with scroll back

Power Shell = loop back to CommandPrompt

Windows Terminal = CommandPrompt/Powershell GUI loopback

Thank you

From me a Human

 

windows shell experience host terminated

I have perhaps a clue that may help you (or Microsoft). I first started seeing windows shell experience host closed from time to time when my PC started from sleep (event id 1002, closed because it stopped interacting
with Windows). But as I traced the events further, this was ALWAYS preceded by windows shell experience host closed upon PC going to sleep (event id 2484. terminated because it took too long to suspend).

Further examination and experiments point to this as a solution:

From Power Shell Admin:

Get-appxpackage -all *shellexperience* -packagetype bundle |% {add-appxpackage -register -disabledevelopmentmode ($_.installlocation + “\appxmetadata\appxbundlemanif

The problem returned after a improper shutdown (electrical outage), and the above command resolved it again.

My problem does not appear to be related to the OS version/patch, corruption, drivers, etc. Microsoft can weigh in, but I suggest trying this command in power shell before any time consuming or other risky updates. One last note, I rebooted after issuing
the power shell command, which may or may not be necessary.