Can't copy a file to system32 on Windows 7
Is this folder protected or something? I can copy it if I Manually do it from a CMD window but I can't do it from a script. What gives?
Answers (10)
I've even written a small .CMD file that does the copy. I put a PAUSE statement into my .CMD file and ran it in "Normal" view so I can see it. Wise kicks off the .CMD file, I see that the file WAS COPIED. But when I look in c:\windows\system32 the .DLL is NOT there.
So the .CMD file says it copied the file yet the .DLL is not in the \system32 folder.
Not sure what else to try?!?!
Thanks.
Comments:
-
try to Use SYSNATIVE .... - mahendraKumar 12 years ago
When you run your MSI, it will run in Win 32 shell so it will show you that it is copying it to system32, but in actual, in Win32 shell Syswow64 is the system32 folder and hence it is getting copied to syswow64 folder.
I recommend you to read my article here for better understanding:
http://msiworld.blogspot.com.au/2011/09/creating-msi-for-x64-and-x86-machines.html
You will need to upgrade your WISE package Studio to use it for 64 bit.
This is a Windows* OS/file system issue.The cause is
the directory paths in the system is longer than 255 characters (including spaces).You may see the error "Can't copy or delete file.".The fully qualified file
name must be less than 260 characters, and the
directory name must be less than 248 characters,"
under the following circumstances:Opening an assembly with .NET ReflectorExporting source code for an assembly using an add-in such as FileDisassembler,or
FileGenerator.There's a lot of additional softwares
which can fix this problem like Long Path Tool.
http://PathTooDeep.com
Long Path Tool can simplify and probably end your
problems in unlocking, managing and renaming files
that appear to have a long filename.