Everyone! I have solved this problem. I want to think everyone for their input, as it has been instrumental in the process of elimination. I spent the last 8 hours trying this and I was able to replicate this problem 4 times in a row on 3 different machines. Here is the problem. When you remove the beta from your computer using the uninstaller, it leaves many files and dll's and control ID things behind. Then when you use the norton removal tool, all that basically does is removes the old keys from the registry. Well, I found out last night that the norton removal tool wont touch any system files(+s) or any hidden files(+h) attributes. So after many hours of trial and error, this is how I fixed the problem.
1. First thing is uninstall the program normally through the add remove if you have it listed, if not step 2.
2. Run the norton removal tool to clean the old keys from the registry. Then restart and meet back here or print this out.
3. Go to My computer and click on the 'Tools' menu. Go down and select 'Folder Options' Click on the view tab,
4. Check the radio box (the scantron bubble) Next to 'Show hidden files, folders, and drives'.
5. Uncheck 'Hide extensions for known file types'
6. Uncheck 'Hide protected operating system files (Recommended)'
7. Now navigate to the following locations "C:\ProgramData", replace C: with your installation drive.
8. Now you will see two files. Norton and Norton Installation. If you open these folders you will see they are jammed full of keys and file IDs from many failed installation attempts. Note: you may not even be able to open these folders at first. This was my case. Norton had locked these files and changed their attributes to system files and had taken full ownership of these said files.
9. Also look here "C:\Program Files\" for the Folders 'Norton Internet Security' and 'NortonInstaller' Make sure you delete these if they are present and if you can't delete them follow the same directions below. Take back ownership and then delete them.
10. I found this awesome registry script that does exactly what we want without me having to try to explain how to take back file ownership privileges. It allows us to take back ownership of these said files and folders.
11. Here is the download link for this very useful registry script that will add a 'Take ownership' Menu item to your right click menu.
http://www.howtogeek.com/downloads/TakeOwnership.zip . This is not a virus so please dont remove my link MODERATORS. I am trying to help people.
12. Next what you want to do is extract the zip file. 'TakeOwnership.zip' inside you will find the install reg file and the uninstall reg file. Double click the install file. You will get a system prompt saying are you sure you want to do this. The right button to click on is 'yes'.
13. Now after it is sucessfully enetered into the registry, when you right click on a file or folder, you will see an option to 'Take Ownership' this will allow you to be able to take back your file and folder permissions from Symantec.
14. Now where were we oh yes we were at item #7 before you had to install that registry script. Now as I was saying you will see two files. 'Norton' and 'Norton Installation' Right click on each one and select 'Take Ownership' from the right click menu. It will pop up a black command window and start changing all the files attributes and permissions back to you. It will take a couple minutes. When it is done, you will be able to browse these folders and also manipulate any of the files inside.
15. Now what I did and it worked for me was to delete these two folders entirely. So select both folders and press delete. Confirm delete.
16. Now restart again. When you log back on to windows, double click your installer again and watch with happiness as it installs properly. Then enter your key and bam your in business. Don't forget to run LiveUpdate.
Thanks to everyone. I am not saying this will work for everyone, however I was able to reproduce this same error on two desktops and a laptop all running windows 7. I followed the steps above and this fixed the same error I was having on all my computers. I really hope this solves everyones problems.
Message Edited by mattlenfest on 10-06-2009 10:18 AM
Message Edited by mattlenfest on 10-06-2009 10:22 AM
