<?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>Help me, help you</title><link>http://blogs.technet.com/b/joscon/archive/2009/06/16/help-me-help-you.aspx</link><description>We frequently get cases where customers have issues with installing updates or service packs. With the release of Service Pack 2 recently for Windows Vista and Windows 2008, I thought it might be a good idea with what would be good to collect before you</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Help me, help you</title><link>http://blogs.technet.com/b/joscon/archive/2009/06/16/help-me-help-you.aspx#3388124</link><pubDate>Thu, 17 Feb 2011 22:04:38 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3388124</guid><dc:creator>Drewfus</dc:creator><description>&lt;p&gt;I see. So CheckSUR is like chkdsk for the component store, whereas SFC is more of a version fixing tool. So if anything, CheckSUR is the more &amp;#39;fundamental&amp;#39;, low-level tool of the two. Given that there must be some case for building CheckSUR into the OS, or at least making it available as a recommended Windows Update.&lt;/p&gt;
&lt;p&gt;Thanks Joseph.&lt;/p&gt;
&lt;p&gt;Andrew&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3388124" width="1" height="1"&gt;</description></item><item><title>re: Help me, help you</title><link>http://blogs.technet.com/b/joscon/archive/2009/06/16/help-me-help-you.aspx#3387947</link><pubDate>Thu, 17 Feb 2011 11:55:02 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3387947</guid><dc:creator>joscon [Microsoft]</dc:creator><description>&lt;p&gt;Sure, the reason you want to run CheckSUR first is that it is checking for corrupted binaries and manifests that it knows how to fix. &amp;nbsp;SFC on the other hand is checking to see if the version that you have in the component store matches that of the one on the file system. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;If you were having a problem with a corrupted manifest that was causing some sort of servicing issue, it most likely wouldnt be able to be reprojected with SFC, however CheckSUR could fix the manifest and then any further reprojection could take place as it should.&lt;/p&gt;
&lt;p&gt;--Joseph&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3387947" width="1" height="1"&gt;</description></item><item><title>re: Help me, help you</title><link>http://blogs.technet.com/b/joscon/archive/2009/06/16/help-me-help-you.aspx#3387862</link><pubDate>Thu, 17 Feb 2011 03:41:08 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3387862</guid><dc:creator>Drewfus</dc:creator><description>&lt;p&gt;Hi joscon.&lt;/p&gt;
&lt;p&gt;For a while I&amp;#39;ve wondered about the order that SURT and SFC should run in. Now I know, but I&amp;#39;m not sure what the reason is. Could you briefly explain why running SURT is step 2, and running SFC is step 3, and not the other way around?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3387862" width="1" height="1"&gt;</description></item></channel></rss>