<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Microsoft Supportability e-Newsletter : Windows Automatic Update</title><link>http://blogs.technet.com/asiasupp/archive/tags/Windows+Automatic+Update/default.aspx</link><description>Tags: Windows Automatic Update</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Automatic Update causes SVCHOST.exe high CPU</title><link>http://blogs.technet.com/asiasupp/archive/2007/05/29/automatic-update-causes-svchost-exe-high-cpu.aspx</link><pubDate>Tue, 29 May 2007 09:54:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:1093520</guid><dc:creator>Support News Editor</dc:creator><slash:comments>6</slash:comments><comments>http://blogs.technet.com/asiasupp/comments/1093520.aspx</comments><wfw:commentRss>http://blogs.technet.com/asiasupp/commentrss.aspx?PostID=1093520</wfw:commentRss><wfw:comment>http://blogs.technet.com/asiasupp/rsscomments.aspx?PostID=1093520</wfw:comment><description>Symptom SVCHOST high CPU. If stopping the Automatic Update service, the high CPU issue disappears. You can use the following method to verify whether it is AU caused SVCHOST high CPU. 1. Run the command to find the PID of SVCHOST which is running on Automatic...(&lt;a href="http://blogs.technet.com/asiasupp/archive/2007/05/29/automatic-update-causes-svchost-exe-high-cpu.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=1093520" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/asiasupp/archive/tags/Hot+Issue/default.aspx">Hot Issue</category><category domain="http://blogs.technet.com/asiasupp/archive/tags/Windows+Automatic+Update/default.aspx">Windows Automatic Update</category></item><item><title>Easy ways to query hot fix information</title><link>http://blogs.technet.com/asiasupp/archive/2006/09/19/457421.aspx</link><pubDate>Tue, 19 Sep 2006 10:11:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:457421</guid><dc:creator>gbs</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.technet.com/asiasupp/comments/457421.aspx</comments><wfw:commentRss>http://blogs.technet.com/asiasupp/commentrss.aspx?PostID=457421</wfw:commentRss><wfw:comment>http://blogs.technet.com/asiasupp/rsscomments.aspx?PostID=457421</wfw:comment><description>Many of customers request information on querying hot fix information. They need a report on what hot fixes have been patched and what hot fixes they do not have installed. This article explains several ways to find this information....(&lt;a href="http://blogs.technet.com/asiasupp/archive/2006/09/19/457421.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=457421" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/asiasupp/archive/tags/Best+Practice/default.aspx">Best Practice</category><category domain="http://blogs.technet.com/asiasupp/archive/tags/Windows+Automatic+Update/default.aspx">Windows Automatic Update</category></item><item><title>Automatic Update Scan Issues</title><link>http://blogs.technet.com/asiasupp/archive/2006/09/19/457409.aspx</link><pubDate>Tue, 19 Sep 2006 09:33:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:457409</guid><dc:creator>gbs</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.technet.com/asiasupp/comments/457409.aspx</comments><wfw:commentRss>http://blogs.technet.com/asiasupp/commentrss.aspx?PostID=457409</wfw:commentRss><wfw:comment>http://blogs.technet.com/asiasupp/rsscomments.aspx?PostID=457409</wfw:comment><description>Microsoft is aware, through recent customer feedback, that some enterprise customers have been experiencing Unexpectedly high cpu utilization or system unresponsiveness issue when they apply Microsoft updates to certain workstations or servers. 
Customers are experiencing this when they use Microsoft System Management Server (SMS) 2003 Service Pack 1 (SP1) or a later version together with the Inventory Tool for Microsoft Updates (ITMU). Customers also experience this issue on computers that are running the Windows Update Agent (WUA).
...(&lt;a href="http://blogs.technet.com/asiasupp/archive/2006/09/19/457409.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=457409" width="1" height="1"&gt;</description><category domain="http://blogs.technet.com/asiasupp/archive/tags/Hot+Issue/default.aspx">Hot Issue</category><category domain="http://blogs.technet.com/asiasupp/archive/tags/Windows+Automatic+Update/default.aspx">Windows Automatic Update</category></item></channel></rss>