Got this warning this morning...never seen this before...what do you think!!

Got his warning...never ran into this one before...what do you make of it!!

http://img.photobucket.com/albums/v611/rogval/Warning.jpg

Thanks
Roger

 

Something on your system replaced a protected file.

Your event viewer will show which file it is.

 

you could go "run" type "sfc /scannow" if you want to check them all I think I might

 

This has been known to happen with Office 2k, and Office XP, same for Win2k. The SFC /Scannow should hopefully work.

 

Thanks guys/gals!!!! I think i've got it under control...I ran the sfc/scannow command and while that was en-route, I had to put in the orginal XP SP2 cd and hit retry a million and a half times but it eventually made it through, and i'm assuming that it is taken care of!!??

The thing that gets me...how did it becomes compromised in the first place!!?? I am virus/spyware free and I haven't recently altered anything as far as install/un-installing anything...and i'm also behind a hardware and software firewall!!

Roger

 

It didn't get compromised, it worked how it should.

Windows "protects" certain core system files. If one of them is replaced or damaged, it will want to replace that file with the original, which is why it asks for your XP CD.

 

Ok...that makes me feel better!! I was under the impression that the only way a protected files such as...could only be damaged by virus/spyware problems!!

Another question though...when I did that sfc/scannow thing...should I have had to hit the retry so many times in order for it to complete the scan or is it setup to ask for your retry everytime it scans a file that needs to be replaced?? AS I said in a couple post back...I would have to hit "retry" a dozen times then it might scan for another 3-5 secs then the retry thing anothere dozen or so times then scans again for maybe 10-15 secs this time, then the retry thing again...and so forth and so-on!! Does that throw up any red flags or is that the way it works??

Roger

 

Nope, your source paths are messed up in the registry.

I'd check Event Viewer too, because there is a fair chance that it didn't copy the file you needed back over.

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup

There is a Sourcepath value, and a ServicePackSourcePath value. If you installed Windows XP from CD, Sourcepath should point to your CD drive. If you installed SP1/SP2 from CD, ServicepackSourcePath should point to your CD. Otherwise it should point to the location of the service pack files on your hard drive, which is usually C:\windows\servicepackfiles\i386. You would enter c:\windows\servicepackfiles however, because i386 is already implied, in both values.

 

I've set both values to what you suggest, yet when I run sfc /scannow I'm still asked to insert the CD.

 

Then you have set them incorrectly.

Post what you set them to.

 

I have Windows 2000. Both items are set to c:\winnt\ServicePackFiles. ServicePackSourcePath was already set to that.

 

Well there ya go. Thats not what I said. I said sourcepath should be set to the CD drive.

servicepackfiles directory only includes service pack files, not all of the system files.

 

You could also copy i386 from the CD to your C:\ drive and then set the sourcepath to C:\

 

Excellent Adrynalyn...you saved the day!! i'm glad I elaborated on my question!! I did like you said and went into the registry and checked the source path...and duh...stupid me...I had the cd in the wrong drive!! Put it in the specified sourcepath and fired off sfc /scannow, and it went all the way through without any problems/prompts, etc!!

* gotta defend myself here!! LOL*

I use my optical drives sooooo seldom, I never remember which one is which!! I just assumed that it would find the cd and use it...no matter what the sourcepath is!! Well...you know what happens when you assume.......

Thanks again all for the help!!

Roger

 

Glad to help

 

OK, I misunderstood what you said in the above. I thought you said I should enter the same thing for both values.