I believe this scenario is just specific to an environmental difference on your specific machine. (mlopezjr was able to show this by his clean OS working fine) I'm suggesting MSConfig to help rule out other applications and services that we are unaware of that may be causing a possible conflict here.
Hi, I have exactly the issues described by the others above..
I have tried a number of things - including all the suggestions in this thread and have been online via chat with Support on several occasions..
The only thing that I have not tried as yet is to re-install the OS...but that is not really something that I'm willing to do at this point.
Given the version 1.x installs and works without issue , can someone make any suggestions as to what component of ver 2.x could be the source of the problem here..There are clearly a number of people seeing very similar issues so there must be a conflict somewhere - however given that I have tried to install without loading any Services other than MS ones and also without loading any start-up apps I don't know where to start in terms of getting to a root cause...
I'm running Windows XP Pro, SP3
All suggestions welcome..
Thanks
Message Edited by eannalennon on 10-08-2008 12:17 PM
The error is always the same ,the only variable is the name of the offending EXE file - Variously it will be MainStub.exe , Scanstub.exe , CCapp.exe , OScheck.exe and once the error occurs No symantec product will run - e.g If I try to run NRT I'll get the app error for SymNRT.exe
Can you launch any other EXE application installs? I’m almost suspecting a possible threat at this point, if only Symantec signed applications are being prevented from running.
Anyone ever figure out a good fix besides reinstalling the OS?
I have the same problem others do, failed to initialize messages, all the norton EXEs show that same behaviour but all other applications seem to work fine.
Other PCs I have upgrade fine, but this one PC I have just wont do it.
I am going to isolate this PC in case anyone wants any info to try and fix this problem.