Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Package Issue]: DBeaver.DBeaver not respecting machine install scope defined in settings.json #135726

Closed
2 tasks done
Skeb1ns opened this issue Jan 22, 2024 · 3 comments
Closed
2 tasks done
Labels
Area-Manifest This may require a change to the manifest Area-Scope Issue-Bug It either shouldn't be doing this or needs an investigation.
Milestone

Comments

@Skeb1ns
Copy link
Contributor

Skeb1ns commented Jan 22, 2024

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

Installation issue.

Brief description of your issue

The installer.yaml file for DBeaver has been changed in version 23.3.2 and removed the explicit user and machine codeblocks. For some reason the app now get's installed by default in the user scope unless --scope machine is passed.

If I don't pass the scope it get's installed in user context even though I have configured the settings.json file where I explicitly set that everything must be installed in machine context if possible. (This works fine for other apps)

This currently breaks installing the app using Intune where the system account is used to install the app (it now installs it in the user profile of the system account making the app unusable for the logged on user).

This worked fine before.

Steps to reproduce

winget install --exact dbeaver.dbeaver --silent --accept-package-agreements --accept-source-agreements

Actual behavior

DBeaver is installed in user context even though settings.json has been configured in the defaultState (System) / LocalState (User) directories.

Expected behavior

DBeaver get's installed in machine context. (Corporate devices should not use user installed apps wherever possible in my opinion).

Environment

Windows: Windows.Desktop v10.0.22621.3007
System Architecture: Arm64
Package: Microsoft.DesktopAppInstaller v1.21.3482.0

Winget Directories
-----------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\Diag…
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\sett…
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages
Installer Downloads                \\Mac\Home\Downloads

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled

Screenshots and Logs

No response

@Skeb1ns Skeb1ns added the Issue-Bug It either shouldn't be doing this or needs an investigation. label Jan 22, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage This work item needs to be triaged by a member of the core team. label Jan 22, 2024
@Skeb1ns Skeb1ns changed the title [Package Issue]: DBeaver not respecting machine install scope defined in settings.json [Package Issue]: DBeaver.DBeaver not respecting machine install scope defined in settings.json Jan 22, 2024
@PckgrBot
Copy link
Contributor

@vedantmgoyal2009 I think your automation is overwriting previous manifests and not respecting the scopes or count of installers.

@stephengillie stephengillie added Area-Manifest This may require a change to the manifest Area-Scope and removed Needs-Triage This work item needs to be triaged by a member of the core team. labels Jan 23, 2024
@Exorcism0666
Copy link
Contributor

@stephengillie Can you close this issue ? #135771

@stephengillie
Copy link
Collaborator

@ stephengillie Can you close this issue ? #135771

@denelon denelon added this to the 1.7 Packages milestone Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Manifest This may require a change to the manifest Area-Scope Issue-Bug It either shouldn't be doing this or needs an investigation.
Projects
None yet
Development

No branches or pull requests

5 participants