-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Error 1603 -- easy work-around and easy fix. #248
Comments
Definitely agree. Brackets was the first thing on the list I decided to try out and had the exact same experience. For some reason I expected this to install applications into user-space. While I can appreciate the idea and the direction things are headed with this, it is extremely off-putting that the very first attempt to install something by following the listed instructions yields a useless generic 'stop you in your tracks' error. Thanks, |
This error code appears to be coming from the installer and not winget.exe. We have an Issue to deal with non-zero exit codes on success in the backlog. We also have #152 that may cover this scenario. Is this a duplicate, or something else? |
It looks like there is also an association with #152 |
I just had an error 1603 come up when trying to install an application that already existed. Removing the application fixed the error without a need for elevated privileges. |
Got error 1603 while trying to install Powershell 7
note: On trying again with a powershell elevated to admin, i still got the same error. |
It appears there are a few reasons MSI installers return 1603. |
We will be implementing #149 User vs. System Installation (non MSIX). That should help with installers that require elevation. |
Cause Windows Installer is attempting to install an app that is already installed on your PC. |
This error message is coming from the MSI installer, and not the Windows Package Manager. I'll convert this issue into a Feature so we can add a better error explanations when we get error 1603 from MSI installers. |
I don't know if it helps, but I am experiencing the same issue with LibreOffice. If I download and install it manually, it works perfectly fine. |
For |
According to the documentation
but it doesn't work now. For install the application in the current cmd session you can use interactive mode (option -i) or third-party sudo command $ winget install -i LibreOffice
$ sudo winget install LibreOffice |
Running PowerShell (Admin) and using -i flag solved my problem
I was facing issues with LibreOffice and VirtualBox |
Experienced the same issue while installing LibreOffice, and it's surprising to see the feature has not been added yet. |
This issue is complex, as there can be many causes of error 1603. I was receiving this in an automation when installing Adobe.Acrobat.Reader.64-bit. I was auto-installing each available version into a subdirectory named after the ID of the application. I was using "--override" to specify the install directory and getting 1603s. All permissions on path were wide open. |
@Swamination, have you reported the problem to Adobe? Some confirmation from them would be beneficial. I doubt that anybody but you shall bother, if able to, reproduce that problem. |
FYI: In my case, |
1603 when installing SSMS with elevated permissions. UPDATE: After a reboot, in installed fine. |
@BobFrankston - Are you still experiencing this issue on the latest version of WinGet (1.7.10582) ? |
Brief description of your issue
Steps to reproduce
I tried installing Adobe.brackets.
It failed with 1603
Run in admin shell and it works.
Before I get into it there are two problems with easy fixes
Instead of error 1603 give an actionable message. This is such a fundamental point that I shouldn't have to say it for the umpteenth time.
The fix was to run it with privilege. Tell me that in the error message and, better, offer, to do it automatically.
Expected behavior
Install brackets
Actual behavior
Error 1603
Environment
Powershell
The text was updated successfully, but these errors were encountered: