Windows 10 Build 14942 - One Long overdue change
On Friday Oct 7, MS released Windows 10 Redstone 2 branch build 14942 to Fast Ring Insiders. This was a PC only build.
The update installed cleanly on PC, Laptop and Tablet.
While there were a handful of fixes, a new Photos app and Update icon and teh ability to hide the app list on start, there was one big change that to me was long overdue in Windows.
That change involved how MS represented running services in Task Manager.
For years, MS lumped together many of the Windows Services that are managed in Windows Management Console into a very ubiquitous service called SvcHost with little ability to monitor or kill those individual services via Task Manager. You would just see a list of svchost.exe processes running with little to no idea what service that process was actually running.
For machines with 3.5GB of RAM or higher that has all changed. Starting with 14942 there are individual listings of each service and so now you have the ability to see how many resources the service is consuming along with ability to kill an individual service.
To me this is a long overdue and welcomed change. Why they limited it to machines with 3.5GB Ram or higher is a bit of a mystery, and I'd still like to see it simply list the services versus placing them under the Service Host moniker.
While Service Host is accurate in terms of the actual svchost.exe that is running the service, folks think in terms of service names - like BITS or User Profile, etc. You can see the actual service name by expanding the service host entry, but it should be the opposite way around.
You can also show the actual command line that started the service in the first place. This goes a long way towards reducing troubleshooting and repair if things get sideways. So thank you Microsoft. You should have done this a decade ago.
Overall Redstone 2 seems to be much more about refinement and bug fixes of Redstone 1 issues than moving forward dramatically. As I mentioned in an earlier post regarding the announcements from the Ignite conference, it almost appears as though there is a change in tone with Redstone 2. So it's still earlier in the branch cycle, but so far, the changes are subtle.
The update installed cleanly on PC, Laptop and Tablet.
While there were a handful of fixes, a new Photos app and Update icon and teh ability to hide the app list on start, there was one big change that to me was long overdue in Windows.
That change involved how MS represented running services in Task Manager.
For years, MS lumped together many of the Windows Services that are managed in Windows Management Console into a very ubiquitous service called SvcHost with little ability to monitor or kill those individual services via Task Manager. You would just see a list of svchost.exe processes running with little to no idea what service that process was actually running.
For machines with 3.5GB of RAM or higher that has all changed. Starting with 14942 there are individual listings of each service and so now you have the ability to see how many resources the service is consuming along with ability to kill an individual service.
To me this is a long overdue and welcomed change. Why they limited it to machines with 3.5GB Ram or higher is a bit of a mystery, and I'd still like to see it simply list the services versus placing them under the Service Host moniker.
While Service Host is accurate in terms of the actual svchost.exe that is running the service, folks think in terms of service names - like BITS or User Profile, etc. You can see the actual service name by expanding the service host entry, but it should be the opposite way around.
You can also show the actual command line that started the service in the first place. This goes a long way towards reducing troubleshooting and repair if things get sideways. So thank you Microsoft. You should have done this a decade ago.
Overall Redstone 2 seems to be much more about refinement and bug fixes of Redstone 1 issues than moving forward dramatically. As I mentioned in an earlier post regarding the announcements from the Ignite conference, it almost appears as though there is a change in tone with Redstone 2. So it's still earlier in the branch cycle, but so far, the changes are subtle.
Comments
Post a Comment