Thank you very much Phil. I'm not aware of WOW6432. Yes, the written key is present in the WOW6432.
But if in case of HKCU, it is written in the normal path. Not sure why? I'll try to build the installer in 64 bit and check. -----Original Message----- From: Phil Wilson [mailto:phildgwil...@gmail.com] Sent: Thursday, December 19, 2013 12:20 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Adding a registry key to HKLM You need to decide the bitness of that package and ideally say something explicit in the components and in the Package Platform - nothing is specified, so it's x86 by default. If you want both, you need two separate MSI files. Phil Wilson On Thu, Dec 19, 2013 at 12:10 PM, Phil Wilson <phildgwil...@gmail.com>wrote: > Well it's not a Win64 component, so it's going to WoW6432 in the registry. > Where were you looking? > > Phil Wilson > > > On Thu, Dec 19, 2013 at 11:47 AM, Shyam Kannam <shyam.kan...@hotmail.com>wrote: > >> Hi Blair, >> I just created a new sample just writing two registry keys and a >> readme file. Registry key gets written only if the Root is HKCU - if >> it is HKLM or HKMU installs fine, but no registry key written. >> >> Please let me know what am I missing here. Thanks in advance. >> >> <?xml version="1.0" encoding="UTF-8"?> <Wix >> xmlns="http://schemas.microsoft.com/wix/2006/wi";> >> <Product Id="*" Name="SetupProject3" Language="1033" >> Version="1.0.0.0" Manufacturer="Fabrikam" >> UpgradeCode="23fed7bc-bd26-4e94-94de-a61c9d7382d5"> >> <Package InstallerVersion="200" Compressed="yes" >> InstallScope="perMachine" /> >> >> <MajorUpgrade DowngradeErrorMessage="A newer version >> of [ProductName] is already installed." /> >> <MediaTemplate /> >> >> <Feature Id="ProductFeature" Title="SetupProject3" >> Level="1"> >> <ComponentGroupRef Id="ProductComponents" /> >> </Feature> >> </Product> >> >> <Fragment> >> <Directory Id="TARGETDIR" Name="SourceDir"> >> <Directory Id="ProgramFilesFolder"> >> <Directory Id="INSTALLFOLDER" >> Name="SetupProject3" /> >> </Directory> >> </Directory> >> </Fragment> >> >> <Fragment> >> <ComponentGroup Id="ProductComponents" >> Directory="INSTALLFOLDER"> >> <!-- </Component> --> >> <Component Id="CMPRegistryEntries" >> Guid="069E2626-1217-10D4-6D17-B720D5DFEA7D" > >> <RegistryKey Root="HKLM" Key="Software\Microsoft\TestRegKey" > >> <RegistryValue Name="installed" Value="1" Type="integer" >> KeyPath="no"/> >> <RegistryValue Name="PackageVersion" Value="1.1.10.1" >> Type="string" /> >> </RegistryKey > >> </Component> >> <Component Id="CMPReadMeTXT" >> Guid="299F0B6F-5388-92F8-391F-3133F146CA03"> >> <File Id="FileReadmeTxt" Name="Readme.txt" >> Source="$(var.ProjectDir)\Docs\Readme.txt" KeyPath="yes" /> >> </Component> >> </ComponentGroup> >> </Fragment> >> </Wix> >> >> -----Original Message----- >> From: Blair Murri [mailto:os...@live.com] >> Sent: Thursday, December 19, 2013 1:16 AM >> To: General discussion for Windows Installer XML toolset. >> Subject: Re: [WiX-users] Adding a registry key to HKLM >> >> You arent providing enough code here to verify a complete repro, and >> the obvious repro from the code you do provide actually does work. >> >> >> Please provide a complete example of a failing case, and please >> include the associated verbose log from that same case. >> >> >> Since attachments tend to be dropped by the remailer, please place >> those files somewhere in the cloud and provide the URL for them here >> in the mail list so we can replicate your exact test case. >> >> >> >> >> >> >> -Blair >> >> >> >> >> >> From: Shyam Kannam >> Sent: Wednesday, December 18, 2013 12:16 PM >> >> To: General discussion for Windows Installer XML toolset. >> >> >> >> >> >> Hi Phil, >> It's still doesn't work for me. I don't get an elevated prompt but >> an untrusted warning - as the package wasn't signed. >> >> I tried running the installer from an elevated command prompt - but >> the result is the same. I didn't see much of a difference in the >> verbose log as well from HKCU and HKLM Root tests. The component >> gets installed when it is HKCU, but when I keep either HKMU or HKLM, >> it is totally ignored and doesn't write the key to registry. >> >> Do I need to set any property for getting an elevated command prompt? >> Any suggestions would be helpful. >> >> <Property Id="ALLUSERS" Value="1" Admin="yes"/> >> >> <ComponentGroup Id="REGISTRYENTRIES" Directory="INSTALLFOLDER"> >> <Component Id="CMPRegistryEntries" >> Guid="069E2626-1217-10D4-6D17-B720D5DFEA7D" > >> <RegistryKey Root="HKLM" Key="Software\Microsoft\Spectrum" > >> <RegistryValue Name="installed" Value="1" Type="integer" >> KeyPath="no"/> >> <RegistryValue Name="SpectrumPackageVersion" >> Value="$(var.MSIPACKAGEVERSION)" Type="string" /> >> </RegistryKey > >> </Component> >> </ComponentGroup> >> >> >> -----Original Message----- >> From: Phil Wilson [mailto:phildgwil...@gmail.com] >> Sent: Wednesday, December 18, 2013 8:22 AM >> To: General discussion about the WiX toolset. >> Subject: Re: [WiX-users] Adding a registry key to HKLM >> >> Yes of course WiX supports writing to HKLM, so where are you at this >> point? >> Using HKMU? HKLM? It just works, and if it doesn't then something is >> going wrong but you're not supplying any extra information to let >> anyone figure out why it's not working. Are you seeing an elevation >> prompt during the install, or otherwise making sure that the install >> is elevated? Are you sure the component is being installed? Have you looked at a verbose log? >> >> Phil Wilson >> >> >> On Tue, Dec 17, 2013 at 9:42 PM, Nicolás Alvarez >> <nicolas.alva...@gmail.com>wrote: >> >> > Why are you reposting your question after merely 2 hours? This is >> > free volunteer support, have some patience. >> > >> > -- >> > Nicolás >> > >> > 2013/12/17 Shyam Kannam <shyam.kan...@hotmail.com>: >> > > Could someone help me on this? Does WiX allows to write registry >> > entries to HKLM? Even it is mentioned as a per machine scope, it >> > ignores it. >> > > >> > > >> > > -----Original Message----- >> > > From: Shyam Kannam [mailto:shyam.kan...@hotmail.com] >> > > Sent: Tuesday, December 17, 2013 1:51 PM >> > > To: wix-users@lists.sourceforge.net >> > > Subject: Re: [WiX-users] Adding a registry key to HKLM >> > > >> > > Tried HKMU - but the key is just ignored. Key is not created >> > > neither in >> > HKLM nor in HKCU. This is the same behavior with HKLM. Logs also >> > doesnt give me any hint on why it is getting ignored. >> > > >> > > >> > > >> > > >> > > >> > > >> > > Sent from Windows Mail >> > > >> > > >> > > >> > > >> > > >> > > From: Phil Wilson >> > > Sent: Tuesday, December 17, 2013 1:50 PM >> > > To: wix-users@lists.sourceforge.net >> > > >> > > >> > > >> > > >> > > >> > > P.S. IMO you don't need HKMU because you should split that >> > > component, >> > but if your HKMU is going into HKCU then you're probably not doing >> > an elevated per machine install. You're probably per user. >> > > >> > > Phil Wilson >> > > >> > > >> > > On Tue, Dec 17, 2013 at 1:33 PM, Shyam Kannam >> > ><shyam.kan...@hotmail.com >> > >wrote: >> > > >> > >> Thanks Jacob for the response. >> > >> >> > >> >> > >> I still didnt have success. With the below code, I dont have >> > >> any warnings. But the key is created only when it is give is HKCU. >> > >> Both HKLM or HKMU seems ignored (dont see the key created >> > >> after installation). Any help on this would be appreciated. >> > >> All I need is to place one registry key under HKLM. >> > >> >> > >> >> > >> >> > >> <ComponentGroup Id="REGISTRYENTRIES" Directory="INSTALLFOLDER"> >> > >> >> > >> <Component Id="CMPRegistryEntries" >> > >> Guid="069E2626-1217-10D4-6D17-B720D5DFEA7D" > >> > >> >> > >> <RegistryKey Root="HKMU" Key="Software\Microsoft\Spectrum" > >> > >> >> > >> <RegistryValue Name="installed" Value="1" Type="integer" /> >> > >> >> > >> <RegistryValue Name="SpectrumPackageVersion" >> > >> Value="$(var.MSIPACKAGEVERSION)" Type="string" /> >> > >> >> > >> </RegistryKey > >> > >> >> > >> </Component> >> > >> >> > >> </ComponentGroup> >> > >> >> > >> <!-- program menu items --> >> > >> >> > >> <ComponentGroup Id="PROGRAMMENUSHORTCUT" >> > >> Directory="INSTALLFOLDER"> >> > >> >> > >> <Component Id="CMPApplicationStartMenuShortcut" >> > >> Guid="13269471-FC6F-40E6-B7BF-02CDB3395A11" > >> > >> >> > >> <Shortcut Id="UninstallDriver" >> > >> >> > >> Name="!(loc.Uninstall)" >> > >> >> > >> Description="!(loc.UninstallDescription)" >> > >> >> > >> Target="[System64Folder]msiexec.exe" >> > >> >> > >> Arguments="/x [ProductCode]" >> > >> >> > >> Icon="PackageIcon" /> >> > >> >> > >> <RemoveFolder Id="PROGRAMMENUDIR" On="uninstall"/> >> > >> >> > >> </Component> >> > >> >> > >> </ComponentGroup> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> Sent from Windows Mail >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> From: Hoover, Jacob >> > >> Sent: Tuesday, December 17, 2013 1:27 PM >> > >> To: wix-users@lists.sourceforge.net >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> http://robmensching.com/blog/posts/2007/4/27/how-to-create-an-un >> > >> ins >> > >> tal >> > >> l-shortcut-and-pass-all-the >> > >> >> > >> If it were me... and your install is per-machine, use HKMU and >> > >> then suppress the one invalid ICE message. ( >> > >> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/IC >> > >> E57 >> > >> -wi >> > >> th-HKMU-tt5795201.html#a5796717 >> > >> ) >> > >> >> > >> >> > >> But really, why is it a requirement for this RegistryKey be >> > >> associated with the shortcut, which shouldn't have anything to >> > >> do with a service (IE, can't they be two components). >> > >> >> > >> -----Original Message----- >> > >> From: Shyam Kannam [mailto:shyam.kan...@hotmail.com] >> > >> Sent: Tuesday, December 17, 2013 1:23 PM >> > >> To: wix-users@lists.sourceforge.net >> > >> Subject: [WiX-users] Adding a registry key to HKLM >> > >> >> > >> Im running into issues to add couple registry keys to HKLM hive. >> > >> This is a requirement for the project to add the key to HKLM as >> > >> they can be accessed from a local system service. HKCU is not >> > >> accessible from a local system service. >> > >> >> > >> >> > >> When I use the code below, Im getting ICE errors. Tried >> > >> different ways to avoid the error, but unable to see the key >> > >> under HKLM created after installation. I think Im missing some basic here. >> > >> >> > >> >> > >> >> > >> >> > >> error LGHT0204: ICE38: Component CMPApplicationStartMenuShortcut >> > >> installs to user profile. It's KeyPath registry key must fall >> > >> under >> > HKCU. >> > >> error LGHT0204: ICE43: Component CMPApplicationStartMenuShortcut >> > >> has non-advertised shortcuts. It's KeyPath registry key should >> > >> fall under >> > HKCU. >> > >> error LGHT0204: ICE57: Component 'CMPApplicationStartMenuShortcut' >> > >> has both per-user and per-machine data with a per-machine KeyPath. >> > >> >> > >> >> > >> >> > >> <!-- program menu items --> >> > >> <ComponentGroup Id="PROGRAMMENUSHORTCUT" Directory="PROGRAMMENUDIR2"> >> > >> <Component Id="CMPApplicationStartMenuShortcut" >> > >> Guid="13269471-FC6F-40E6-B7BF-02CDB3395A11" > >> > >> <Shortcut Id="UninstallDriver" >> > >> Name="!(loc.Uninstall)" >> > >> Description="!(loc.UninstallDescription)" >> > >> Target="[System64Folder]msiexec.exe" >> > >> Arguments="/x [ProductCode]" >> > >> Icon="PackageIcon" /> >> > >> <RegistryValue Root="HKLM" Key="Software\Microsoft\Spectrum" >> > >> Name="SpectrumPackageVersion" Type="string" >> > >> Value="$(var.MSIPACKAGEVERSION)"/> >> > >> <RemoveFolder Id="PROGRAMMENUDIR" On="uninstall"/> >> > >> </Component> >> > >> </ComponentGroup> >> > >> >> > >> >> > >> >> > >> > >> > ------------------------------------------------------------------- >> > --- >> > -------- Rapidly troubleshoot problems before they affect your >> > business. Most IT organizations don't have a clear picture of how >> > application performance affects their revenue. With AppDynamics, >> > you get 100% visibility into your Java,.NET, & PHP application. >> > Start your 15-day FREE TRIAL of AppDynamics Pro! >> > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ost >> > g.c lktrk _______________________________________________ >> > WiX-users mailing list >> > WiX-users@lists.sourceforge.net >> > https://lists.sourceforge.net/lists/listinfo/wix-users >> > >> >> --------------------------------------------------------------------- >> ------- >> -- >> Rapidly troubleshoot problems before they affect your business. Most >> IT organizations don't have a clear picture of how application >> performance affects their revenue. With AppDynamics, you get 100% >> visibility into your Java,.NET, & PHP application. Start your 15-day >> FREE TRIAL of AppDynamics Pro! >> >> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg. >> clktrk _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >> --------------------------------------------------------------------- >> --------- Rapidly troubleshoot problems before they affect your >> business. Most IT organizations don't have a clear picture of how >> application performance affects their revenue. With AppDynamics, you >> get 100% visibility into your Java,.NET, & PHP application. Start >> your 15-day FREE TRIAL of AppDynamics Pro! >> >> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg. >> clktrk _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> --------------------------------------------------------------------- >> --------- Rapidly troubleshoot problems before they affect your >> business. Most IT organizations don't have a clear picture of how >> application performance affects their revenue. With AppDynamics, you >> get 100% visibility into your Java,.NET, & PHP application. Start >> your 15-day FREE TRIAL of AppDynamics Pro! >> >> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg. >> clktrk _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >> --------------------------------------------------------------------- >> --------- Rapidly troubleshoot problems before they affect your >> business. Most IT organizations don't have a clear picture of how >> application performance affects their revenue. With AppDynamics, you >> get 100% visibility into your Java,.NET, & PHP application. Start >> your 15-day FREE TRIAL of AppDynamics Pro! >> >> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg. >> clktrk _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> > > ---------------------------------------------------------------------------- -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
