-
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
[Package Issue]: Gyan.FFmpeg does not uninstall correctly #2949
Comments
@denelon - sounds like a CLI issue
If any files are created in the folder outside of just the ffmpeg application, the default behavior of winget is to preserve them when uninstalling to avoid removing user data. You can override this using |
This comment was marked as off-topic.
This comment was marked as off-topic.
This has been fixed in WinGet v1.5.1081-preview release through PR #3002 cc @denelon |
Hi, still have the same problem on the latest stable version of Winget (v1.5.2201), on Windows 11 22h2. No matter what command I use, the process is stuck |
Please confirm these before moving forward
Category of the issue
Other
Brief description of your issue
Package Gyan.FFmpeg (v5.1.2) does not properly uninstall:
![image](https://user-images.githubusercontent.com/2787305/218076903-e1054d9e-6444-459d-870b-622a346a765f.png)
I'm
using --force
because otherwise it refuses to uninstall due to the package being supposedly modified, which is not the case. I even get this straight away after installing it fresh.Notice I'm running this as Administrator because that also how I install it (due to microsoft/winget-pkgs#95349 / #2909).
Steps to reproduce
(As administrator:)
winget install gyan.ffmpeg
winget uninstall gyan.ffmpeg
(complains about the package being modified, which is not the case)winget uninstall gyan.ffmpeg --force
Actual behavior
%LOCALAPPDATA%\Microsoft\WinGet\Packages\Gyan.FFmpeg_Microsoft.Winget.Source_8wekyb3d8bbwe
and subfolder/files remain behind.Expected behavior
All files/folders related to package are gone.
Environment
Screenshots and Logs
No response
The text was updated successfully, but these errors were encountered: