Community Forums
Page 1 of 2 12 LastLast
Results 1 to 5 of 6

Thread: Installing a 64-bit software created is not putting entry in corresponding registry.

  1. #1
    Join Date
    Mar 2017
    Posts
    3

    Smile Installing a 64-bit software created is not putting entry in corresponding registry.

    Hi,

    So, I've been using Install shield to create a setup file. It is a 64-bit setup file(FYI : it has some 32 bit exes in it). On installing this setup, its getting properly in the destined location ("C:\<Software_Name>\"). But, on checking the registry path, its getting registered in the below path

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432NodeMicrosoft\Windows\CurrentVersion\Uninstall\
    which is 32 bit software path where it actually should have been registered under 64 bit path

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
    I built 32-bit setup file for the same software and entry is getting registered on the same location(this one is normal behavior off course).

    Can someone clear me my following doubt on this

    1. Is setting a registry location done within Install shield by default or explicitly?
    2. If explicitly, Should registry location be decided by us during building in install shield or somewhere else?
    3. If we provide somewhere else explicitly, what would happen to the 32-bit registry location created in my case?


    Any sort of guidance on this is much appreciated. Thanks in Advance.

  2. #2
    chad.petersen Guest
    The Uninstall key is being created by the 32-bit MSIEXEC.EXE process that is spawned when you run your MSI. So, you won't have any control over that location.

    Otherwise, I almost never specify Wow6432Node but instead let MSI decide for me based off of whether the Component is set to 64-bit or not. If the "64-Bit Component" is set to "Yes" it will write to 64-bit registry locations and if the "64-Bit Component" is set to "No" then it will write to 32-bit registry locations.

    I hope that helps

    Chad

  3. #3
    chad.petersen Guest
    As I thought about what you said a little bit more I realized you'd need a 64-bit installer to do what you want. That should go to the 64-bit Uninstall section.

    I tried it and it seemed OK to me. I did have to set my Template Summary to

    x64;1033

    In the General Information view, Summary Information Stream section, set the Template Summary property to x64;1033. Note: If you live in a country where English is not the language, you will use a different language code from 1033.

    That might be all it is. If you already have that set then watch in Task Manager as you run your installer and make sure it doesn't spawn an MSIEXEC.EXE *32, but only MSIEXEC.EXE and it should work correctly in that situation.

    Sorry about misunderstanding initially.

    Chad

  4. #4
    Join Date
    Mar 2017
    Posts
    3

    Red face

    Quote Originally Posted by chad.petersen View Post
    As I thought about what you said a little bit more I realized you'd need a 64-bit installer to do what you want. That should go to the 64-bit Uninstall section.

    I tried it and it seemed OK to me. I did have to set my Template Summary to

    x64;1033

    In the General Information view, Summary Information Stream section, set the Template Summary property to x64;1033. Note: If you live in a country where English is not the language, you will use a different language code from 1033.

    That might be all it is. If you already have that set then watch in Task Manager as you run your installer and make sure it doesn't spawn an MSIEXEC.EXE *32, but only MSIEXEC.EXE and it should work correctly in that situation.

    Sorry about misunderstanding initially.

    Chad
    Hi Chad,
    Thanks for the heads up. This information is very useful. However, I am in need of a script which automates this work. i.e., change the template summary property using script. Is there any possibility for that. Thanks in advance.

  5. #5
    chad.petersen Guest
    No, an installer is either compiled as 32-bit or 64-bit. Once compiled you cannot change the bit type on the fly.

    Chad

Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •