10-10-2011 07:43 AM - edited 10-10-2011 07:46 AM
Hi Everyone,
I am receiving the above error on my Windows XP 32-bit laptop this morning. The "fix" is to run Live Update until it completes successfully, then reboot. Unfortunately, the error still persists.
I am at a loss at this point and considering uninstalling/reinstalling NIS 2012.
Any other thoughts?
-Wayne
Norton Internet Security 19.1.1.3 Error: 3043, 1 Microsoft Windows XP 2600.xpsp_sp3_gdr.101209-1647 Norton Autofix Results: 1 item(s) Installation :: FailedSolved! Go to Solution.
10-10-2011 08:10 AM
Hi Wayne,
Since running LU did not work for you, unfortunately the next step would be uninstall & reinstall of the product.
Refer to this link on how to go ahead with this.
But before doing that, just try to run the live update again after restarting your machine.
Let us know if that works.
Regards,
Prasanna.
10-10-2011 09:42 AM
Prasanna,
Re-running LU did not work. I had to uninstall/re-install the NIS 2012. I am back to a green checkmark.
Regards,
-Wayne
10-10-2011 09:45 AM
Hi,
Great to know its solved now.
Regards,
Prasanna.
10-10-2011 10:04 AM
Hello Wayne
Would you please mark the post which gave you the solution so we may know that this thread is solved.? Marking the correct post will help others looking for the solution to their problem. Thanks.
Success always occurs in private and failure in full view.
10-10-2011 10:24 AM
Hello,
Could you please collect the install logs folder and attach it here? That will help us determine what might be causing your error.
On XP the default location is:
C:\Documents and Settings\All Users\Application Data\NortonInstaller\Logs
Thanks.
10-10-2011 11:27 AM
Hello aric_brown
The original poster's problem has been fixed by reinstalling the program. Do you still want the logs from the working program? Are the previous install logs still there from the first install of the program if the program had been uninstalled first and then reinstalled?
Success always occurs in private and failure in full view.
10-11-2011 10:50 AM
10-11-2011 10:52 AM
Hi,
I am glad the issue was resolved. By collecting the Logs, which should still be there, we can better understand what caused the issue, and try to prevent it from happening again in the future.
Thanks.
