Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to browse to 64bit System32 for manual file select #13

Open
theultramage opened this issue Apr 24, 2021 · 2 comments
Open

Unable to browse to 64bit System32 for manual file select #13

theultramage opened this issue Apr 24, 2021 · 2 comments

Comments

@theultramage
Copy link

theultramage commented Apr 24, 2021

The patcher could not auto-find the activeX flash ocx files on my system because I installed latest version 465 and Patches.cs only knows 445. So I proceeded to manually select the files using the classic explorer file open dialog. However I could not access the 64bit one because both System32 and SysWoW64 led to the same 32bit macromedia folder. I assume this dialog needs wow64 redirection turned off. (As a workaround, I temporarily moved the file to a more convenient location for patching.)

@darktohka
Copy link
Owner

Unfortunately, it looks like we cannot disable wow64 redirection on this dialog. Windows doesn't support this behavior.

I'll release FlashPatch version 1.6 with Any CPU configuration, see if that does anything?

@theultramage
Copy link
Author

No noticeable difference, it still runs as a 32-bit windows executable. But now that the latest activex version is auto detected, this is no longer a big issue.
It is too bad that the behavior cannot be changed for the dialog. One additional workaround I found is that the dialog supports the 'SysNative' pseudo folder name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants