terminal icon indicating copy to clipboard operation
terminal copied to clipboard

Installer failed with exit code: 0x80070002 : The system cannot find the file specified.

Open payn-git opened this issue 2 years ago • 7 comments

Windows Terminal version

1.14.1962.0

Windows build number

10.0.19042.1706

Other Software

No response

Steps to reproduce

run "winget install --id=Microsoft.WindowsTerminal -e" in admin command line

Expected Behavior

WT will install correctly :)

Actual Behavior

WTInstallFail

payn-git avatar Aug 04 '22 19:08 payn-git

@denelon any ideas here? Anything we can do to get more verbose info?

zadjii-msft avatar Aug 04 '22 21:08 zadjii-msft

I'd start with winget --info to see were logs go, then I'd run winget install Microsoft.WindowsTerminal --verbose-logs.

It could be the Windows 10 version is one older than the Windows 11 version:

  • https://github.com/microsoft/winget-cli/issues/2134

denelon avatar Aug 04 '22 22:08 denelon

Also, you're apparently on 1.14, but winget tried to install 1.13? That doesn't make sense...

If anything, the latest stable release was 1.14.1861.0. I think the 1.14.1962 release is the one we shipped as a hotfix (but never got around to publishing release notes due to some unexpected OOFages).

Regardless, I'd try the commands suggested above, to get more details.

zadjii-msft avatar Aug 05 '22 11:08 zadjii-msft

unexpected OOFages

😂

denelon avatar Aug 05 '22 15:08 denelon

FYI, on my Windows 10 system I think I see something similar:

image

So it seems something upstream for Winget is looking at the wrong version.

ashemedai avatar Aug 06 '22 09:08 ashemedai

Ah, it looks there are no manifests in https://github.com/microsoft/winget-pkgs/tree/master/manifests/m/Microsoft/WindowsTerminal after 1.13.11431.0. That would explain much.

ashemedai avatar Aug 06 '22 09:08 ashemedai

I guess no more info required from me than :).

payn-git avatar Aug 08 '22 23:08 payn-git

Oh derp yea, this is /dup #13542

zadjii-msft avatar Aug 10 '22 20:08 zadjii-msft

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

ghost avatar Aug 10 '22 20:08 ghost