<?xml version="1.0" encoding="UTF-8"?>
<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/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>gHacks technology news &#187; symprotect</title>
	<atom:link href="http://www.ghacks.net/tag/symprotect/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ghacks.net</link>
	<description>A technology blog covering software, mobile phones, gadgets, security, the Internet and other relevant areas.</description>
	<lastBuildDate>Mon, 23 Nov 2009 22:22:46 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Symantec Registry Fix for Windows XP Service Pack 3</title>
		<link>http://www.ghacks.net/2008/06/10/symantec-registry-fix-for-windows-xp-service-pack-3/</link>
		<comments>http://www.ghacks.net/2008/06/10/symantec-registry-fix-for-windows-xp-service-pack-3/#comments</comments>
		<pubDate>Tue, 10 Jun 2008 06:34:25 +0000</pubDate>
		<dc:creator>Martin</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[service pack 3]]></category>
		<category><![CDATA[symantec]]></category>
		<category><![CDATA[symantec registry fix]]></category>
		<category><![CDATA[symprotect]]></category>
		<category><![CDATA[symregfix]]></category>
		<category><![CDATA[windows-xp]]></category>

		<guid isPermaLink="false">http://www.ghacks.net/?p=4928</guid>
		<description><![CDATA[Users with a recent Symantec product faced several problems after updating their computer from Windows XP Service Pack 2 to the latest version, among them removed network connections, an empty device manager, unusable wireless connections and thousands of bogus Registry entries. This was apparently caused by the toolsymprotect, a part of many Symantec applications, that [...]]]></description>
			<content:encoded><![CDATA[<p>Users with a recent Symantec product faced several problems after updating their computer from Windows XP Service Pack 2 to the latest version, among them removed network connections, an empty device manager, unusable wireless connections and thousands of bogus Registry entries. This was apparently caused by the tool<a href="http://www.ghacks.net/2008/05/28/symantec-disable-symprotect-before-upgrading-to-windows-xp-sp3/">symprotect</a>, a part of many Symantec applications, that is protecting those applications against malware. It did that so well that it prevented the Windows XP installation routine from deleting temporary Registry keys which in turn caused the problems for the users.</p>
<p>Initially Symantec blaimed Microsoft solely but admitted that symprotect was involved as well. The tool <a href="http://solutions.symantec.com/sdccommon/asp/symcu_defcontent_view.asp?ssfromlink=true&#038;sprt_cid=b32555cd-1b26-4041-abac-882faf8d365f&#038;docid=20080530144453EN">SymRegFix.exe</a> has been designed by Symantec to remove the bogus Registry entries and correct the errors that have been caused by them on the user&#8217;s system. The software has to be downloaded to the local computer and executed from there, it will fix the Registry automatically.</p>
<p>Symantec users who have not updated to Windows XP Service Pack 3 yet will be delighted to hear that Symantec added a solution to prevent the situation to live updates of their products. If the Symantec product is fully updated the problems will not arise and symprotect does not have to be disabled during Service Pack 3 installation.</p>
<p><span id="more-4928"></span></p>

	Tags: <a href="http://www.ghacks.net/tag/service-pack-3/" title="service pack 3" rel="tag">service pack 3</a>, <a href="http://www.ghacks.net/tag/symantec/" title="symantec" rel="tag">symantec</a>, <a href="http://www.ghacks.net/tag/symantec-registry-fix/" title="symantec registry fix" rel="tag">symantec registry fix</a>, <a href="http://www.ghacks.net/tag/symprotect/" title="symprotect" rel="tag">symprotect</a>, <a href="http://www.ghacks.net/tag/symregfix/" title="symregfix" rel="tag">symregfix</a>, <a href="http://www.ghacks.net/tag/windows-xp/" title="windows-xp" rel="tag">windows-xp</a><br />

	<h4>Related posts</h4>
	<ul class="st-related-posts">
	<li><a href="http://www.ghacks.net/2008/05/28/symantec-disable-symprotect-before-upgrading-to-windows-xp-sp3/" title="Symantec: Disable SymProtect before upgrading to Windows XP SP3 (May 28, 2008)">Symantec: Disable SymProtect before upgrading to Windows XP SP3</a> (1)</li>
	<li><a href="http://www.ghacks.net/2008/07/03/microsoft-issues-windows-xp-service-pack-3-update-fix/" title="Microsoft issues Windows XP Service Pack 3 Update Fix (July 3, 2008)">Microsoft issues Windows XP Service Pack 3 Update Fix</a> (5)</li>
	<li><a href="http://www.ghacks.net/2008/05/07/xp-sp3-and-vista-sp-1-available-through-windows-update/" title="XP SP3 and Vista SP 1 available through Windows Update (May 7, 2008)">XP SP3 and Vista SP 1 available through Windows Update</a> (6)</li>
	<li><a href="http://www.ghacks.net/2008/04/16/windows-xp-sp3-release-date-announced/" title="Windows XP SP3 Release Date announced (April 16, 2008)">Windows XP SP3 Release Date announced</a> (1)</li>
	<li><a href="http://www.ghacks.net/2008/02/20/windows-xp-sp3-release-candidate-2/" title="Windows XP SP3 Release Candidate 2 (February 20, 2008)">Windows XP SP3 Release Candidate 2</a> (4)</li>
</ul>

]]></content:encoded>
			<wfw:commentRss>http://www.ghacks.net/2008/06/10/symantec-registry-fix-for-windows-xp-service-pack-3/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Symantec: Disable SymProtect before upgrading to Windows XP SP3</title>
		<link>http://www.ghacks.net/2008/05/28/symantec-disable-symprotect-before-upgrading-to-windows-xp-sp3/</link>
		<comments>http://www.ghacks.net/2008/05/28/symantec-disable-symprotect-before-upgrading-to-windows-xp-sp3/#comments</comments>
		<pubDate>Wed, 28 May 2008 10:40:46 +0000</pubDate>
		<dc:creator>Martin</dc:creator>
				<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[service pack 3]]></category>
		<category><![CDATA[symantec]]></category>
		<category><![CDATA[symprotect]]></category>
		<category><![CDATA[windows-xp]]></category>

		<guid isPermaLink="false">http://www.ghacks.net/?p=4359</guid>
		<description><![CDATA[If you are running the Symantec products Norton Internet Security 2008, Norton SystemWorks 2008, Norton 360 or Norton AntiVirus 2008 on a machine with Windows XP Service Pack 2 and want to upgrade to Service Pack 3 you should disable the SymProtect feature before doing so or your operating system could go kaboom. More precisely [...]]]></description>
			<content:encoded><![CDATA[<p>If you are running the Symantec products Norton Internet Security 2008, Norton SystemWorks 2008, Norton 360 or Norton AntiVirus 2008 on a machine with Windows XP Service Pack 2 and want to upgrade to Service Pack 3 you should disable the SymProtect feature before doing so or your operating system could go kaboom. More precisely users would be left with an empty device manager and network connections window. This is apparently caused by a large number of bogus Registry keys starting with special characters that have been added to the Registry during the update.</p>
<p>Reese Anschultz, Sr. SQA Manager of Symantec Corporation, posted information on how to disable the SymProtect feature in all Symantec products in a <a href="http://norton.lithium.com/norton/board/message?board.id=nis_feedback&#038;thread.id=967&#038;view=by_date_ascending&#038;page=2">support</a> forum. Symantec is currently developing a tool to clean the Registry from those extraneous registry keys. Unfortunately no information were posted when the tool will be available but it will most likely be in the coming week.</p>
<p>The problem apparently spawns from the fact that the Microsoft tool fixccs.exe is adding temporary keys to the Windows XP Registry during the update which cannot be deleted due to the SymProtect protection which prevents changes to the Registry. </p>
<p><span id="more-4359"></span>Below are the instructions on how to disable SymProtect on the various Symantec products.</p>
<blockquote><p>To help prevent this issue from occurring, you should disable SymProtect prior to installing the Windows XP SP3 upgrade. This setting, in Norton Internet Security 2008 and Norton AntiVirus 2008, can be found within the Options page as “Turn on protection for Norton products.” In this case you should uncheck the box prior to the upgrade. After the upgrade is complete, please remember to re-enable this feature. It should be noted, however, that this workaround only addresses issues with Symantec products. You may still run into similar problems with other products affected by this XP SP3 upgrade issue.</p></blockquote>
<blockquote><p>For Norton SystemWorks 2008 you have to go to the Advanced Options UI that is under Settings. Next, click on &#8220;Norton SystemWorks Options&#8221; and select the General tab. Lastly, uncheck the box that says, &#8220;Turn on protection for my Symantec product”.</p></blockquote>
<blockquote><p>For Norton SystemWorks 2008 Premier you can use either the previous instructions or the Norton AntiVirus instructions.</p></blockquote>
<p>What I don&#8217;t understand is that companies are always changing the location of the options and menus. That&#8217;s not user friendly. Microsoft for instance is always changing the location of the options in Internet Explorer. </p>

	Tags: <a href="http://www.ghacks.net/tag/service-pack-3/" title="service pack 3" rel="tag">service pack 3</a>, <a href="http://www.ghacks.net/tag/symantec/" title="symantec" rel="tag">symantec</a>, <a href="http://www.ghacks.net/tag/symprotect/" title="symprotect" rel="tag">symprotect</a>, <a href="http://www.ghacks.net/tag/windows-xp/" title="windows-xp" rel="tag">windows-xp</a><br />

	<h4>Related posts</h4>
	<ul class="st-related-posts">
	<li><a href="http://www.ghacks.net/2008/06/10/symantec-registry-fix-for-windows-xp-service-pack-3/" title="Symantec Registry Fix for Windows XP Service Pack 3 (June 10, 2008)">Symantec Registry Fix for Windows XP Service Pack 3</a> (3)</li>
	<li><a href="http://www.ghacks.net/2008/07/03/microsoft-issues-windows-xp-service-pack-3-update-fix/" title="Microsoft issues Windows XP Service Pack 3 Update Fix (July 3, 2008)">Microsoft issues Windows XP Service Pack 3 Update Fix</a> (5)</li>
	<li><a href="http://www.ghacks.net/2008/05/07/xp-sp3-and-vista-sp-1-available-through-windows-update/" title="XP SP3 and Vista SP 1 available through Windows Update (May 7, 2008)">XP SP3 and Vista SP 1 available through Windows Update</a> (6)</li>
	<li><a href="http://www.ghacks.net/2008/04/16/windows-xp-sp3-release-date-announced/" title="Windows XP SP3 Release Date announced (April 16, 2008)">Windows XP SP3 Release Date announced</a> (1)</li>
	<li><a href="http://www.ghacks.net/2008/02/20/windows-xp-sp3-release-candidate-2/" title="Windows XP SP3 Release Candidate 2 (February 20, 2008)">Windows XP SP3 Release Candidate 2</a> (4)</li>
</ul>

]]></content:encoded>
			<wfw:commentRss>http://www.ghacks.net/2008/05/28/symantec-disable-symprotect-before-upgrading-to-windows-xp-sp3/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
