Quirky issue with copying sysinternals to System32

So I usually copy the sysinternals suite to /windows. This in order to make it easy to use the tools in bat files and soI can quickly open them. Anyways in win 7 I didnt have a problem with this.

In win 8 I had some issues copying these files to %windir% but system32 was fine. I think this was due to my av (agnitum) preventing this. Not sure though. Anyways, now when some of the tools are updated I try to copy the whole suite again. Only it only works with overwriting the previous files if I copy over 1 file at a time. Sometimes it seems to work if I pull over 5-10 a time. But always works 1 at a time. This is one of the weirdest issues I have encountered. And yes, while doing this my av is disabled.

Any input as to why this happens?

Hi Knowhere,

Is it a steadfast requirement to try and move that sysinternals suite to the system32 folder? The reason I'm asking is because I use many of the suite's individual offerings and they work perfectly when run from a non-system folder (eg, downloads folder). If not, then I don't see any logical reason to attempt what you are doing. So, am I missing something here?

You should not be putting anything in the Windows system directories. It would be much better to put your third party command line tools in C:\bin and add it to your PATH. For example, I put all the Sysinternals tools in C:\bin\Sysinternals, and I have a bunch more portable tools in C:\bin, which I copy onto all my machines.