disable_wow64_fs_redirection not applying to check_file ?

52 views
Skip to first unread message

Brian Hanson

unread,
Mar 21, 2016, 12:00:57 PM3/21/16
to dotnetinstaller
On a 64bit Windows 10 system, I have created a simple configuration to copy over some PowerShell Modules (as an example installer).
Example:

Command component:
xcopy "#CABPATH\Scripts\Profile.ps1" "#SYSTEMPATH\WindowsPowerShell\v1.0" /y

works correctly and file is copied to "C:\Windows\System32\WindowsPowerShell\v1.0"

However file_check (exists) of "#SYSTEMPATH\WindowsPowerShell\v1.0\Profile.ps1" reports "not installed"

The file exists and is viewable (not hidden).
WoW64 Redirection fails on file checks.PNG

Brian Hanson

unread,
Mar 21, 2016, 1:56:52 PM3/21/16
to dotnetinstaller
Some additional information:
Enabling or disabling wow64_fs_redirection on the "Install" or individual component (or both) does not change check_file redirection.
It appears to always check the "C:\Windows\SysWOW64" folder for installed file.
The log output always reports "C:\Windows\System32".

Also hard coding the check_file path with "C:\Windows\System32" instead of using #SYSTEMPATH will result in the same issue.

Any help with this matter is greatly appreciated.

Daniel Doubrovkine

unread,
Mar 22, 2016, 1:09:38 PM3/22/16
to dotneti...@googlegroups.com
You'll have to debug this one, I don't see immediately why it wouldn't work.

--
You received this message because you are subscribed to the Google Groups "dotnetinstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dotnetinstall...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--

dB. | Moscow - Geneva - Seattle - New York
code.dblock.org - @dblockdotorg - artsy.net - github/dblock

Rami AbuGhazaleh

unread,
Aug 9, 2019, 5:02:03 PM8/9/19
to dotnetinstaller

Thank you.


On Tuesday, March 22, 2016 at 10:09:38 AM UTC-7, Daniel D. wrote:
You'll have to debug this one, I don't see immediately why it wouldn't work.
On Mon, Mar 21, 2016 at 1:56 PM, Brian Hanson <brian.ha...@gmail.com> wrote:
Some additional information:
Enabling or disabling wow64_fs_redirection on the "Install" or individual component (or both) does not change check_file redirection.
It appears to always check the "C:\Windows\SysWOW64" folder for installed file.
The log output always reports "C:\Windows\System32".

Also hard coding the check_file path with "C:\Windows\System32" instead of using #SYSTEMPATH will result in the same issue.

Any help with this matter is greatly appreciated.


On Monday, March 21, 2016 at 9:00:57 AM UTC-7, Brian Hanson wrote:
On a 64bit Windows 10 system, I have created a simple configuration to copy over some PowerShell Modules (as an example installer).
Example:

Command component:
xcopy "#CABPATH\Scripts\Profile.ps1" "#SYSTEMPATH\WindowsPowerShell\v1.0" /y

works correctly and file is copied to "C:\Windows\System32\WindowsPowerShell\v1.0"

However file_check (exists) of "#SYSTEMPATH\WindowsPowerShell\v1.0\Profile.ps1" reports "not installed"

The file exists and is viewable (not hidden).

--
You received this message because you are subscribed to the Google Groups "dotnetinstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dotneti...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages