<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Don&#8217;t let this happen to you&#8230;</title>
	<atom:link href="http://www.tnpcnewsletter.com/blog/2009/01/24/dont-let-this-happen-to-you/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tnpcnewsletter.com/blog/2009/01/24/dont-let-this-happen-to-you/</link>
	<description>Asking better questions</description>
	<lastBuildDate>Tue, 07 Feb 2012 13:09:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Willard A Minns</title>
		<link>http://www.tnpcnewsletter.com/blog/2009/01/24/dont-let-this-happen-to-you/comment-page-1/#comment-21818</link>
		<dc:creator>Willard A Minns</dc:creator>
		<pubDate>Sun, 25 Jan 2009 03:47:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.tnpcnewsletter.com/blog/2009/01/24/dont-let-this-happen-to-you/#comment-21818</guid>
		<description>I confirm the statement by Joshua Proschan! I also had a problem with both Drives and Folders, when doubled clicked they would try to open in the first program listed in my &quot;open with&quot; list. They could only be opened by right clicking and selecting &quot;open&quot;. Then my printers disappeared when the print spooler service was inhibited from starting. It took almost 2 weeks from first noticing the problems to final cleaning of of the residual problems.</description>
		<content:encoded><![CDATA[<p>I confirm the statement by Joshua Proschan! I also had a problem with both Drives and Folders, when doubled clicked they would try to open in the first program listed in my &#8220;open with&#8221; list. They could only be opened by right clicking and selecting &#8220;open&#8221;. Then my printers disappeared when the print spooler service was inhibited from starting. It took almost 2 weeks from first noticing the problems to final cleaning of of the residual problems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joshua Proschan</title>
		<link>http://www.tnpcnewsletter.com/blog/2009/01/24/dont-let-this-happen-to-you/comment-page-1/#comment-21817</link>
		<dc:creator>Joshua Proschan</dc:creator>
		<pubDate>Sun, 25 Jan 2009 02:04:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.tnpcnewsletter.com/blog/2009/01/24/dont-let-this-happen-to-you/#comment-21817</guid>
		<description>Microsoft&#039;s advice is not adequate.  See:

http://www.computerworld.com/action/article.do?command=viewArticleBasic&amp;articleId=9126478&amp;source=rss_news

Also the US-CERT advisory:

http://www.us-cert.gov/cas/techalerts/TA09-020A.html

According to US-CERT you must also apply a little-known MS update (KB953252) that Microsoft does not mention on the page you mention.  Without this update, Windows ignores the registry settings for NoDriveAutoRun and NoDriveTypeAutoRun.  Once this patch is installed, Windows will enforce the NoDriveAutoRun and NoDriveTypeAutoRun settings.

I can confirm from my own experience (two XP Pro PCs) that, at least for USB drives, the No...AutoRun settings are ineffective without the KB953252 update.  The update is version-specific; the link to these is in the last paragraph (&quot;update&quot;) of the US-CERT advisory.  After applying the update, the No...AutoRun values must be added to the registry as described by CERT.

One thing hinted at in the advisory: the registry changes should be made to HKLM, and not HKCU.  HKLM over-rides any HKCU settings, and need only be changed once on each PC (from an admin login).  HKCU changes must be made user-by-user, which must be promoted to administrator to make the changes.  For almost all PCs, having the same settings for all users is the best way to protect the system as well as the simplest.

Thanks for the great newsletter; I look forward to the next issue.</description>
		<content:encoded><![CDATA[<p>Microsoft&#8217;s advice is not adequate.  See:</p>
<p><a href="http://www.computerworld.com/action/article.do?command=viewArticleBasic&amp;articleId=9126478&amp;source=rss_news" rel="nofollow">http://www.computerworld.com/action/article.do?command=viewArticleBasic&amp;articleId=9126478&amp;source=rss_news</a></p>
<p>Also the US-CERT advisory:</p>
<p><a href="http://www.us-cert.gov/cas/techalerts/TA09-020A.html" rel="nofollow">http://www.us-cert.gov/cas/techalerts/TA09-020A.html</a></p>
<p>According to US-CERT you must also apply a little-known MS update (KB953252) that Microsoft does not mention on the page you mention.  Without this update, Windows ignores the registry settings for NoDriveAutoRun and NoDriveTypeAutoRun.  Once this patch is installed, Windows will enforce the NoDriveAutoRun and NoDriveTypeAutoRun settings.</p>
<p>I can confirm from my own experience (two XP Pro PCs) that, at least for USB drives, the No&#8230;AutoRun settings are ineffective without the KB953252 update.  The update is version-specific; the link to these is in the last paragraph (&#8220;update&#8221;) of the US-CERT advisory.  After applying the update, the No&#8230;AutoRun values must be added to the registry as described by CERT.</p>
<p>One thing hinted at in the advisory: the registry changes should be made to HKLM, and not HKCU.  HKLM over-rides any HKCU settings, and need only be changed once on each PC (from an admin login).  HKCU changes must be made user-by-user, which must be promoted to administrator to make the changes.  For almost all PCs, having the same settings for all users is the best way to protect the system as well as the simplest.</p>
<p>Thanks for the great newsletter; I look forward to the next issue.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

