0x803f8001 | Terminal is not available on my Account #23980

Closed
opened 2026-01-31 08:58:00 +00:00 by claunia · 9 comments
Owner

Originally created by @Alex-265 on GitHub (Jan 21, 2026).

Windows Terminal version

I can't open the app

Windows build number

10.0.26100.7462

Other Software

No response

Steps to reproduce

Open Terminal

Expected Behavior

It would be pretty nice, if the terminal would open

Actual Behavior

A message popped up:
(Translated from german)
Check your Account
Terminal is not currently availiable on you account. Make sure you are signed in on the MIcrosoft Store and try again. Here is the error-code if you need it: 0x803f8001

https://github.com/user-attachments/assets/8f54d418-0d22-4681-a45e-5a2c778c9353

Originally created by @Alex-265 on GitHub (Jan 21, 2026). ### Windows Terminal version I can't open the app ### Windows build number 10.0.26100.7462 ### Other Software _No response_ ### Steps to reproduce Open Terminal ### Expected Behavior It would be pretty nice, if the terminal would open ### Actual Behavior A message popped up: (Translated from german) Check your Account Terminal is not currently availiable on you account. Make sure you are signed in on the MIcrosoft Store and try again. Here is the error-code if you need it: 0x803f8001 https://github.com/user-attachments/assets/8f54d418-0d22-4681-a45e-5a2c778c9353
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 08:58:01 +00:00
Author
Owner

@DHowett commented on GitHub (Jan 21, 2026):

That is very unusual.

Can you try to "Repair" the Terminal application? You can find this option in the "Installed Apps" section of Windows Settings.

Image Image
@DHowett commented on GitHub (Jan 21, 2026): That is very unusual. Can you try to "Repair" the Terminal application? You can find this option in the "Installed Apps" section of Windows Settings. <img width="1269" height="463" alt="Image" src="https://github.com/user-attachments/assets/f775cbc1-2cbe-41e7-88bb-d92acf86a56f" /> <img width="869" height="340" alt="Image" src="https://github.com/user-attachments/assets/4e688688-763a-424b-94d1-2faf4bd8e494" />
Author
Owner

@lbruno commented on GitHub (Jan 21, 2026):

this also happened to me, sorted by using the repair function.

lost the settings: terminal appearance, starting directory, specific font -- better than not having a terminal, but i can't be locked out of a terminal; there's a design flaw here

@lbruno commented on GitHub (Jan 21, 2026): this also happened to me, sorted by using the repair function. lost the settings: terminal appearance, starting directory, specific font -- better than not having a terminal, but i can't be locked out of a terminal; there's a design flaw here
Author
Owner

@Alex-265 commented on GitHub (Jan 21, 2026):

I uninstalled Windows Terminal and reinstalled it using winget (because the Microsoft Store didn’t work), and now it works.
I lost all my settings, though.
but why does my terminal need the microsoft store

@Alex-265 commented on GitHub (Jan 21, 2026): I uninstalled Windows Terminal and reinstalled it using winget (because the Microsoft Store didn’t work), and now it works. I lost all my settings, though. but why does my terminal need the microsoft store
Author
Owner

@zadjii-msft commented on GitHub (Jan 21, 2026):

It seems like something beyond our1 control happened to roll out some bad permissions... somehow. We1 gonna try tracking this down. We1 sure didn't push out any updates ourselves, but there are now a bunch of reports today of Terminal instances breaking in this way. I wonder if a Store cert broke or something...


  1. the terminal team ↩︎

@zadjii-msft commented on GitHub (Jan 21, 2026): It seems like something beyond our[^1] control happened to roll out some bad permissions... somehow. We[^1] gonna try tracking this down. We[^1] sure didn't push out any updates ourselves, but there are now a bunch of reports today of Terminal instances breaking in this way. I wonder if a Store cert broke or something... [^1]: the terminal team
Author
Owner

