-
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
Vim install fails with error code 2 #500
Comments
@dbrodsky I was just able to install vim as a user. Can you check the logs? |
Where do I find the log file? I tried passing |
This seems like a duplicate of #245 |
#390 would help here. |
I think the Vim installer is not correctly attempting to get elevated permissions. That's the best I can come up with since I still don't know where I tried running on a different PC, and it claims to install successfully but the installer never actually runs (it just flashes on the screen briefly).
So now, if I run in interactive mode with
@megamorf It could be a duplicate of that ticket, certainly looks similar. However, there are other programs I can install successfully, such as PowerToys. Could be something with the Vim installer, or something janky in the handoff between |
We've added the log location to |
Thank you, @denelon -- here is my log file from running
|
I get this error when I try to install Stretchly too. When I use the installer (in this case with the
Logs:
|
Path changed after manifest schema upgrade: https://github.com/microsoft/winget-pkgs/tree/master/manifests/s/Stretchly/Stretchly/1.3.0 |
@kapsiR can you share |
Sure:
|
@kapsiR can you upgrade your client? I'm trying to figure out if it's a client issue, an OS issue, or something with the installer. I did a clean install, and I've seen a couple of apps that throw errors when you try a subsequent install. |
@kapsiR nevermind, I see you are on the latest release :( |
I'm using the App Installer from the Store, can there be any difference with a directly installed appxbundle? |
The one key difference is the version of APP Installer in the Microsoft Store is automatically updated when we publish new releases there. This issue looks like it's related to the installers. You may need to reach out to the publishers to determine what exit code 2 means. Please thumbs up this issue: hovancik/stretchly#893 |
I'm not sure about the integrity level comment in the stretchly issue, but I'm noting it here so we can look to see if that may have something to do with the issue. |
@kapsiR you can test the x64 using a local copy of the manifest and using |
it seems winget checks for installers UAC permissions , hence denying UAC results in winget reporting installation canceled. trying to manually downloading and installing also fails because installer doesn't auto elevate from standard account. installing to ~\UserFolder installs fine but doesn't register to ARP list :) (irony) It seems NSIS Installers check for admin accounts and only elevate the installers when run from admin accounts only.
My suggestion : since it seems this is not vim or stretchly specific issue rather a generic issue of NSIS installers, I will suggest you to close this issue and focus on implementing following behaviors :
just my 2 cents :) |
@ecovio1 thank you for such thorough analysis. This will certainly help guide a better solution. |
I've marked this Area-External to indicate it's a challenge with NSIS installers. We've got another Issue or two to create for User vs. Machine installation, so I'll keep this open until that is implemented. I'll link the Issue when we have it better defined. |
I'd like to add here the current state with the following
Stretchly v1.7.0 now installs successfully when |
I'm having the same problem testing an NSIS (Nullsoft) install package made with Electron-Builder which I'ld like to release via winget. The installer works fine when run from PowerShell with the /S switch, and installs silently defaulting to CurrentUser (as expected). However, if I attempt to install the same package using a wincreate manifest, the installer exits with Code 2 (and doesn't install anything). I read somewhere (sorry don't have the reference) that NSIS Code 2 means "invalid commandline switches". I have checked the logs and the correct commandline appears to be being used:
I don't know if it's relevant that this is a 32bit binary, with the aim of targetting both x86 and x64 with the one package (being Electron, this makes absolutely no difference for the end user and simplifies things a lot for the Dev!). There are some strange "FAIL" log entries relating to that (I think), don't know if they're relevant:
I've tried changing the This is what the Installer manifest looks like (the
|
I have some further information that can help diagnose this, I think. I tried running the manifest in my previous message with the This suggests a very different error from what I was suspecting, and suggests some underlying problem with paths in the handover between winget and NSIS installers... |
Brief description of your issue
When I try to install vim (technically gvim) using
winget
, the download succeeds but then it immediately errors out. Full output shown below:Steps to reproduce
winget install vim
I also tried running with the
-i
flag, and when I do, instead of just erroring I get a popup dialogLight googling of the error message indicates it may be a problem with vim's installer. Nevertheless, silently failing is still an issue with
winget
.Expected behavior
Vim installs
Actual behavior
Vim does not install
Environment
I am running as a nonprivileged user. I have not tried running PowerShell as administrator; I prefer to use this tool as a regular user and just do the admin account pw in a UAC dialog when necessary.
Thanks for reading! :)
The text was updated successfully, but these errors were encountered: