[Dependency Issue]: Dependency can't be found by main installer after it's installed

[stephengillie]

Please confirm these before moving forward

• I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
• I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue

Other

Brief description of your issue

This installer has Git as a dependency. It finds Git in the Windows Path during install to register itself. But the Windows Path in most Command Prompt and PowerShell windows appears to only update at window launch. One window must be opened for the dependency install, and then another window opened for the main package install. Observed in

• New version: GitHub.GitLFS version 3.3.0 winget-pkgs#90133

Similar behavior was observed in this PR - the installer completed, but validation failed as it used the same PowerShell window, and thus couldn't find Git in the Windows Path.

• GitHub.GitCredentialManager version 2.0.877.50119 winget-pkgs#90517

Steps to reproduce

For 90133 - On new system, modify the package's manifest to have Git.Git as a dependency, then install in a VM.

Actual behavior

The installer will error "Could not find Git; can not register Git LFS."

Expected behavior

Winget could help the client window to update its local Windows Path variable from the registry, so subsequent installers could install successfully, and programs run from the same window could find Git to execute successfully.

Environment

Windows Package Manager (Preview) v1.4.3132-preview
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19044.1288
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.19.3132.0

Screenshots and Logs

No response

[denelon]

Related to:

• Installing a package doesn't add it it to path #549