NIS2013 on XP SP3: virus & spyware definitions are not up-to-date, 'Fix Now' doesn't

I upgraded from NIS2012 to NIS2013 on 3 PC's today.  All went fine on the Win 7 & Vista machnes but not so fine on the XP SP3 machine.

 

The upgrade went ok, but on performing the first manual 'Live Update' (which worked fine), NIS then decided that my computer was at risk 'Your Virus & spyware definitions are not up-to-date. Your PC may be at risk of infection.'

 

Clicking on the 'Fix Now' button ran a 'Live Update' which worked ok, but 'Fix Now' then says 'Fix not complete, Protection Updated Not Fixed'.

 

Have tried a reinstall of NIS2013 (including the Norton Removal Tool), but the same happens again on the reinstall.

 

Found a thread on this forum suggesting that I should try a live update with AntiSpam turned Off. (Settings->Antispam->Norton AntiSpam->Off), but that didn't help (Live Update worked, but NIS still wasn't fixed).

 http://community.norton.com/t5/Norton-Internet-Security-Norton/Live-Update-fails-crashes-after-upgrade-from-NIS-2012-to-NIS/td-p/801224

 

Reverting back to NIS2012 unless anyone has any better ideas.  Thanks in advance ;)

The logfile from CHKDFK /V:

 

WARNING!  F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
Detected minor inconsistencies on the drive.  This is not a corruption.
CHKDSK is recovering lost files.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Cleaning up 2 unused index entries from index $SII of file 9.
Cleaning up 2 unused index entries from index $SDH of file 9.
Cleaning up 2 unused security descriptors.
Security descriptor verification completed.
CHKDSK is verifying Usn Journal...
Repairing Usn Journal file record segment.
Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

Hi! MarkBevan,

 

Please type in CHKNTFS /D and press enter.  If no error message appears type in exit then press enter an restart the computer. Let me know when your back at the desktop.

 

Tech83  :)

CHNTFS /D produced no error messages (nor anything else).  I have restarted & I'm back at the deskop.

Excellent! MarkBevan,

 

Now let's see if CHKDSK /V in the command prompt returns any errors this time.  If it does it may need to be run in Safe Mode.

 

Tech83  :)

The CHKDSK /V result:

 

WARNING!  F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
Detected minor inconsistencies on the drive.  This is not a corruption.
CHKDSK is recovering lost files.
Recovering orphaned file tmp.edb (10877) into directory file 10433.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Cleaning up 2 unused index entries from index $SII of file 9.
Cleaning up 2 unused index entries from index $SDH of file 9.
Cleaning up 2 unused security descriptors.
Security descriptor verification completed.
CHKDSK is verifying Usn Journal...
Repairing Usn Journal file record segment.
Usn Journal verification completed.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

MarkBevan,

 

Please boot the computer into Safe Mode (with command prompt option) and re-run the CHKDSK /V and let me know the results; need to determine if the bitmap errors are being falsely reported or are actually present errors.

 

Thanks for your patience,

 

Tech83  :)

Hi MarkBevan,

 

I'm not very good with computers so I can't quite understand those messages on this CHKDSK thingy, this may also be simple but I just would like to check if the date and time on your computer is correct? Because when I had the error message (not with 2013 but older versions) the time and date is not correct.

 

Just an input, it might be of help. :smileywink:

Hi! Charie22,

 

MarkBevan's system is reporting errors in the Volume Bitmap & the Master File Table or MFT; these errors if they are not being falsely reported by Check Disk (which can occur sometimes when Windows is in normal mode) can lead to massive data loss and corruption causing the system to ultimately crash if they are not corrected.

 

Tech83  :)

The result of CHKDSK /V in safe mode;

 

Cleaning up 3 unused index entries from index $SII of file 9.

Cleaning up 3 unused index entries from index $SDH of file 9.

Cleaning up 3 unused security descriptors.

 

I have a couple more basic Windows installs on this machine if you need them (just for safetys sake, in case I ever can't boot the main one).

 

Thanks v much for your help :)

MarkBevan,

 

What other Operating Systems do you have on your computer?

 

Tech83  :)

Just 3 Win Xp installs.  The main one which is at XP3 and is used for everything.  The other two are just basic unpatched installs, in case I even had problems with the main install (one on each physical hard drive).

Okay.  Do you have the Windows XP installation disc or is it a recovery disc?

 

Tech83  :)

I have the XP installation disc.

MarkBevan,

 

Please boot the affected computer from the installation disc & select the option to Repair (this should bring up the Recovery Console).  Then select your main XP installation.  Let me know when your at the prompt.

 

Tech83  :)

 Am I in any danger of losing data or programs here ?

MarkBevan,

 

Negative; I've performed the steps I'm about to provide you on my own system and others numerous times without any data loss but if you would feel more comfortable you can move your personal files to one of the other XP installations on your computer.

 

Tech83  :)

To follow up on what charie22 posted earlier, is the system date correct?  An incorrect date can cause the sort of definitions errors that were being reported.

 

I'm not getting the option to bring up the recovery console.  It's going straight into Windows Setup.


SendOfJive wrote:

To follow up on what charie22 posted earlier, is the system date correct?  An incorrect date can cause the sort of definitions errors that were being reported.

 


Hi! SendOfJive,

 

How many systems have you encountered that have Volume Bitmap an MFT Bitmap errors brought on by incorrect date/time settings?  This is something to be learned and tucked away for future reference. :)

 

Tech83  :)