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.

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

'The application cannot be started because it is currently updating" - No WSL2 Commands Work at All #10793

Closed
1 of 2 tasks
bebebib opened this issue Nov 19, 2023 · 2 comments
Closed
1 of 2 tasks

Comments

@bebebib
Copy link

bebebib commented Nov 19, 2023

Windows Version

Microsoft Windows [Version 10.0.19044.3448]

WSL Version

0.0.0.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

No response

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

Any time I run a WSL command in powershell, I am met with
The application cannot be started because it is currently updating.

There are no other obvious issues, and when I attempt to start WSL in another window with Terminal Preview I get

The application cannot be started because it is currently updating.

[process exited with code 1 (0x00000001)]
You can now close this terminal with Ctrl+D, or press Enter to restart.

There seems to be no way out of this, I have tried restarting my PC, killing WSL related tasks, etc. And I cannot really troubleshoot as all WSL commands in powershell return The application cannot be started because it is currently updating.

Expected Behavior

Ideally some WSL commands should work, such as version reporting, but The application cannot be started because it is currently updating. is all I get.

Actual Behavior

I get the following from WSL commands:

PS C:\Users\bebebib> wsl.exe --version
The application cannot be started because it is currently updating.

And starting a new window in Terminal Preview returns:

The application cannot be started because it is currently updating.

[process exited with code 1 (0x00000001)]
You can now close this terminal with Ctrl+D, or press Enter to restart.

There seems to be no other mention of people having a similar issue.

Diagnostic Logs

No response

Copy link

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@bebebib
Copy link
Author

bebebib commented Nov 19, 2023

Was able to solve it, noting this for others as it may be helpful, I went to Windows Settings -> Apps -> Windows Subsystem for Linux -> Advanced Options -> Repair, after I did this restarting the WSL terminal seemed to work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant