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

Manual installation succeeded although it sounded like it didn't #235

Closed
ermshiperete opened this issue May 20, 2020 · 8 comments
Closed
Labels
Resolution-Duplicate Issue is a duplicate
Milestone

Comments

@ermshiperete
Copy link

ermshiperete commented May 20, 2020

Brief description of your issue

Confusing message after installation of winget-cli

Steps to reproduce

I downloaded the installer for winget from the GitHub release page and opened it which started the installation.

Expected behavior

A message that the installation was successful.

Actual behavior

I don't remember what dialog message it put up exactly, but it made it sound like it didn't successfully install. (Maybe it said something that I can now install packages with winget. However, I didn't read it carefully and skimming over it made it sound like the installation didn't succeed).

So I went searching on the Internet how I can install a .appxbundle file, followed the steps and was then presented with the message that the App Installer is already installed.

Environment

Windows Package Manager v0.1.41331 Preview
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.18362.836
Package: Microsoft.DesktopAppInstaller v1.0.41331.0
@xtqqczze
Copy link

image

@QAInsights
Copy link

@xtqqczze I got the exact message as you mentioned. Were you able to install winget-cli successfully? Please clarify.

@xtqqczze
Copy link

@QAInsights I received that message upon installation, but the winget command is in fact available on my command line. So even though the mesage is confusing, the installation actually succeeded.

@QAInsights
Copy link

QAInsights commented May 20, 2020

Okay, for me it is not installed properly.
image

@QAInsights
Copy link

It worked for for me after configuring the PATH in the environment variable.

@denelon
Copy link
Contributor

denelon commented May 28, 2020

Duplicate of #210

@denelon denelon marked this as a duplicate of #210 May 28, 2020
@ghost
Copy link

ghost commented May 28, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed May 28, 2020
@ghost ghost added the Resolution-Duplicate Issue is a duplicate label May 28, 2020
@ermshiperete
Copy link
Author

ermshiperete commented May 28, 2020

No, I don't think it's an exact duplicate. The focus of this issue is on the misleading and confusing message. Things worked for me which suggests that the PATH was correct.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate Issue is a duplicate
Projects
None yet
Development

No branches or pull requests

4 participants