Registry keys missed on Win 64, but not Win 32 - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

AndrewDover
Posts: 3
Joined: Sun Jun 26, 2011 1:34 am

Registry keys missed on Win 64, but not Win 32

I have a pretty simple install problem and have been using the freeware version so far.
A executable in a Application directory.
A CSP DLL which needs to go into windows\system
Three registry entries
HTLM\Software\Microsoft\Cryptography\Defaults\Provider\csp_http\Type=1
HTLM\Software\Microsoft\Cryptography\Defaults\Provider\csp_http\SigInFile=1
HTLM\Software\Microsoft\Cryptography\Defaults\Provider\csp_http\Image Path= path to the DLL

the MSI works on a Windows7 32 bit system, but does not install the registry keys on a Windows 7 64 bit system.

Now perhaps I need the Professional version, but what worries me is that I saw no error, just a normal install.
The verbose log in the area of the three Registry keys is shown below:

I saw something about "WIN64DUALFOLDERS: Substitution in 'C:\Program Files (x86)\Daon\csp_http\InitUtil.exe' folder had been blocked by the 1 mask argument (the folder pair's iSwapAttrib member = 0).", which I don't understand, but might be relevant.

{{{{{{{{{{{{{{{{

Action 20:27:00: ProcessComponents. Updating component registration
MSI (s) (D8:70) [20:27:00:406]: Executing op: ProgressTotal(Total=6,Type=1,ByteEquivalent=24000)
MSI (s) (D8:70) [20:27:00:406]: Executing op: ComponentRegister(ComponentId={EADA360A-CB43-4619-89DA-FF25B2121DFE},KeyPath=02:\Software\Microsoft\Cryptography\Defaults\Provider\csp_http\Type,State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)
1: {063C79C4-2827-4DAA-916A-64BC29A7C248} 2: {EADA360A-CB43-4619-89DA-FF25B2121DFE} 3: 02:\Software\Microsoft\Cryptography\Defaults\Provider\csp_http\Type
MSI (s) (D8:70) [20:27:00:407]: Executing op: ComponentRegister(ComponentId={865E4A4E-3564-476F-BDC7-2DA4CDF7CBCC},KeyPath=C:\Program Files (x86)\Daon\csp_http\InitUtil.exe,State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)
1: {063C79C4-2827-4DAA-916A-64BC29A7C248} 2: {865E4A4E-3564-476F-BDC7-2DA4CDF7CBCC} 3: C:\Program Files (x86)\Daon\csp_http\InitUtil.exe
MSI (s) (D8:70) [20:27:00:408]: WIN64DUALFOLDERS: Substitution in 'C:\Program Files (x86)\Daon\csp_http\InitUtil.exe' folder had been blocked by the 1 mask argument (the folder pair's iSwapAttrib member = 0).
MSI (s) (D8:70) [20:27:00:409]: Executing op: ComponentRegister(ComponentId={7C08E492-B346-4A6E-98FC-0C826EE35D34},KeyPath=C:\Windows\SysWOW64\csp_http.dll,State=3,,Disk=1,SharedDllRefCount=1,BinaryType=0)
1: {063C79C4-2827-4DAA-916A-64BC29A7C248} 2: {7C08E492-B346-4A6E-98FC-0C826EE35D34} 3: C:\Windows\SysWOW64\csp_http.dll
MSI (s) (D8:70) [20:27:00:410]: WIN64DUALFOLDERS: 'C:\Windows\system32\' will substitute 20 characters in 'C:\Windows\SysWOW64\csp_http.dll' folder path. (mask argument = 1, the folder pair's iSwapAttrib member = 1).
MSI (s) (D8:70) [20:27:00:410]: WIN64DUALFOLDERS: 'C:\Windows\system32\' will substitute 20 characters in 'C:\Windows\SysWOW64\csp_http.dll' folder path. (mask argument = 1, the folder pair's iSwapAttrib member = 1).
MSI (s) (D8:70) [20:27:00:410]: Executing op: ComponentRegister(ComponentId={9F15A856-DA1A-4B3F-9439-FFCC8E8480C0},KeyPath=02:\Software\Microsoft\Cryptography\Defaults\Provider\csp_http\Image path,State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)
1: {063C79C4-2827-4DAA-916A-64BC29A7C248} 2: {9F15A856-DA1A-4B3F-9439-FFCC8E8480C0} 3: 02:\Software\Microsoft\Cryptography\Defaults\Provider\csp_http\Image path
MSI (s) (D8:70) [20:27:00:411]: Executing op: ComponentRegister(ComponentId={875D73C4-07E2-41F2-B0BC-BC613147DEEC},KeyPath=02:\Software\Microsoft\Cryptography\Defaults\Provider\csp_http\SigInFile,State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)
1: {063C79C4-2827-4DAA-916A-64BC29A7C248} 2: {875D73C4-07E2-41F2-B0BC-BC613147DEEC} 3: 02:\Software\Microsoft\Cryptography\Defaults\Provider\csp_http\SigInFile
MSI (s) (D8:70) [20:27:00:412]: Executing op: ComponentRegister(ComponentId={69E3C178-694E-4F29-9DCE-9C528D638A01},KeyPath=02:\Software\Wow6432Node\Microsoft\Cryptography\Defaults\Provider\csp_http\Type,State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)
1: {063C79C4-2827-4DAA-916A-64BC29A7C248} 2: {69E3C178-694E-4F29-9DCE-9C528D638A01} 3: 02:\Software\Wow6432Node\Microsoft\Cryptography\Defaults\Provider\csp_http\Type
MSI (s) (D8:70) [20:27:00:413]: Executing op: ProgressTotal(Total=1,Type=1,ByteEquivalent=13200)
MSI (s) (D8:70) [20:27:00:414]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs,,BinaryType=0,,)
MSI (s) (D8:70) [20:27:00:414]: Executing op: ProgressTick()
MSI (s) (D8:70) [20:27:00:414]: Executing op: ActionStart(Name=RemoveODBC,Description=Removing ODBC components,)
Action 20:27:00: RemoveODBC. Removing ODBC components
}}}}}}}}}}}}}}}}

Any hints appreciated.

best regards,
Andrew
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Registry keys missed on Win 64, but not Win 32

Hi Andrew,

Please note that 32-bit installers use the 32-bit registry hive on a 64-bit machine. So your entries are placed in Wow6432Node key. This is the normal behavior and it doesn't affect your application functionality.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
AndrewDover
Posts: 3
Joined: Sun Jun 26, 2011 1:34 am

Re: Registry keys missed on Win 64, but not Win 32

Yes, I had considered the Wow6432Node last night, but when I looked using regedit directly after the install last night, there was nothing in Wow6432Node under that key.

This morning, after the Windows 64 bit machine had been powered off overnight, the keys appeared. And this morning, I can see the registry keys under Wow6432Node appear and be removed using regedit.

Either there was some reboot event, or I could have made some mistake last night trying to look at Wow6432Node.

Anyhow, it worked now. Many thanks, and congratulations on a great product.

Return to “Common Problems”