@mr-valente commented on GitHub (Jan 21, 2026):

It seems like something beyond our1 control happened to roll out some bad permissions... somehow. We1 gonna try tracking this down. We1 sure didn't push out any updates ourselves, but there are now a bunch of reports today of Terminal instances breaking in this way. I wonder if a Store cert broke or something...

Footnotes

  1. the terminal team ↩2 ↩3

Godspeed 🫡

I can't even open notepad, lol.

@mr-valente commented on GitHub (Jan 21, 2026): > It seems like something beyond our[1](#user-content-fn-1-f77905a77bd03d09b6ffb9500fcc57a8) control happened to roll out some bad permissions... somehow. We[1](#user-content-fn-1-f77905a77bd03d09b6ffb9500fcc57a8) gonna try tracking this down. We[1](#user-content-fn-1-f77905a77bd03d09b6ffb9500fcc57a8) sure didn't push out any updates ourselves, but there are now a bunch of reports today of Terminal instances breaking in this way. I wonder if a Store cert broke or something... > > ## Footnotes > 1. the terminal team [↩](#user-content-fnref-1-f77905a77bd03d09b6ffb9500fcc57a8) [↩2](#user-content-fnref-1-2-f77905a77bd03d09b6ffb9500fcc57a8) [↩3](#user-content-fnref-1-3-f77905a77bd03d09b6ffb9500fcc57a8) Godspeed 🫡 I can't even open notepad, lol.
Author
Owner

@lbruno commented on GitHub (Jan 21, 2026):

I uninstalled Windows Terminal and reinstalled it using winget

cool, i tried that too at some point, but didn't work; that could explain why i lost my settings, above i had attributed that to the repair function

for me, only repairing worked; winget uninstall + install from the cmd shell had no effect

[edit: this is on win10]

@lbruno commented on GitHub (Jan 21, 2026): > I uninstalled Windows Terminal and reinstalled it using winget cool, i tried that too at some point, but didn't work; that could explain why i lost my settings, above i had attributed that to the repair function for me, only repairing worked; winget uninstall + install from the cmd shell had no effect [edit: this is on win10]
Author
Owner

@ooree23 commented on GitHub (Jan 21, 2026):

In my case, I have the same issue with Paint, and screenshot tool... I can't launch them anymore.

A LOT of people are having the same issue, with many different apps :
https://learn.microsoft.com/en-us/answers/questions/5728884/error-0x803f8001
https://learn.microsoft.com/en-us/answers/questions/5729246/how-to-fix-error-code-0x803f8001

An article also talks about it : https://www.windowscentral.com/microsoft/windows-11/windows-11-apps-like-notepad-arent-loading-what-is-error-code-0x803f8001-and-how-d

@ooree23 commented on GitHub (Jan 21, 2026): In my case, I have the same issue with Paint, and screenshot tool... I can't launch them anymore. A LOT of people are having the same issue, with many different apps : https://learn.microsoft.com/en-us/answers/questions/5728884/error-0x803f8001 https://learn.microsoft.com/en-us/answers/questions/5729246/how-to-fix-error-code-0x803f8001 An article also talks about it : https://www.windowscentral.com/microsoft/windows-11/windows-11-apps-like-notepad-arent-loading-what-is-error-code-0x803f8001-and-how-d
Author
Owner

@WillyWonksters commented on GitHub (Jan 21, 2026):

For what it's worth, only one of my two systems is experiencing this issue.

The one with the issue is running windows 11, and the working system is running Linux.

@WillyWonksters commented on GitHub (Jan 21, 2026): For what it's worth, only one of my two systems is experiencing this issue. The one with the issue is running windows 11, and the working system is running Linux.
Author
Owner

@DHowett commented on GitHub (Jan 22, 2026):

The fix for this has been rolled out through the store server.

@DHowett commented on GitHub (Jan 22, 2026): The fix for this has been rolled out through the store server.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#23980