Problems with launch condition and per-machine vs. per-user installation on Windows 10 #9285
Unanswered
bobhairgrove
asked this question in
Questions
Replies: 1 comment
-
|
OK, item 2 is solved for the moment, thanks to the user @forderud :) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Question
(NOTE: I do not actually pay anything for the OSMF since this is for a school project which doesn't pay anything. Since I therefore consider myself compliant in this regard, I checked the box anyway...)
This is my first attempt at creating a non-trivial MSI package except from various tutorials found on the web. Using WiX Toolset 6.0.2, my
<Package>element hasScope="perMachine". Windows 10 installs everything to the right folders, except that all of the registry values are written to a subkey ofHKCUinstead ofHKLM. Also, there are no shortcuts created (desktop and start menu folders are specified). I do not specify any registry keys except for shortcuts; when I use 'HKLM' for these, WiX or MSI complains about mixed per-user and per-machine data in the shortcuts. The error message seems to imply that shortcuts are ALWAYS installed on a per-user basis, and that registry keys for shortcuts must therefore go under "HKCU" instead of "HKLM".Another problem is that for the purpose of testing the MSI installation, I created a virtual machine with a clean installation of Windows 10 which does not have the MSVC redistributables installed. The launch condition does not trigger at all which compares the result of a registry search for the version to a minimum version value.
Do I need two registry searches, one to determine whether the redistributables are installed, and another to fetch the installed version?
I generated a log file on the initial install, but cannot detect any problems with the invocation of the launch condition checks. I did have to disable ICE03 concerning "string overflow in launch condition table" or some such thing.
Here is my
<Package>element opening tag along with the launch conditions:And the main component is defined here:
The main
<Feature>element pulls in other components; these seem to get installed OK:After the installation has finished, I can run uninstall, and the files and registry entries are removed.
TL;DR:
Open Source Maintenance Fee
wixtoolsetproject because I support the maintainers.Beta Was this translation helpful? Give feedback.
All reactions