<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>Hotfix Published for KB925336</title><link>http://blogs.msdn.com/heaths/archive/2007/04/24/hotfix-published-for-kb925336.aspx</link><description>When installing Visual Studio 2005 Service Pack 1 , users may see an error that reads, Error 1718.File D:\WINDOWS\Installer\50baad.msp was rejected by digital signature policy. I've published instructions to work around this issue using either the Management</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Hotfix Published for KB925336</title><link>http://blogs.msdn.com/heaths/archive/2007/04/24/hotfix-published-for-kb925336.aspx#2644217</link><pubDate>Tue, 15 May 2007 10:51:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2644217</guid><dc:creator>arsalan</dc:creator><description>&lt;p&gt;I have tried to install SP1 for Visual Studio 2k5 on a windows server 2003 R2 machine with sp1 having enough disk space; eventually giving me a memory dump. Any suggestions as to what should I do??? :(&lt;/p&gt;
&lt;p&gt;my email address:arsalan83@hotmail.com&lt;/p&gt;</description></item><item><title>re: Hotfix Published for KB925336</title><link>http://blogs.msdn.com/heaths/archive/2007/04/24/hotfix-published-for-kb925336.aspx#2656897</link><pubDate>Wed, 16 May 2007 00:09:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2656897</guid><dc:creator>Heath Stewart</dc:creator><description>&lt;p&gt;Contact Microsoft Customer Support Services via &lt;a rel="nofollow" target="_new" href="http://support.microsoft.com"&gt;http://support.microsoft.com&lt;/a&gt; and provide them with the memory dump.&lt;/p&gt;
&lt;p&gt;If you have a Windows Installer log generated as recommended in many of my posts or done automatically if not specified, you can follow some of the log diagnostics techniques in this blog to find the actual problem. Crashes in Windows Installer are rare and I have yet to see one - though both are entirely impossible - in custom actions we use (though the latter will most often fail for other reasons, though gracefully).&lt;/p&gt;
&lt;p&gt;See &lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/heaths/archive/2005/12/14/503796.aspx"&gt;http://blogs.msdn.com/heaths/archive/2005/12/14/503796.aspx&lt;/a&gt; for some help diagnosing Windows Installer logs if you want to do so yourself.&lt;/p&gt;
</description></item></channel></rss>