Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Norton Internet Security
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
===Windows Service Packs=== When [[Norton Internet Security 2008]] was installed, users encountered incompatibilities upgrading to [[Windows XP Service Pack 3]] or [[Windows Vista Service Pack 1]]. Users reported invalid [[Windows Registry|registry]] keys added by a tool named fixcss.exe, resulting in an empty Device Manager and missing devices such as wireless network adapters.<ref name="Sym">{{cite web|title=FAQ: Upgrading to Windows XP Service Pack 3 or Windows Vista Service Pack 1 with your Norton 2008 product installed |url=http://solutions.symantec.com/sdccommon/asp/symcu_defcontent_view.asp?sprt_cid=b32555cd-1b26-4041-abac-882faf8d365f |publisher=Symantec Corporation |date=4 August 2008 |access-date=2009-03-28 |url-status=dead |archive-url=https://web.archive.org/web/20090325215843/http://solutions.symantec.com/sdccommon/asp/symcu_defcontent_view.asp?sprt_cid=b32555cd-1b26-4041-abac-882faf8d365f |archive-date=25 March 2009 }}</ref> Symantec initially blamed Microsoft for the incompatibilities but accepted partial responsibility. Dave Cole, Symantec's Vice President & General Manager,<ref name="Symantec's Vice President & General Manager">{{Cite web|url=http://www.symantec.com/about/news/resources/press_kits/bio.jsp?bioid=dave_cole|archive-url=https://web.archive.org/web/20070305045330/http://www.symantec.com/about/news/resources/press_kits/bio.jsp?bioid=dave_cole|url-status=dead|archive-date=March 5, 2007|title=Dave Cole|publisher=Symantec|access-date=2013-08-10}}</ref> acknowledged that users running Norton products were experiencing problems, but said the numbers were small. Cole said that Symantec had done "extensive testing" of its products with Windows XP SP3, but this issue was not encountered. Cole blamed Microsoft "This is related to XP SP3." Microsoft recommended that users contact Windows customer support.<ref name="Gregg">{{Cite news|url=http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9088598/ |title=Symantec pins blame for XP SP3 registry corruption on Microsoft |publisher=Computerworld Inc. |author=Gregg Keizer |date=2008-05-23 |access-date=2008-06-19 |url-status=dead |archive-url=https://web.archive.org/web/20090122232705/http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9088598%2F |archive-date=2009-01-22 }}</ref> To resolve the problem, Symantec issued a fix intended for users before upgrading.<ref name="Sym"/> Symantec recommended disabling the tamper protection component in the 2008 release, dubbed SymProtect. A tool to remove the added registry entries was available from Symantec.<ref name="Sym"/>
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)