Skip to content

Shouldn't App Paths registration be done for HKLM? #5905

Closed

Description

<Component Id="RegistryEntries" Guid="{402e52f7-baf8-489d-af21-f756a6ca3530}">
<RegistryKey Root="HKCU" Key="Software\Microsoft\Windows\CurrentVersion\App Paths\pwsh.exe" ForceCreateOnInstall="yes" ForceDeleteOnUninstall="yes">
<RegistryValue Type="string" Value="[$(var.ProductVersionWithName)]pwsh.exe"/>
</RegistryKey>
</Component>

pwsh is installed globally so shouldn't it be on HKLM?

Activity

  1. added
    Issue-Questionideally support can be provided via other mechanisms, but sometimes folks do open an issue to get a
    on Jan 15, 2018
  2. iSazonov commented on Jan 15, 2018

    @iSazonov
    Collaborator
  3. bergmeister commented on Jan 15, 2018

    @bergmeister
    Contributor

    Kagami Sascha Rosylight (@saschanaz) is absolutely right that it should be HKLM because at the moment the install scope is per machine and not per user.
    I wanted to ask at some point if the installer should rather install only on a per user basis (or give the option) but for the moment, HKLM is the better thing to do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue-Questionideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aResolution-FixedThe issue is fixed.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions