Probs with usage of <SystemDir64>

Common questions about using Actual Installer.
Post Reply
Posts: 7
Joined: Tue Dec 08, 2020 10:09 am

Probs with usage of <SystemDir64>

Post by UFa »

I need to copy some DLL files to the Windows\SysWOW64 folder and other DLLs to Windows\System32 as part of the installation.
Here I used the installer variables <SystemDir> for the "SysWOW64" folder and <SystemDir64> for the "System32" folder. Note: the "Requirements \ Operating System" option is NOT set to "64-bit only".

When I first copied DLL files to <SystemDir> only, the installer correctly copied the DLLs to "SysWOW64".
Now after additional use of <SystemDir64> ONLY these DLL files for "SysWoW64" are copied to "System32", the files intended for SysWOW64 are not copied to this destination at all.

What is also very important to know: the DLLs, which are copied into the two folders "SysWOW64" and "System32", have partly the same file names. This is because it is once the 32bit and once the 64bit version of the DLL.

What is going wrong and how to tackle the problem?
Posts: 8
Joined: Fri May 14, 2021 7:55 pm

Re: Probs with usage of <SystemDir64>

Post by AKP »

I think the best would be an option option at each file: only 32bit / only 64bit / all
So an installation for both systems together would be possible.
Site Admin
Posts: 409
Joined: Fri Jan 22, 2010 12:40 pm

Re: Probs with usage of <SystemDir64>

Post by Leo »

It happens because of the Windows' system WOW64.
Even if you specify "C:\Windows\System32", and the option "64-bit only" is not selected, the files go to "C:\Windows\SysWOW64".
More info here: ... ndows.html

You can use the path: <WindowsDir>\sysnative
Actual Installer Team
Post Reply