mqh7 Posted March 26, 2014 Report post Posted March 26, 2014 I am posting this here since I did not know where to post this. And I know there are some smart people on this site so here goes..... We have windows XP machines. I am not able to copy a .SCR file to the c:\windows\system32 folder or anyplace on the drive, not even c:\Temp. No matter what I do I can't. I've tried the following.Rename the file to SC.SC1copy sc.sc1 to c:\windows\system32 (this works)ren sc.sc1 sc.scr fails. error renaming file or foldercannot rename sc.sc1: access is deniedmake sure the disk is not full or write-protected and that the file si not currently in use.I have tried pushing out sc.scr using SCCM 2007 which runs in the System Account. That failsI have tried pushing out a .CMD file using SCCM 2007. This .CMD file has the following ECHO OFFcopy %~dp0*sc.sc1 "c:\windows\system32" /yc:cd\cd windows\system32ren sc.sc1 sc.scrThis fails too.I have taken my XP machine and placed it into it's own OU within AD. I have blocked all other GPO's from running. I have logged into this XP machine as an Admin and run GPRESULTS /Z NO GPO'S ARE BEING APPLIED !! Yet I still can't rename this file. I CAN copy other files to C:\windows\system32. I can create Foldes there I can create .TXT files. I can actually create or copy .EXE files to C:\windows\system32, just not .SCR files. I checked to see if it was Firewalls or McAfee and it is not. What can prevent this? is it a REG key? if so which one? Quote Share this post Link to post Share on other sites More sharing options...
mqh7 Posted March 27, 2014 Report post Posted March 27, 2014 I removed my machines from the domain and I still can't copy a .SCR file to my hard drive. so it is not any policy or login script. Something changed in the registry or local security. and speaking of local security I did not find anything in the Local Security Policy. Quote Share this post Link to post Share on other sites More sharing options...
mqh7 Posted March 27, 2014 Report post Posted March 27, 2014 It was an anti-virus policy that prevented this. so it is fixed. Quote Share this post Link to post Share on other sites More sharing options...