Restart loop after NIS update on Win XP

Hello. My PC running Windows Xp is on a continues loop of restarting after latest NIS update. It boot ups , goes on user selection screen, you select the user and after few min getting a message that windows suffered serious error and asking to send the report on windows part, which is all fine, but after another min or so it just restarts again. Pc is running Windows Xp sp3 32 bit, had the NIS version 20.2.0.19 and was updated by itself. Not sure if this related but another PC is running windows 7 64bit, I have asked Tony for the latest patch and updated NIs on this PC to NIS version 20.2.1.22. Maybe Norton account  seen one PC running later version and tried to update the other one, but why would it cause continues reboot?

Hi again. I cannot check what version its running, as the minute I click on NIS restart will happen. I know its NIS update that caused this, as   I uninstalled NIs in safe mode, restarted and no more continuous restarts. The minute I installed NIS and updated it , restarts started. So for now am going to uninstall, but do hope Symantec will look into this problem.

Hello. My PC running Windows Xp is on a continues loop of restarting after latest NIS update. It boot ups , goes on user selection screen, you select the user and after few min getting a message that windows suffered serious error and asking to send the report on windows part, which is all fine, but after another min or so it just restarts again. Pc is running Windows Xp sp3 32 bit, had the NIS version 20.2.0.19 and was updated by itself. Not sure if this related but another PC is running windows 7 64bit, I have asked Tony for the latest patch and updated NIs on this PC to NIS version 20.2.1.22. Maybe Norton account  seen one PC running later version and tried to update the other one, but why would it cause continues reboot?

Hi, we are busy researching a possible issue matching your symptoms.

We will reply as as soon as we have or need more information.

 

Pieter

Thank you. I would forward you the crash log, but they were corrupted according to website that opens when you submit your issue.