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

Error 1603 -- easy work-around and easy fix. #248

Open
BobFrankston opened this issue May 20, 2020 · 20 comments
Open

Error 1603 -- easy work-around and easy fix. #248

BobFrankston opened this issue May 20, 2020 · 20 comments
Assignees
Labels
Issue-Feature This is a feature request for the Windows Package Manager client.

Comments

@BobFrankston
Copy link

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

[winget --info]
Windows Package Manager version V0.1.41331 Preview
Windows: Windows.Desktop version 1609
Package: Microsoft.DesktopAppInstaller version

Any other software?
@MostHated
Copy link

MostHated commented May 20, 2020

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,
-MH

@KevinLaMS KevinLaMS added the Issue-Bug It either shouldn't be doing this or needs an investigation. label May 23, 2020
@denelon
Copy link
Contributor

denelon commented May 28, 2020

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?

@denelon
Copy link
Contributor

denelon commented May 30, 2020

It looks like there is also an association with #152

@panasenco
Copy link

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.

@denelon denelon added this to the Package Manager Backlog milestone Jun 1, 2020
@rishavs
Copy link

rishavs commented Nov 1, 2020

Got error 1603 while trying to install Powershell 7

PS C:\Users\risharan> winget install --name PowerShell --exact
Found PowerShell [Microsoft.PowerShell]
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://github.com/PowerShell/PowerShell/releases/download/v7.0.3/PowerShell-7.0.3-win-x64.msi
  ██████████████████████████████  87.0 MB / 87.0 MB
Successfully verified installer hash
Starting package install...
Installer failed with exit code: 1603
Installer log is available at: C:\Users\risharan\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\TempState\WinGet\Microsoft.PowerShell.7.0.3.log

note: On trying again with a powershell elevated to admin, i still got the same error.

@denelon
Copy link
Contributor

denelon commented Jan 7, 2021

It appears there are a few reasons MSI installers return 1603.
https://docs.microsoft.com/en-us/troubleshoot/windows-server/application-management/msi-installation-error-1603

@denelon
Copy link
Contributor

denelon commented Jan 7, 2021

We will be implementing #149 User vs. System Installation (non MSIX). That should help with installers that require elevation.

@denelon
Copy link
Contributor

denelon commented Apr 20, 2021

Cause
You may receive this error message if any one of the following conditions is true:

Windows Installer is attempting to install an app that is already installed on your PC.
The folder that you are trying to install the Windows Installer package to is encrypted.
The drive that contains the folder that you are trying to install the Windows Installer package to is accessed as a substitute drive.
The SYSTEM account does not have Full Control permissions on the folder that you are trying to install the Windows Installer package to. You notice the error message because the Windows Installer service uses the SYSTEM account to install software.

@denelon
Copy link
Contributor

denelon commented Apr 20, 2021

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.

@denelon denelon added Issue-Feature This is a feature request for the Windows Package Manager client. Size-XXS and removed Issue-Bug It either shouldn't be doing this or needs an investigation. labels Apr 20, 2021
@ln-12
Copy link

ln-12 commented May 29, 2021

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.

@llinfeng
Copy link

For TrackerSoftware.PDF-XChangeEditor, I got the exit code: 1603 when I did not notice that the program has been installed with its standalone installer. Removing the manually installed version got the winget install TrackerSoftware.PDF-XChangeEditor command to go through.

@ftoh
Copy link

ftoh commented Aug 24, 2021

According to the documentation

When running winget without administrator privileges, some applications may require elevation to install. When the installer runs, Windows will prompt you to elevate. If you choose not to elevate, the application will fail to install.

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

@sabiviji
Copy link

sabiviji commented Sep 1, 2021

Running PowerShell (Admin) and using -i flag solved my problem

winget install -i <name>

I was facing issues with LibreOffice and VirtualBox
Installer failed with exit code: 1603 [Running PowerShell (Admin) solved]
Then,
Installer failed with exit code: 3010 [Running in -i solved]

@abuturabofficial
Copy link

abuturabofficial commented Oct 28, 2021

Experienced the same issue while installing LibreOffice, and it's surprising to see the feature has not been added yet.

@Swamination
Copy link

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.
/msi /qn INSTALLDIR=C:\SamplePath\Adobe.Acrobat.Reader.64-bit\22.001.20142 /norestart EULA_ACCEPT=YES
I pre-created the Adobe.Acrobat.Reader.64-bit root directory and the errors went away. Feels like could be a bug within the Adobe installer when accepting an override path via winget, failing to create the path before the last segment. If using override, try pre-creating the root dir path.

@RokeJulianLockhart
Copy link

RokeJulianLockhart commented Jul 11, 2022

#248 (comment)

@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.

@sfiruch
Copy link

sfiruch commented Mar 23, 2023

FYI: In my case, -i told me that a machine reboot was required.

@MisinformedDNA
Copy link

MisinformedDNA commented Sep 15, 2023

1603 when installing SSMS with elevated permissions.

UPDATE: After a reboot, in installed fine.

@denelon denelon removed the Size-XXS label Nov 14, 2023
@Trenly
Copy link
Contributor

Trenly commented Mar 6, 2024

@BobFrankston - Are you still experiencing this issue on the latest version of WinGet (1.7.10582) ?

@BobFrankston
Copy link
Author

It's been so long that I forgot what adobe.brackets is but it does seem to install. But figured I'd give it a try to just to hukmor you since, obviously, the problem has been fixed ... or has it?

image
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature This is a feature request for the Windows Package Manager client.
Projects
None yet
Development

No branches or pull requests