{"id":796,"date":"2013-10-15T16:28:43","date_gmt":"2013-10-15T21:28:43","guid":{"rendered":"http:\/\/www.poweradmin.com\/blog\/?p=796"},"modified":"2015-04-27T08:34:49","modified_gmt":"2015-04-27T13:34:49","slug":"windows-2003-and-high-cpu-usage-in-svchost","status":"publish","type":"post","link":"https:\/\/www.poweradmin.com\/blog\/windows-2003-and-high-cpu-usage-in-svchost\/","title":{"rendered":"Windows 2003 and High CPU Usage in Svchost"},"content":{"rendered":"

\n\tWindows 2003 is getting a bit long in the tooth, but we've got a number of customers that are still happily using it, and for good reason \u2014 it's a solid work horse of an OS.\n<\/p>\n

\n\tWe've recently come upon an issue where some of our 2003 servers in the lab were pegging the CPU at 100%. \u00a0Investigation revealed svchost was the culprit. \u00a0But there are lots of svchost processes, what is it really doing? \u00a0There is a cool trick to figure it out:\n<\/p>\n

\n\tRun: tasklist.exe \/svc \/fi \"imagename eq svchost.exe\"\n<\/p>\n

\n\tYou'll see someething like:<\/span>\n<\/p>\n

\n\t\"tasklist\"<\/a>\n<\/p>\n

\n\tHere you can see the PID associated with those svchost processes, and which service is running in each. \u00a0Look in Task Manager to get the PID, compare to this list, and you've now narrowed down which service is hogging the CPU.\n<\/p>\n

\n\tHigh CPU Usage in Automatic Update Service
\n<\/h2>\n

\n\tIn our case, it turns out we've run into a known issue where the Automatic Update service goes a little crazy with CPU usage. \u00a0It will drop down after finishing a scan, but will jump up again the next day.\n<\/p>\n

\n\tSince this is a known issue, there is also a fix.\u00a0 This page\u00a0http:\/\/support.microsoft.com\/kb\/927891<\/a>\u00a0lists two patches to install. \u00a0After running and installing these (and one was already installed in our case), we've not had the problem since \ud83d\ude42\n<\/p>\n

\n\tUPDATE:<\/strong> Elohir and Byron_K below mentioned a new patch that seems to fix this problem even in cases where the previous fix hasn't worked. \u00a0A big thank you! for sharing it.\n<\/p>\n

\n\thttp:\/\/technet.microsoft.com\/en-us\/security\/bulletin\/ms13-097<\/a>\n<\/p>\n

\n\t\u00a0\n<\/p>\n

\n\t\"Tweet<\/a>\n<\/p>\n

\n\t\"Share<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Windows 2003 is getting a bit long in the tooth, but we’ve got a number of customers that are still happily using it, and for good reason \u2014 it’s a solid work horse of an OS. We’ve recently come upon an issue where some of our 2003 servers in the lab were pegging the CPU […]<\/p>\n","protected":false},"author":3,"featured_media":797,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,5,6,9,8],"tags":[],"class_list":["post-796","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-general-it","category-how-to","category-tech","category-technical","category-windows"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t