forum.opsi.org

Hello,

While making update to one package, I have noticed, that I am copying files to SysWOW64 instead of System32.. It's really strange, I believe my package used to work well..

Testing system: Windows 7 x64
opsi-winst: 4.11.6.2

I used to do: but now, I find files in SysWOW64..

Even after: I find files in SysWOW64, although in install logs I see:
Source blahblah copied to C:\windows\System32\
1 File(s) treated

Would be thankful for any ideas..

Hi,

could the files you find be a leftover from previous installation attempts?
Or has the client been setup with a fresh Windows install before?

The documentation has an description of how things are working.
First paragraphs look to me exactly like the problem you are facing.
Does this chapter help you?


Kind regards

Niko

Hi,

every thing is ok and works correctly.
Please read:
http://download.uib.de/opsi_stable/doc/ ... inst-64bit
why it not work like you expected.

regards
d.oertel

On Windows x64, SysWOW64 is actually the path for 32-Bit system files, while System32 is the path for 64-Bit system files. WOW = windows on windows, means they emulate 32-Bit on a 64-Bit system for 32-Bit compatibility.
While the naming is definetly suboptimal, my guess is they did this to keep the native system files in place where everyone got used to after all these years.

This article might give some insight.

Thank you for the explanations