Advanced Installer don't read the x64 registry

[Edtech]

Hi !

I check in the Prerequisites a value in the registry (this key : HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL). If the OS is x86, I found correctly the key but if the OS is x64, the test read the key in WoW64 and not in the current registry, and fail.
I try to change the package to 64 bits, but the registry used is still the WoW64 and not the current x64.

Could you add an option to select if the registry used is x64 or x86 ?

Best regards.

[mihai.petcu]

Hello,

You can try to mark the prerequisite as 64-bit from its Properties tab. Also, if you have the same prerequisite as x86 you can add it separately in the prerequisite list.

All the best,
Mihai

[kkrzyzak]

Hi Edtech,

The HKEY_LOCAL_MACHINE\Software\Wow6432Node is the 32-bit equivalent of HKEY_LOCAL_MACHINE\Software .

Best reg.,
Karol.

[ans]

I am having the same problem: I can't seem to write any key to the regular (64 bit) registry under HKLM\Software. No matter what I do, my registry keys always end up in HKLM\Software\Wow6432Node\...., which is the "virtual" branch for 32 bit apps. I am currently evaluating the trial, testing a "Professional" type project.

It should be possible for a pure x64 MSI package to write to the regular x64 branch of the registry.

If I am not missing something, this is a bug. At least this renders Advanced Installer pretty useless for x64 products.

[mihai.petcu]

Hello,

Thank you for your interest in Advanced Installer.

Aside setting a 64-bit package type from the Install Parameters page, the registry entries' components( find them by pressing F8 while they are selected in the Registry page ) must also be marked as 64-bit from the Organization page.

All the best,
Mihai

[ans]

Thank you, Mihai. That indeed did the trick.

Feature Request: It would be great if AI could look into the file and determine the 32/64 bit automatically. Or at least assume 64 bit status by default in a pure 64 bit package. Or: Have a check mark in the properties dialog of a registry key that uses a file as a value.

Other than on Mac OS X, on Windows we don't have universal binaries (multiple CPU architectures in same file), which complicates the file organization a lot. Every feature that can ease this a bit is very welcome.

[Cosmin]

Hi,

It would be great if AI could look into the file and determine the 32/64 bit automatically. Or at least assume 64 bit status by default in a pure 64 bit package. Or: Have a check mark in the properties dialog of a registry key that uses a file as a value.

I added this improvement on our TODO list and it will be available in a future version. Thank you for your suggestion.

Regards,
Cosmin

[Edtech]

Ok, thanks. Sorry for my late answer ^^

Another suggestion : when adding a prerequisite, give the choice between the x86 and x64 version. I have this problem with SQL Server 2008 R2 SP1. This new version don't have mixed package installation. It's only full x86 or full x64. Advanced Installer have only one choice with a link to the mixed version x86 + x64...

[mihai.petcu]

Hi,

You can try to mark the prerequisite as 64-bit from its Properties tab. Also, if you have the same prerequisite as x86 you can add it separately in the prerequisite list:
http://www.advancedinstaller.com/user-g ... rties.html

You will have to have different relevant launch conditions for each prerequisite( one for x86 package and the other for x64 package ):
http://www.advancedinstaller.com/user-g ... tions.html

All the best,
Mihai