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]: BleachBit.BleachBit - Interactive Install Choice not possible #187864

Open
2 tasks done
Anutrix opened this issue Nov 1, 2024 · 1 comment
Open
2 tasks done
Labels
Area-External Issue-Bug It either shouldn't be doing this or needs an investigation.

Comments

@Anutrix
Copy link

Anutrix commented Nov 1, 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

No Install choice option for Bleachbit via winget.
Elevated and non-elevated window, install without only -i(i.e, without explicit scope):
Image

If we run --scope machine while elevated, it works but has user-level option disabled:
Image

If we run --scope machine while non-elevated, it gives following error but it doesn't seem to be a problem:

PS C:\Users\Anutrix> winget install -i BleachBit.BleachBit --scope machine
Failed to open the predefined source; please report to winget maintainers.
An unexpected error occurred while executing the command:
0x80070005 : unknown error

Steps to reproduce

  1. Just run winget install -i BleachBit.BleachBit in Windows Terminal.
  2. Try in elevated and non-elevated. The install option is always pre-determined and never a choice.

Actual behavior

Image

Expected behavior

This is how it looks when installer is directly run as admin:
Image
It should be possible to do choose via winget.

Environment

Windows Package Manager v1.9.25180
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.26100.2161
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.24.25180.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 %USERPROFILE%\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
ProxyCommandLineOptions Disabled
DefaultProxy Disabled

Screenshots and Logs

No response

@Anutrix Anutrix added the Issue-Bug It either shouldn't be doing this or needs an investigation. label Nov 1, 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 Nov 1, 2024
@SpecterShell
Copy link
Contributor

SpecterShell commented Nov 2, 2024

Elevated and non-elevated window, install without only -i(i.e, without explicit scope):

If we run --scope machine while elevated, it works but has user-level option disabled:

WinGet prefers user scope over machine scope, and would default to the former when user scope is available for this package. For this package, WinGet by default passes the /currentuser switch (or allusers in the machine scope) to the installer, and the installer itself disables the other option. This is somehow expected.

If we run --scope machine while non-elevated, it gives following error but it doesn't seem to be a problem:

This is a client bug. See #3898.

@stephengillie stephengillie added Area-External and removed Needs-Triage This work item needs to be triaged by a member of the core team. labels Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-External Issue-Bug It either shouldn't be doing this or needs an investigation.
Projects
None yet
Development

No branches or pull requests

3 participants