starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

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

New Issue
Closed
opened 2026-01-31 05:43:05 +00:00 by claunia · 10 comments
claunia commented 2026-01-31 05:43:05 +00:00
Owner
Copy Link

Originally created by @LoganDark on GitHub (May 10, 2022).

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.

Originally created by @LoganDark on GitHub (May 10, 2022). ### 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](https://github.com/microsoft/terminal/releases/tag/v1.12.10732.0)) ### 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](https://user-images.githubusercontent.com/4723091/167651479-e381f3be-ee8f-444f-a310-9504c6d9a910.png) 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.
claunia added the Needs-TriageIssue-BugNeeds-Tag-FixNeeds-Attention labels 2026-01-31 05:43:05 +00:00
claunia commented 2026-01-31 05:43:07 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 10, 2022):

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 commented on GitHub (May 10, 2022): 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.
claunia commented 2026-01-31 05:43:07 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 10, 2022):

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 commented on GitHub (May 10, 2022): FWIW, the only state the Terminal keeps around (on version 1.7) is the [`settings.json` file](https://github.com/microsoft/terminal/wiki/Frequently-Asked-Questions-(FAQ)#where-can-i-find-the-settings-file). If you want to go the manual uninstall route, just copy that file out somewhere before you uninstall 😉
claunia commented 2026-01-31 05:43:07 +00:00
Author
Owner
Copy Link

@LoganDark commented on GitHub (May 10, 2022):

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!

@LoganDark commented on GitHub (May 10, 2022): > 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](https://github.com/microsoft/terminal/wiki/Frequently-Asked-Questions-(FAQ)#where-can-i-find-the-settings-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!
claunia commented 2026-01-31 05:43:07 +00:00
Author
Owner
Copy Link

@LoganDark commented on GitHub (May 10, 2022):

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.

@LoganDark commented on GitHub (May 10, 2022): 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.
claunia commented 2026-01-31 05:43:07 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (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 commented on GitHub (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. :)
claunia commented 2026-01-31 05:43:08 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (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 commented on GitHub (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?
claunia commented 2026-01-31 05:43:08 +00:00
Author
Owner
Copy Link

@LoganDark commented on GitHub (May 10, 2022):

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

@LoganDark commented on GitHub (May 10, 2022): > Before installing Terminal 1.12, can you try installing the Microsoft.VCLibs package for your architecture? Looks like that was the problem! ![chrome_75fRaCljuP](https://user-images.githubusercontent.com/4723091/167671437-f438ae66-a9ca-4a1b-8dd8-3ea0e06260c0.png) > 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](https://user-images.githubusercontent.com/4723091/167672565-2e09d918-708a-4e1b-a0fd-2f96c749fc58.png)
claunia commented 2026-01-31 05:43:08 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (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 commented on GitHub (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!
claunia commented 2026-01-31 05:43:08 +00:00
Author
Owner
Copy Link

@LoganDark commented on GitHub (May 10, 2022):

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.

@LoganDark commented on GitHub (May 10, 2022): > 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.
claunia commented 2026-01-31 05:43:08 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 10, 2022):

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

@DHowett commented on GitHub (May 10, 2022): I believe so! That thing isn't really _great_ at error messages... :D
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Attention Needs-Tag-Fix Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#17457
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?