<?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>Why you don’t want to edit your pending.xml to resolve 0xC0000034 issues</title><link>http://blogs.technet.com/b/askcore/archive/2011/03/11/why-you-don-t-want-to-edit-your-pending-xml-to-resolve-0xc0000034-issues.aspx</link><description>I know that one of the workarounds everyone is using is editing the pending.xml file and rebooting the machine.&amp;#160; This is seemingly working for everyone that the SetupExecute registry value does not.&amp;#160; I wanted to give a brief rundown as to why</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Why you don’t want to edit your pending.xml to resolve 0xC0000034 issues</title><link>http://blogs.technet.com/b/askcore/archive/2011/03/11/why-you-don-t-want-to-edit-your-pending-xml-to-resolve-0xc0000034-issues.aspx#3413471</link><pubDate>Wed, 16 Mar 2011 20:18:02 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3413471</guid><dc:creator>Dr Phil H</dc:creator><description>&lt;p&gt;This is ridiculous...Microsoft releases something that literally breaks your machine.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3413471" width="1" height="1"&gt;</description></item><item><title>re: Why you don’t want to edit your pending.xml to resolve 0xC0000034 issues</title><link>http://blogs.technet.com/b/askcore/archive/2011/03/11/why-you-don-t-want-to-edit-your-pending-xml-to-resolve-0xc0000034-issues.aspx#3412383</link><pubDate>Sun, 13 Mar 2011 20:41:57 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3412383</guid><dc:creator>Bytsy</dc:creator><description>&lt;p&gt;While it may be true that the problem is not totally fixed by editing the pending.xml file in this manner it does at least allow access to an otherwise &amp;#39;dead&amp;#39; machine! It is incredible that this service pack has been allowed out to wreak such havoc without being adequately tested. What is the fix which will now be offered to users who have had to fight their own way to the position of having implemented this less-than-total fix? &lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3412383" width="1" height="1"&gt;</description></item><item><title>re: Why you don’t want to edit your pending.xml to resolve 0xC0000034 issues</title><link>http://blogs.technet.com/b/askcore/archive/2011/03/11/why-you-don-t-want-to-edit-your-pending-xml-to-resolve-0xc0000034-issues.aspx#3393805</link><pubDate>Fri, 11 Mar 2011 18:22:20 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3393805</guid><dc:creator>MaPaMa</dc:creator><description>&lt;p&gt;As one of the IT Support professionals who&amp;#39;s been affected. I can tell you that &amp;quot;letting the failure occur later&amp;quot; is not an option. As the machine is stuck on the fatal error screen, and does not get past it to execute a rollback. Editing the pending.xml or replacing it, was a workaround to get the machine to a point where the service back would rollback. &lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3393805" width="1" height="1"&gt;</description></item></channel></rss>