<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress.com" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>

<channel>
	<title>the-application-failed-to-initialize-properly-0xc0000005 &amp;laquo; WordPress.com Tag Feed</title>
	<link>http://en.wordpress.com/tag/the-application-failed-to-initialize-properly-0xc0000005/</link>
	<description>Feed of posts on WordPress.com tagged "the-application-failed-to-initialize-properly-0xc0000005"</description>
	<pubDate>Thu, 23 May 2013 15:38:38 +0000</pubDate>

	<generator>http://en.wordpress.com/tags/</generator>
	<language>en</language>

<item>
<title><![CDATA[Google Chrome.exe: Application Error - The application failed to initialize properly (0xc0000005)]]></title>
<link>http://deepupc.wordpress.com/2009/12/04/google-chrome-exe-application-error-the-application-failed-to-initialize-properly-0xc0000005/</link>
<pubDate>Fri, 04 Dec 2009 11:59:53 +0000</pubDate>
<dc:creator>deepupc</dc:creator>
<guid>http://deepupc.wordpress.com/2009/12/04/google-chrome-exe-application-error-the-application-failed-to-initialize-properly-0xc0000005/</guid>
<description><![CDATA[Edit the property of the shortcut you use to launch Google chrome and --no-sandbox option at the end]]></description>
<content:encoded><![CDATA[<p>Edit the property of the shortcut you use to launch  Google chrome and <code>--no-sandbox</code> option at the end of the “target” line (after  the path to the chrome exe) i.e. Right click your shortcut to “Google Chrome”  and click Properties. In the target text field, add a space then add  <strong><code>--no-sandbox</code></strong> (with two dashes before “no”) right  after the ending quotation mark. Run using this shortcut.However make sure that  there is a space in between the ending quotation mark and the  <strong><code>--no-sandbox</code></strong> option that you add.You could find a  shortcut to google chrome on your desktop.Also note that you should use two  dashes before “no”.See the pic. below.</p>
<p><img title="google-chrome-0xc0000005" src="http://techblissonline.com/wp-content/uploads/2008/09/google-chrome-0xc0000005.jpg" alt="google-chrome-0xc0000005" width="361" height="465" /><br />
You are in effect loosing the sandbox effect of Google  Chrome.</p>
]]></content:encoded>
</item>
<item>
<title><![CDATA[Google Chrome : The application failed to initialize properly (0xc0000005)]]></title>
<link>http://palaniraja.wordpress.com/2008/09/03/google-chrome-the-application-failed-to-initialize-properly-0xc0000005/</link>
<pubDate>Wed, 03 Sep 2008 07:32:52 +0000</pubDate>
<dc:creator>Palani raja</dc:creator>
<guid>http://palaniraja.wordpress.com/2008/09/03/google-chrome-the-application-failed-to-initialize-properly-0xc0000005/</guid>
<description><![CDATA[  The application failed to initialize properly (0xc0000005). Click on OK to terminate the applicati]]></description>
<content:encoded><![CDATA[<p> </p>
<blockquote><p><span style="color:#0000ff;">The application failed to initialize properly (0xc0000005).</span></p>
<p><span style="color:#0000ff;">Click on OK to terminate the application</span></p></blockquote>
<p> </p>
<p>Symantec causes this issue and the temp. solution is to disable the sandbox. And the solution from Google Groups is </p>
<p> </p>
<blockquote><p><span style="color:#0000ff;">You can try running Google Chrome with <strong><span style="color:#800000;"><code>--no-sandbox</code></span></strong> (you need to edit the properties of the shortcut you use to launch it).</span></p></blockquote>
<p> </p>
<p><strong>More links: </strong></p>
<p><strong>Issues </strong>: <a href="https://groups.google.com/group/google-chrome-help/search?q=&#38;start=0&#38;scoring=d&#38;enc_author=LjzA1TIAAACxnAQgd0s-x2NJHdBMCj1kX8-qliYfOMJi0wlpwfQxL7SnwL2ldEkDZ3UGY4Fi834vPp-8dun_mzBPI6iup1z0&#38;">https://groups.google.com/group/google-chrome-help/search?q=&#38;start=0&#38;scoring=d&#38;enc_author=LjzA1TIAAACxnAQgd0s-x2NJHdBMCj1kX8-qliYfOMJi0wlpwfQxL7SnwL2ldEkDZ3UGY4Fi834vPp-8dun_mzBPI6iup1z0&#38;</a></p>
<p><strong>Solution 1 :</strong> <a href="https://forums.symantec.com/syment/board/message?board.id=endpoint_protection11&#38;thread.id=15816">https://forums.symantec.com/syment/board/message?board.id=endpoint_protection11&#38;thread.id=15816</a></p>
<p><strong>Solution 2 :</strong> <a href="http://code.google.com/p/chromium/issues/detail?id=38#c26">http://code.google.com/p/chromium/issues/detail?id=38#c26</a></p>
<p> </p>
<p> </p>
<p><strong>Update: </strong></p>
<ul>
<li>I wrapped &#8220;<code>--no-sandbox</code>&#8221; in CODE tag now to resolve WP double hypen to emdash conversion.</li>
<li>Symantec is not the only known source to this issue.</li>
<li>To know more about what is sandbox? Please try the pages 25,26 on the book <a href="http://www.google.com/googlebooks/chrome/">http://www.google.com/googlebooks/chrome/</a></li>
</ul>
]]></content:encoded>
</item>

</channel>
</rss>
