Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Can't update from Windows Terminal 1.7 to 1.12 - "Windows Terminal is already installed" #13074

Closed
LoganDark opened this issue May 10, 2022 · 10 comments
Closed

Can't update from Windows Terminal 1.7 to 1.12 - "Windows Terminal is already installed" #13074

LoganDark opened this issue May 10, 2022 · 10 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@LoganDark
Copy link

LoganDark commented May 10, 2022 •
edited
Loading

Windows Terminal version

1.7.1033.0

Windows build number

10.0.19041.0

Other Software

I'm trying to update to Windows Terminal 1.12.10733.0 (Win10 version: Microsoft.WindowsTerminal_Win10_1.12.10733.0_8wekyb3d8bbwe.msixbundle, from this release)

Steps to reproduce

  1. Install Windows Terminal 1.7.1033.0
  2. Try to install Windows Terminal 1.12.10733.0

Expected Behavior

I should be able to update Windows Terminal

Actual Behavior

Windows won't let me update Windows Terminal:

image

It says "A newer version of Windows Terminal is already installed." (which is false).

Notes

In this case I'm not sure how this could be solved other than uninstalling the current version of Windows Terminal and installing the newer version fresh. I'm not sure how to keep my configuration intact if I uninstall the app though which is why I haven't tried it yet.
@LoganDark LoganDark added the Issue-Bug It either shouldn't be doing this or needs an investigation. label May 10, 2022
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels May 10, 2022
@LoganDark LoganDark mentioned this issue May 10, 2022
Closed
@zadjii-msft
Copy link
Member

Hmm. This is a crazy theory, so hear me out. I think there's an even newer version of terminal than 1.12.10733 in the Store. I'm wondering if secretly, the Store downloaded that version, has got it all staged, but is patiently waiting for you to stop using the Terminal before it installs it.

I know this is annoying, but does restarting your machine help? That might close out any running Terminal instances, make room for the store to do it's thing, and maybe when you boot back up you'll have the new one? It's a crazy theory, for sure.

@zadjii-msft
Copy link
Member

FWIW, the only state the Terminal keeps around (on version 1.7) is the settings.json file. If you want to go the manual uninstall route, just copy that file out somewhere before you uninstall 😉

@zadjii-msft zadjii-msft added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label May 10, 2022
@LoganDark
Copy link
Author

LoganDark commented May 10, 2022 •
edited
Loading

secretly, the Store downloaded that version, has got it all staged, but is patiently waiting for you to stop using the Terminal before it installs it.

That would be funny considering my Store can't connect to the Internet (intentional). Also Windows Terminal isn't running.

does restarting your machine help?

I'll try anyway, since Windows routinely gets all sorts of insane issues that only restarting can fix.

FWIW, the only state the Terminal keeps around (on version 1.7) is the settings.json file. If you want to go the manual uninstall route, just copy that file out somewhere before you uninstall 😉

Thanks, I'll keep that in mind!

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels May 10, 2022
@LoganDark
Copy link
Author

LoganDark commented May 10, 2022 •
edited
Loading

Looks like my version of Windows is not supported after all (#11371): Ask the developer for a new app package. This package may conflict with a package already installed, or it depends on things not installed here (package dependencies), or is made for a different architecture (0x80073CF3)

Oh well, I'll just go back a release. Installing 1.11 worked!

P.S. The 1.12 EXE works when extracted, but the package itself (even the Win10 one) won't install on my system, and C:\Program Files\WindowsApps\ is protected ridiculously heavily, so I guess I'm stuck forever now lol.

@DHowett DHowett reopened this May 10, 2022
@DHowett
Copy link
Member

DHowett commented May 10, 2022

This is pretty surprising, though! 1.12 should continue to work on your version of windows (as should 1.13! You're on 10.0.19041+, which is the latest public version of Windows 10).

I'm gonna reopen this to track it, since it might be a more widespread issue. :)

@DHowett
Copy link
Member

DHowett commented May 10, 2022

It looks like that error code is ERROR_INSTALL_RESOLVE_DEPENDENCY_FAILED. Can you try something for me?

Instead of downloading the Win10 msixbundle, try downloading the "Preinstall kit". It contains a bunch more libraries, like a package for Microsoft.VCLibs.140.00.UWPDesktop. Before installing Terminal 1.12, can you try installing the Microsoft.VCLibs package for your architecture?

@DHowett DHowett added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label May 10, 2022
@LoganDark
Copy link
Author

LoganDark commented May 10, 2022 •
edited
Loading

Before installing Terminal 1.12, can you try installing the Microsoft.VCLibs package for your architecture?

Looks like that was the problem!

chrome_75fRaCljuP

You're on 10.0.19041+, which is the latest public version of Windows 10

I haven't updated Windows in over a year so I have doubts about this. Isn't 20H2 / 22H2 or something the latest version? I'm on 2004 lol.

image

@ghost ghost removed the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label May 10, 2022
@DHowett
Copy link
Member

DHowett commented May 10, 2022

Isn't 20H2 / 22H2 or something the latest version

Something like that! 20H1 is "The version of Windows released in the first half of 2020". It's been "updated" (via service packs) a couple times to 20H2, 21H1, ... but that part doesn't truly matter. I always get my marketing names mixed up, so all we usually care about is build numbers. You're on build number 10.0.19041 or higher, which is the "baseline" build number[1] of the most recent actual version of Windows 10 that we care about.

[1]: The service packs update it to 19042, 19043 and beyond but those are actually a trick. The binaries on-disk are still numbered 19041. It's all sorts of strange!

I'll close this out as I think we've understood/addressed the main issue. Thanks!

@DHowett DHowett closed this as completed May 10, 2022
@LoganDark
Copy link
Author

I think we've understood/addressed the main issue.

Just to verify, the installer thinking that the older version was newer was caused by the dependency issue, right? That seems totally weird, but I guess on Windows anything can happen.

@DHowett
Copy link
Member

DHowett commented May 10, 2022

I believe so! That thing isn't really great at error messages... :D

@LoganDark LoganDark mentioned this issue May 14, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@DHowett @LoganDark @zadjii-msft