• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 736
  • Last Modified:

Windows Explorer Opens Up Symentec Installer

I had a number of problems with my old works laptop. One of them was that when I press the Windows key and "E" to open Windows Explorer, the Symentec anti virus installer starts to run. When I cancel it WIndows Explorer opens as normal.

I have sincedchanged my lap top for a new one. It worked fine until a couple of days ago and I now have the same problem wit hSymentec installer running when I start WIndows Explorer by hitting the Windows key and "E".

My company IT helpdesk is useless and I am wondering if anybody here can help.

Thanks.
0
everton66
Asked:
everton66
  • 6
  • 5
  • 4
  • +2
1 Solution
 
captainCommented:
Hi

the reason for this in all likelihood is the remnant of an old Symantec product like Norton or IS in the registry.

The first attempt should be using the Microsoft cleanup tool:
http://support.microsoft.com/kb/290301

If this does not work use Symantecs download but this is likely to not clean out everything as Symantec like to keep info about installs in the registry for future product installs. They offer on their website: http://www.symantec.com/norton/support/dtree_ts.jsp?id=tech_issues&selected_nav=4
a download to remove Software remnants depending on product, so if you know your product you be able to do this from there with this tool.

If this does not work the sure fire way to get rid of it is to clean it from the Registry. I don't know how confident you are with this as you will have to take care not to remove any vital parts.

So this comes with a caveat that you do this at your own risk, and also on the assumption that you don't want/need any Symantec products on your system.

This is VERY RISKY if you delete the wrong thing. Do a system restore point or backup of your system. Then open the Registry, make sure the top of the registry tree is selected (as search goes down) and go to Edit|Search type in Symantec and hit OK. Delete the resulting KEY not the value, eg the KEY on the left side of the window, not the entry on the right.
Hit F3 when done and search jumps to the next result, repeat delete and F3 until Finished. Ignore the values in {LEGACY} keys as they will create an error deleting. Reboot.

hth
capt.

0
 
Vadim RappCommented:
Uninstall everything from Symantec on the computer. This would be step in right direction even without this problem.
0
 
everton66Author Commented:
Can't do that guys. Symentec is the current anti virus checker - it's there and still working and is the company's anti virus choice. Removing it is not an option.

I am curious as to why this has happened to me me twice on different lap tops and on the most recent it didnt happen at all until a few days ago.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
Vadim RappCommented:
something on these laptops changes or deletes some file or registry key that symantec's installer thinks is vital, so it repairs it.

Check out this my article then: http://www.vadimrapp.com/article3.htm
0
 
captainCommented:
Did you install a new program that added a shell extension or anything else that is unusual?

What happens if you run the installer, does it create an error about what it cannot find?

capt.
0
 
everton66Author Commented:
It trys to connect to the internal network resource to complete the install. I am not based in an office and this is not possible. None of my colleagues have this problem. I have not installed anything on the laptop.
0
 
captainCommented:
Does it look for a particular file? If so have a search on your laptop and if you find the same filename point the installer there instead.

0
 
everton66Author Commented:
Doesnt work. I'm interested as to why it was working fine and then it wasnt. Also why the problem has followed me from one laptop to anohter. I'm not alone, by all accounts. I see other threads with a similar theme involving Adobe. I dont any issues on my home desktop which also runs XP Pro.
0
 
captainCommented:
Hi

the only thing I could imagine is that the auto updater on the Adobe is causing some Symantec feature to kick in. But this would  normally start a outbound scan rather than an install and only if Adobe is started.

Difficult to tell. You can disable the auto updater as it is non critical by Starting Adobe, go to help, run Check for updates and then after it has finished select the preferences button and uncheck the 'Automatically..' check box.

Otherwise I am low on ideas..

capt.
0
 
Vadim RappCommented:
did you look in the event log for EventID 1004?
0
 
everton66Author Commented:
Hi. My problem doesnt involve Adobe - that was an example of another user on this forum who has a similar problem, but with Adobe and not Symentec. How do I check the event log?
0
 
Vadim RappCommented:
start - run - eventvwr
0
 
everton66Author Commented:
That event does exist with the following description:-

Detection of product '{33CFCF98-F8D6-4549-B469-6F4295676D83}', feature 'SAVMain', component '{F4CC0714-3217-44CE-AD72-5CE4781C33FE}' failed.  The resource 'C:\Program Files\Common Files\Microsoft Shared\SFPCA Cache\msxmlx.cat' does not exist.
0
 
fhdsubzCommented:
Not sure if some one found the solution to this. i found a work around to the problem. I had the same problem. I openned the MSI in a MSI editor (Wise,Installshield, Orca etc...) and in the custom action, there was a property being referenced to clear the cache in 'C:\Program Files\Common Files\Microsoft Shared\SFPCA Cache\ folder. What happens is the LiveUpdate which is running at all times sees the file missing and the Symantec MSI kicks off the seal healing, and it tries to repair the missing files. I just commented the custom action out and the Symentec no longer was broken on the machine.

Hope this helps!
0
 
Vadim RappCommented:
Thanks to this new comment I see that I completely forgot about this question.

I don't think this could be custom action that has caused the auto-repair, since custom action is (kind of) independent program called by the installation, a black box for the installer, so it does not participate in its definition of the integrity of the installation. From the event record above, it's obvious that the self-repair is started because the file msxmlx.cat is missing. And from the location of that file under folder related to "cache" it's obvious that in fact this file is temporary and therefore shouldn't be linked to the integrity of the product.

The possible solutions are:

1. create the wanted file. However, in this case it's likely that the application may delete it when it's working.

2. find the component with this file, and clear its key path.

3. in general case there could be yet another way: if self-repair was triggered by launching an advertised shortcut, then replacing it with a regular shortcut to the main executable  of the program would also work.

For this case, yet another, somewhat advanced way is described in my article "How to disable Installer self-repair for particular product"

0
 
Vadim RappCommented:
The correct link in the above comment is
http://www.vadimrapp.com/article3.htm
0
 
James MurrellProduct SpecialistCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 6
  • 5
  • 4
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now