Here's one for you WinXP pros

[jadinolf]

I was messing around the other day and intentionally deleted a few .scr files since I don't use them.

Boy, did I get nailed. Windows griped that I had removed critical system files and that I should insert my Win XP Home SP2 CD. Sure, I'm running XP Home SP2 but the SP2 was downloaded from the net (I have the SP2 disk now). Well, Windows would not buy my Windows SP1 CD OR my SP2 disk so I had to give up. I ran sfc /scannow instead and I don't know if it did anything or not.

May I assume that there is no way around this problem?

I'll be a good boy in the future. :laugh:

 

[jadinolf]

Stumped you,eh?

Don't blame you.

I think I'll talk to Microsoft if no one here has any ideas.

 

[LiLithTecH]

With Windows XP SP2 Advanced security policy, .SCR files are System Protected
(secured) much the same as TXT, VBS and EXE files since they are the easiest
way to infect a PC.

 

[bsobel]

Go to your system install directory, servicepackfiles\i386 and then copy the files you nuked back from there.

Bill

 

[xtknight]

Your system won't be damaged from deleting scr files. Don't even worry about it. You can also hex-edit out the annoying WFP protection.

 

[bsobel]

Originally posted by: xtknight
Your system won't be damaged from deleting scr files. Don't even worry about it. You can also hex-edit out the annoying WFP protection.

:roll: While your right it won't cause any damage, the solution is NOT to turn off WFP.

 

[jadinolf]

Well, that was it. They were some of the larger .scr files.

I appreciate the education. Thanks a bunch, all of you.

I going to pass this along to a friend who asked why .scr file removal who cause Windows to react.

 

[jadinolf]

Originally posted by: bsobel
Go to your system install directory, servicepackfiles\i386 and then copy the files you nuked back from there.

Bill

I was just thinking... I have three computers so I could have copied the files from them.

Oh well, moot point.