Re: [WiX-users] X64 Burn Bootstrapper
My install project has a 64bit cmdlet that must run from our custom Bootstrapper Application as well. Our BA is not managed, but I believe the same concept applies. You can get the install location of the 64bit PowerShell from the registry by ensuring that you open your registry key with the 64bit view (http://msdn.microsoft.com/en-us/library/microsoft.win32.registrykey.openbasekey, http://msdn.microsoft.com/en-us/library/microsoft.win32.registryview). The registry key for determining the location of Powershell.exe is here: Key: HKLM\SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine, Value: ApplicationBase (http://technet.microsoft.com/en-us/query/dd315312, http://tfl09.blogspot.com/2009/10/ensuring-powershell-is-loaded-onto.html). It turns out that this will still give you a wow64 redirected path to powershell. You can check if your BA is 32bit (you know it is) with IsWow64Process() (http://msdn.microsoft.com/en-us/library/windows/desktop/ms684139(v=vs.85).aspx). Then safely replace the System directory path from the registry, C:\Windows\SysWOW64 with the native 64 redirected path, C:\Windows\Sysnative (http://msdn.microsoft.com/en-us/library/windows/desktop/aa384187(v=vs.85).aspx). This path passed to ShellExecute would effectively start the 64bit powershell, combine that with a script or a set of commands and you've got a solution to your current 32bit BA woes. Hope that helps, Nate -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, June 27, 2012 2:59 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] X64 Burn Bootstrapper You'll have to proxy out to a 64-bit process. On Wed, Jun 27, 2012 at 7:17 AM, Henning Krause m...@henningkrause.euwrote: Since I'm in the context of Burn, I can't call CAQuietExec. I'm not running in any MSI context. That comes later... Henning -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Wednesday, June 27, 2012 3:56 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] X64 Burn Bootstrapper Hmmm. Generally, when I call applets I wrap them in C# or call them with CAQuietExec[64] because of this issue. The trick is that there are two powershell.exe's on a 64-bit system, and you get the 32-bit one by default. You're probably going to have to find a way to force the 64-bit powershell to be called or your context will be wrong. -- John M. Cooper -Original Message- From: Henning Krause [mailto:m...@henningkrause.eu] Sent: Wednesday, June 27, 2012 8:24 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] X64 Burn Bootstrapper Maybe my question was poorly phrased. I'm not running a custom action. My call to Get-WindowsFeature resides in a Managed Bootstrapper application (aka Burn). I haven't found a way to start the Bundle process as x64. Kind regards, Henning -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Wednesday, June 27, 2012 3:10 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] X64 Burn Bootstrapper You have to call with a 64-bit entry point. If you're using CAQuietExec, you need to be using CAQuietExec64 to execute in a 64-bit process. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.(r) Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Henning Krause [mailto:m...@henningkrause.eu] Sent: Wednesday, June 27, 2012 4:46 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] X64 Burn Bootstrapper Hi, as part of my managed bundle, I may need to activate certain Windows Features. Since I'm targeting Windows 2008 R2 or later, I can safely use the Add-WindowsFeature and Get-WindowsFeature cmdlets. The Add-WindowsFeature would be called from a custom action. However, I want to display a list of missing features to the user during the UI part of the Setup. For this I call the Get-WindowsFeature cmdlet in my managed bootstrapper. However, this fails, because the custom Bootstrapper application always seems to be 32bit. Unfortunately, the ServerManager PowerShell module is only available as 64bit. I've already tried to compile the whole setup solution as 64, but no avail. Is this scenario simply not possible or am I missing something? Kind regards, Henning -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond
[WiX-users] X64 Burn Bootstrapper
Hi, as part of my managed bundle, I may need to activate certain Windows Features. Since I'm targeting Windows 2008 R2 or later, I can safely use the Add-WindowsFeature and Get-WindowsFeature cmdlets. The Add-WindowsFeature would be called from a custom action. However, I want to display a list of missing features to the user during the UI part of the Setup. For this I call the Get-WindowsFeature cmdlet in my managed bootstrapper. However, this fails, because the custom Bootstrapper application always seems to be 32bit. Unfortunately, the ServerManager PowerShell module is only available as 64bit. I've already tried to compile the whole setup solution as 64, but no avail. Is this scenario simply not possible or am I missing something? Kind regards, Henning -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] X64 Burn Bootstrapper
You have to call with a 64-bit entry point. If you're using CAQuietExec, you need to be using CAQuietExec64 to execute in a 64-bit process. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.(r) Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Henning Krause [mailto:m...@henningkrause.eu] Sent: Wednesday, June 27, 2012 4:46 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] X64 Burn Bootstrapper Hi, as part of my managed bundle, I may need to activate certain Windows Features. Since I'm targeting Windows 2008 R2 or later, I can safely use the Add-WindowsFeature and Get-WindowsFeature cmdlets. The Add-WindowsFeature would be called from a custom action. However, I want to display a list of missing features to the user during the UI part of the Setup. For this I call the Get-WindowsFeature cmdlet in my managed bootstrapper. However, this fails, because the custom Bootstrapper application always seems to be 32bit. Unfortunately, the ServerManager PowerShell module is only available as 64bit. I've already tried to compile the whole setup solution as 64, but no avail. Is this scenario simply not possible or am I missing something? Kind regards, Henning -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] X64 Burn Bootstrapper
Maybe my question was poorly phrased. I'm not running a custom action. My call to Get-WindowsFeature resides in a Managed Bootstrapper application (aka Burn). I haven't found a way to start the Bundle process as x64. Kind regards, Henning -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Wednesday, June 27, 2012 3:10 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] X64 Burn Bootstrapper You have to call with a 64-bit entry point. If you're using CAQuietExec, you need to be using CAQuietExec64 to execute in a 64-bit process. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.(r) Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Henning Krause [mailto:m...@henningkrause.eu] Sent: Wednesday, June 27, 2012 4:46 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] X64 Burn Bootstrapper Hi, as part of my managed bundle, I may need to activate certain Windows Features. Since I'm targeting Windows 2008 R2 or later, I can safely use the Add-WindowsFeature and Get-WindowsFeature cmdlets. The Add-WindowsFeature would be called from a custom action. However, I want to display a list of missing features to the user during the UI part of the Setup. For this I call the Get-WindowsFeature cmdlet in my managed bootstrapper. However, this fails, because the custom Bootstrapper application always seems to be 32bit. Unfortunately, the ServerManager PowerShell module is only available as 64bit. I've already tried to compile the whole setup solution as 64, but no avail. Is this scenario simply not possible or am I missing something? Kind regards, Henning -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] X64 Burn Bootstrapper
Hmmm. Generally, when I call applets I wrap them in C# or call them with CAQuietExec[64] because of this issue. The trick is that there are two powershell.exe's on a 64-bit system, and you get the 32-bit one by default. You're probably going to have to find a way to force the 64-bit powershell to be called or your context will be wrong. -- John M. Cooper -Original Message- From: Henning Krause [mailto:m...@henningkrause.eu] Sent: Wednesday, June 27, 2012 8:24 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] X64 Burn Bootstrapper Maybe my question was poorly phrased. I'm not running a custom action. My call to Get-WindowsFeature resides in a Managed Bootstrapper application (aka Burn). I haven't found a way to start the Bundle process as x64. Kind regards, Henning -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Wednesday, June 27, 2012 3:10 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] X64 Burn Bootstrapper You have to call with a 64-bit entry point. If you're using CAQuietExec, you need to be using CAQuietExec64 to execute in a 64-bit process. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.(r) Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Henning Krause [mailto:m...@henningkrause.eu] Sent: Wednesday, June 27, 2012 4:46 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] X64 Burn Bootstrapper Hi, as part of my managed bundle, I may need to activate certain Windows Features. Since I'm targeting Windows 2008 R2 or later, I can safely use the Add-WindowsFeature and Get-WindowsFeature cmdlets. The Add-WindowsFeature would be called from a custom action. However, I want to display a list of missing features to the user during the UI part of the Setup. For this I call the Get-WindowsFeature cmdlet in my managed bootstrapper. However, this fails, because the custom Bootstrapper application always seems to be 32bit. Unfortunately, the ServerManager PowerShell module is only available as 64bit. I've already tried to compile the whole setup solution as 64, but no avail. Is this scenario simply not possible or am I missing something? Kind regards, Henning -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received
Re: [WiX-users] X64 Burn Bootstrapper
Since I'm in the context of Burn, I can't call CAQuietExec. I'm not running in any MSI context. That comes later... Henning -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Wednesday, June 27, 2012 3:56 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] X64 Burn Bootstrapper Hmmm. Generally, when I call applets I wrap them in C# or call them with CAQuietExec[64] because of this issue. The trick is that there are two powershell.exe's on a 64-bit system, and you get the 32-bit one by default. You're probably going to have to find a way to force the 64-bit powershell to be called or your context will be wrong. -- John M. Cooper -Original Message- From: Henning Krause [mailto:m...@henningkrause.eu] Sent: Wednesday, June 27, 2012 8:24 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] X64 Burn Bootstrapper Maybe my question was poorly phrased. I'm not running a custom action. My call to Get-WindowsFeature resides in a Managed Bootstrapper application (aka Burn). I haven't found a way to start the Bundle process as x64. Kind regards, Henning -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Wednesday, June 27, 2012 3:10 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] X64 Burn Bootstrapper You have to call with a 64-bit entry point. If you're using CAQuietExec, you need to be using CAQuietExec64 to execute in a 64-bit process. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.(r) Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Henning Krause [mailto:m...@henningkrause.eu] Sent: Wednesday, June 27, 2012 4:46 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] X64 Burn Bootstrapper Hi, as part of my managed bundle, I may need to activate certain Windows Features. Since I'm targeting Windows 2008 R2 or later, I can safely use the Add-WindowsFeature and Get-WindowsFeature cmdlets. The Add-WindowsFeature would be called from a custom action. However, I want to display a list of missing features to the user during the UI part of the Setup. For this I call the Get-WindowsFeature cmdlet in my managed bootstrapper. However, this fails, because the custom Bootstrapper application always seems to be 32bit. Unfortunately, the ServerManager PowerShell module is only available as 64bit. I've already tried to compile the whole setup solution as 64, but no avail. Is this scenario simply not possible or am I missing something? Kind regards, Henning -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https
Re: [WiX-users] X64 Burn Bootstrapper
You'll have to proxy out to a 64-bit process. On Wed, Jun 27, 2012 at 7:17 AM, Henning Krause m...@henningkrause.euwrote: Since I'm in the context of Burn, I can't call CAQuietExec. I'm not running in any MSI context. That comes later... Henning -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Wednesday, June 27, 2012 3:56 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] X64 Burn Bootstrapper Hmmm. Generally, when I call applets I wrap them in C# or call them with CAQuietExec[64] because of this issue. The trick is that there are two powershell.exe's on a 64-bit system, and you get the 32-bit one by default. You're probably going to have to find a way to force the 64-bit powershell to be called or your context will be wrong. -- John M. Cooper -Original Message- From: Henning Krause [mailto:m...@henningkrause.eu] Sent: Wednesday, June 27, 2012 8:24 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] X64 Burn Bootstrapper Maybe my question was poorly phrased. I'm not running a custom action. My call to Get-WindowsFeature resides in a Managed Bootstrapper application (aka Burn). I haven't found a way to start the Bundle process as x64. Kind regards, Henning -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Wednesday, June 27, 2012 3:10 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] X64 Burn Bootstrapper You have to call with a 64-bit entry point. If you're using CAQuietExec, you need to be using CAQuietExec64 to execute in a 64-bit process. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.(r) Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Henning Krause [mailto:m...@henningkrause.eu] Sent: Wednesday, June 27, 2012 4:46 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] X64 Burn Bootstrapper Hi, as part of my managed bundle, I may need to activate certain Windows Features. Since I'm targeting Windows 2008 R2 or later, I can safely use the Add-WindowsFeature and Get-WindowsFeature cmdlets. The Add-WindowsFeature would be called from a custom action. However, I want to display a list of missing features to the user during the UI part of the Setup. For this I call the Get-WindowsFeature cmdlet in my managed bootstrapper. However, this fails, because the custom Bootstrapper application always seems to be 32bit. Unfortunately, the ServerManager PowerShell module is only available as 64bit. I've already tried to compile the whole setup solution as 64, but no avail. Is this scenario simply not possible or am I missing something? Kind regards, Henning -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions
