You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Package Gyan.FFmpeg (v5.1.2) does not properly uninstall:
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 #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
Expected behavior
All files/folders related to package are gone.
Actual behavior
%LOCALAPPDATA%\Microsoft\WinGet\Packages\Gyan.FFmpeg_Microsoft.Winget.Source_8wekyb3d8bbwe and subfolder/files remain behind.
Environment
Windows Package Manager v1.4.10173
Windows: Windows.Desktop v10.0.22621.1105
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.19.10173.0
Gyan.FFmpeg v5.1.2
The text was updated successfully, but these errors were encountered:
Brief description of your issue
Package Gyan.FFmpeg (v5.1.2) does not properly uninstall:
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 #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
Expected behavior
All files/folders related to package are gone.
Actual behavior
%LOCALAPPDATA%\Microsoft\WinGet\Packages\Gyan.FFmpeg_Microsoft.Winget.Source_8wekyb3d8bbwe
and subfolder/files remain behind.Environment
The text was updated successfully, but these errors were encountered: