Windows 10: Creators Update: number of processes

Turns out this is a change by design. Starting with Build 14942, Microsoft is not grouping services if you have sufficient amounts of memory. With this change, every service will have it's own dedicated svchost.exe process.

With higher amounts of RAM being commonplace today, there really wasn't a good reason for MS to share the svchost.exe process. With this new model, if 1 service happens to crash, it won't affect other services.

 

...As well as bugsolving, security issues etc. as explained in the article I read.

Oh, by the way:
(get-process |where-object {$_.ProcessName -Match "svchost"}).Count


counts all processes named "svchost"... is there any command to count all the services started by every svchost?

 

This can do it

$array=get-process |where-object {$_.ProcessName -Match "svchost"}|Select Id

foreach ($item in $array.Id){
Get-WmiObject -Class win32_service -Filter "ProcessID='$item'" | select DisplayName
}

 

Great! Thank you! *Biggrin
What language is this?

 

It's not a language (per se), it's PowerShell. PowerShell is Microsoft's configuration management engine intended for task automation and configuration management. it is based on .NET framework. It's a series of commands (called cmdlets) which return objects, rather than text. It's become a staple in Microsoft Exchange, and is being used more and more frequently across Microsoft products.

It's less complicated than learning a programming language because everything is based on a verb-noun concept (like, get-process). And you typically take the output of 1 command and Pipe it (|) into another command to string together a series of commands to end at the result you are looking for.

For example, you can start with
get-service

That command will return a list of services on your box, whether it's running or stopped and the name of the service.

You can build on that command with
get-service |Select *
Now you are seeing all of the available information you can get on each of the services

You can then modify that command to
get-service |select Name,CanShutdown,StartType
Which shows you specific columns you want.

Now, you can take get-service spo*|stop-service
That command will take all services that start with spo and stop them.

Now, run
get-service spooler and it should be stopped

Can now restart with
start-service spooler

Want to shut down your computer faster, you can run
stop-computer

Here is another example
start-process notepad.exe

Run it 2 more times
start-process notepad.exe
start-process notepad.exe

Then,
get-process |where-object ProcessName -eq notepad

Then,
get-process|where-object ProcessName -eq notepad|Select *

Then,
get-process|where-object ProcessName -eq notepad|select StartTime,WS

Now you can see the start time and the memory size used.

Now, kill them all
get-process |where ProcessName -eq notepad|stop-process

 

Thank You pparks1. It's very versatile! *Smile

 

You can copy and paste this directly into the Powershell ISE to run it.

Any way to sort the output alphabetically? Sort-Object?

 

Yes, at end, run
Sort-object using the property value you want to sort on and then you can sort ascending or descending.

 

hmmm...
| Sort-Object <object>

...maybe? :/

 

I've tried to use Sort-Object but no success. Can you include it in the sample code?

$array=get-process |where-object {$_.ProcessName -Match "svchost"}|Select Id

foreach ($item in $array.Id){
Get-WmiObject -Class win32_service -Filter "ProcessID='$item'" | select DisplayName
}

 

Out-gridview would do it although there is a more elegant way I'm sure.

Code: $array=get-process |where-object {$_.ProcessName -Match "svchost"}|Select Id $names=foreach($item in $array.Id){ Get-WmiObject -Class win32_service -Filter "ProcessID='$item'" | select DisplayName } $names | sort-object DisplayName | out-gridview[/quote]

 

That works, thanks. Takes a bit longer but not much.

 

Perhaps this may explain why my limited 4gig of RAM laptop now seems slightly more sluggish after the update. Yes, It seemed sluggish before, but now...

Anyway this is why I tell people I see absolutely NO reason to stick with less than 8, or even 16 gig of RAM. Both my desktops run 32gig. But my Asus Zenbook Prime UX31A laptop is locked at 4gig by design *Mad

 

I always recommend 8. Haven't had less than 8 for many years. 16 is good for vms. I have not yet taken a home machine over 16GB.

 

As a photographer who processes large image files (typically 800mb to 1gig) in Photoshop, I find 32gig works well for me. And for me, I've not been with less 8 for many years as well.

When I bough my notebook I knew it was RAM limited but I figured I could work with it seeing I don't game on it. Now it chokes whenever I try to process RAW files through LR from my Nikon D800E. Being a 36 megapixel camera it produces 73meg nef files. You can bet my next notebook won't be so RAM limited.

Anyway with Windows 10, anyone running 4gig of RAM on a 64-bit OS is in for a sluggish ride. I know, I'm there with my notebook *Sad