Runtime error when trying to uninstall coreutils

[kele14x]

I installed coreutils using winget, when I want to uninstall it, it report:

Runtime error

Failed to update PowerShell profiles: Shim: Could not
determine if target is a GUI app. Assuming console.

Clicking OK the uninstaller exits without uninstalled. So it can't be uninstalled for now.

[a-rookie-of-C-language]

Could you please provide your environment information, including the version number, uninstallation commands, and other detailed information?
Because we resolved it in #40 and a new release already released

[a-rookie-of-C-language]

I found 2026.5.29 not 2026.6.16 in winget.So maybe It dupe of #17

[kele14x]

@a-rookie-of-C-language , thanks for your reply.

I install the coreutils using winget install Microsoft.Coreutils, which is 2026.5.29 at install time. At first I uninstall it via Control Panel -> App, the uninstaller fails with this message. Then I tried using winget uninstall Microsoft.Coreutils, which calls the same uninstaller and fails the same way.

Then I tried install the new release from GitHub (coreutils-2026.6.16-x64.exe) and hope it will fix this issue. The installer fails at the end of process with this message (yes installer). But the version number in Control Panel has changed to 2026.6.16.

Then I uninstall via Control Panel, which still fails by this message.

I've checked #40 but not sure if it is related to pwsh.exe. I've pwsh.exe installed by scoop (which is a portable version if pwsh).

[kele14x]

This is the installer fail during install 2026.6.16. So not sure if this issue is really a dupe of #17 .

[a-rookie-of-C-language]

In #73 you can use --force to resolve it maybe?

Could you try it?

[kele14x]

@a-rookie-of-C-language I tried with winget install --id Microsoft.Coreutils --exact --force and the installer successed. The version number in Control Panel has changed to 2026.5.29. But the issue is still there, I can't uninstall it. The uninstaller reports error.

[a-rookie-of-C-language]

PS C:\Users\hzz> winget install --id Microsoft.Coreutils --exact
已找到 Coreutils for Windows [Microsoft.Coreutils] 版本 2026.5.29
此应用程序由其所有者授权给你。
Microsoft 对第三方程序包概不负责，也不向第三方程序包授予任何许可证。
正在下载 https://github.com/microsoft/coreutils/releases/download/v2026.5.29/coreutils-2026.5.29-x64.exe
  ██████████████████████████████  4.86 MB / 4.86 MB
已成功验证安装程序哈希
正在启动程序包安装...
安装程序将请求以管理员身份运行。期待提示。
已成功安装
PS C:\Users\hzz> winget uninstall --id Microsoft.Coreutils --exact
已找到 Coreutils for Windows version 2026.5.29 [Microsoft.Coreutils]
正在启动程序包卸载...
已成功卸载

I can uninstall it

I've pwsh.exe installed by scoop

maybe you install a pwsh.exe in microsoft will resolve that.
https://learn.microsoft.com/zh-cn/powershell/scripting/install/install-powershell-on-windows?view=powershell-7.6

The root cause is that uninstall calls pwsh.exe by name, so it depends on PATH. If Scoop shims are before the real PowerShell installation, the uninstaller starts ...\scoop\shims\pwsh.exe. That shim may fail and return non-zero

And #40 would be enhanced like #74 or check pwsh.exe really health? because #40 only check pwsh exist but not deal with pwsh.exe returned non-zero like ...\scoop\shims\pwsh.exe

[a-rookie-of-C-language]

Or close this issue and ignore this:

And #40 would be enhanced like #74 or check pwsh.exe really health? because #40 only check pwsh exist but not deal with pwsh.exe returned non-zero like ...\scoop\shims\pwsh.exe

Because this isn't the installer's problem It looks run well in normal,only use unofficial pwsh.exe will cause that.
But I hope approve my pr(#74 ). As I said in #74 :

if pwsh.exe already exist,but returned non-zero
such as:
In PowerShell profile, coreutils marker damaged；
Recorded profile Path unable to write or delete(；
Installer drectory or pwsh-install.ps1 damaged；
and so on

This kind of damage isn't necessarily caused by the user; it could also be due to disk errors, antivirus quarantines, or an incomplete previous installation.

[a-rookie-of-C-language]

@kele14x

maybe you install a pwsh.exe in microsoft will resolve that.
https://learn.microsoft.com/zh-cn/powershell/scripting/install/install-powershell-on-windows?view=powershell-7.6
The root cause is that uninstall calls pwsh.exe by name, so it depends on PATH. If Scoop shims are before the real PowerShell installation, the uninstaller starts ...\scoop\shims\pwsh.exe. That shim may fail and return non-zero

You can follow this:

• uninstall your pwsh.exe which installed by scoop or removed it in PATH
• install microsoft's pwsh.exe
• run winget uninstall --id Microsoft.Coreutils --exact

Wish this can help you

[kele14x]

Yes remove scoop's pwsh package and install Microsoft Store's PowerShell works.

I'm not sure if coreutils need to be fixed since it depends the external pwsh which is strange. Anyway my issue is solved so close this issue.