Error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. #20256

Closed
opened 2026-01-31 07:08:16 +00:00 by claunia · 12 comments
Owner

Originally created by @TheBigBear on GitHub (Jul 19, 2023).

Windows Terminal version

1.16.10261.0

Windows build number

10.0.20348.1787

Other Software

No response

Steps to reproduce

double click the windowsterminal icon and this message comes up ( also see screenshot )
Screenshot  2023-07-19 at 17 27 45

Expected Behavior

the WindowsTerminal application window should open instead.

Actual Behavior

it gives me the error shown here
Screenshot  2023-07-19 at 17 27 45

Originally created by @TheBigBear on GitHub (Jul 19, 2023). ### Windows Terminal version 1.16.10261.0 ### Windows build number 10.0.20348.1787 ### Other Software _No response_ ### Steps to reproduce double click the windowsterminal icon and this message comes up ( also see screenshot ) ![Screenshot 2023-07-19 at 17 27 45](https://github.com/microsoft/terminal/assets/471105/03fedb67-3525-40f7-b38a-ca7cdb63e6f3) ### Expected Behavior the WindowsTerminal application window should open instead. ### Actual Behavior it gives me the error shown here ![Screenshot 2023-07-19 at 17 27 45](https://github.com/microsoft/terminal/assets/471105/fb60c124-8b29-40ba-94a6-811800cc7a54)
claunia added the Needs-TriageIssue-BugNeeds-Author-FeedbackNo-Recent-Activity labels 2026-01-31 07:08:16 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Jul 19, 2023):

This may seem like a silly question, but did you manually disable any services/?

@zadjii-msft commented on GitHub (Jul 19, 2023): This may seem like a silly question, but did you manually disable any services/?
Author
Owner

@TheBigBear commented on GitHub (Jul 21, 2023):

@zadjii-msft not that I can remember. I have done a full comparison of any disabled services on this server and compared the list to the other servers where WindowsTerminal runs just fine. And even went as far as enabling them and seeing if that made a difference, but it did not.
A good question though. ;-) Are there any services that come to mind that the WindowsTerminal would check and that might be a potential culprit?

@TheBigBear commented on GitHub (Jul 21, 2023): @zadjii-msft not that I can remember. I have done a full comparison of any disabled services on this server and compared the list to the other servers where WindowsTerminal runs just fine. And even went as far as enabling them and seeing if that made a difference, but it did not. A good question though. ;-) Are there any services that come to mind that the WindowsTerminal would check and that might be a potential culprit?
Author
Owner

@jamespack commented on GitHub (Jul 23, 2023):

@zadjii-msft not that I can remember. I have done a full comparison of any disabled services on this server and compared the list to the other servers where WindowsTerminal runs just fine. And even went as far as enabling them and seeing if that made a difference, but it did not. A good question though. ;-) Are there any services that come to mind that the WindowsTerminal would check and that might be a potential culprit?

Shooting from the hip here. but seclogon. (Assuming you are in a corporate environment and your corporate environment disables that service using GPO to prevent running things as a different user)

@jamespack commented on GitHub (Jul 23, 2023): > @zadjii-msft not that I can remember. I have done a full comparison of any disabled services on this server and compared the list to the other servers where WindowsTerminal runs just fine. And even went as far as enabling them and seeing if that made a difference, but it did not. A good question though. ;-) Are there any services that come to mind that the WindowsTerminal would check and that might be a potential culprit? Shooting from the hip here. but seclogon. (Assuming you are in a corporate environment and your corporate environment disables that service using GPO to prevent running things as a different user)
Author
Owner

@carlos-zamora commented on GitHub (Jul 26, 2023):

Are there any services that come to mind that the WindowsTerminal would check and that might be a potential culprit?

Could you check if the Windows Update service is running?

@carlos-zamora commented on GitHub (Jul 26, 2023): > Are there any services that come to mind that the WindowsTerminal would check and that might be a potential culprit? Could you check if the Windows Update service is running?
Author
Owner

@zadjii-msft commented on GitHub (Jul 26, 2023):

As an aside, it also looks like this might be a Windows Server machine - how did you install the Terminal to that machine?

@zadjii-msft commented on GitHub (Jul 26, 2023): As an aside, it also looks like this might be a Windows Server machine - how did you install the Terminal to that machine?
Author
Owner

@TheBigBear commented on GitHub (Jul 27, 2023):

@zadjii-msft not that I can remember. I have done a full comparison of any disabled services on this server and compared the list to the other servers where WindowsTerminal runs just fine. And even went as far as enabling them and seeing if that made a difference, but it did not. A good question though. ;-) Are there any services that come to mind that the WindowsTerminal would check and that might be a potential culprit?

Shooting from the hip here. but seclogon. (Assuming you are in a corporate environment and your corporate environment disables that service using GPO to prevent running things as a different user)

@jamespack no, secondary logon is on automatic - I even started it manually - just to be sure. but no change. thanks for the feedback.

@TheBigBear commented on GitHub (Jul 27, 2023): > > @zadjii-msft not that I can remember. I have done a full comparison of any disabled services on this server and compared the list to the other servers where WindowsTerminal runs just fine. And even went as far as enabling them and seeing if that made a difference, but it did not. A good question though. ;-) Are there any services that come to mind that the WindowsTerminal would check and that might be a potential culprit? > > Shooting from the hip here. but seclogon. (Assuming you are in a corporate environment and your corporate environment disables that service using GPO to prevent running things as a different user) @jamespack no, secondary logon is on automatic - I even started it manually - just to be sure. but no change. thanks for the feedback.
Author
Owner

@TheBigBear commented on GitHub (Jul 27, 2023):

Are there any services that come to mind that the WindowsTerminal would check and that might be a potential culprit?

Could you check if the Windows Update service is running?

@carlos-zamora yes the windows update service is also running. thanks for the help.

@TheBigBear commented on GitHub (Jul 27, 2023): > > Are there any services that come to mind that the WindowsTerminal would check and that might be a potential culprit? > > Could you check if the Windows Update service is running? @carlos-zamora yes the windows update service is also running. thanks for the help.
Author
Owner

@TheBigBear commented on GitHub (Jul 27, 2023):

As an aside, it also looks like this might be a Windows Server machine - how did you install the Terminal to that machine?

@zadjii-msft yes, that is the point it is on a server 2022. I installed winget or the desktopappinstaller which does install from github to a recent enough server even without any ms store on it.
once winget was up and running I used it to install microsoft's windowsterminal.
but I could have also used chocolatey to install windowsterminal on the server 2022 machine.
thanks for your help.

@TheBigBear commented on GitHub (Jul 27, 2023): > As an aside, it also looks like this might be a Windows Server machine - how did you install the Terminal to that machine? @zadjii-msft yes, that is the point it is on a server 2022. I installed winget or the desktopappinstaller which does install from github to a recent enough server even without any ms store on it. once winget was up and running I used it to install microsoft's windowsterminal. but I could have also used chocolatey to install windowsterminal on the server 2022 machine. thanks for your help.
Author
Owner

@zadjii-msft commented on GitHub (Jul 27, 2023):

Huh, fascinating. @denelon You ever seen anything like this? I'm not sure how well winget works on Windows Server. I suspect it should just work fine, but maybe this is one of the edge cases?

Does an unpackaged install (straight from the .zip on our releases page) work?

(There's also the preinstall kits, which I don't really know how they work but I know have been useful in the past for installing on Server)

@zadjii-msft commented on GitHub (Jul 27, 2023): Huh, fascinating. @denelon You ever seen anything like this? I'm not sure how well winget works on Windows Server. I suspect it should just work fine, but maybe this is one of the edge cases? **Does an unpackaged install (straight from the .zip on our releases page) work**? (There's also the preinstall kits, which _I_ don't really know how they work but I know have been useful in the past for installing on Server)
Author
Owner

@zadjii-msft commented on GitHub (Jul 27, 2023):

oh lmao winget punted you to us https://github.com/microsoft/winget-cli/issues/3442

@zadjii-msft commented on GitHub (Jul 27, 2023): oh lmao winget punted you to us https://github.com/microsoft/winget-cli/issues/3442
Author
Owner

@microsoft-github-policy-service[bot] commented on GitHub (Aug 20, 2023):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@microsoft-github-policy-service[bot] commented on GitHub (Aug 20, 2023): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Author
Owner

@microsoft-github-policy-service[bot] commented on GitHub (Aug 20, 2023):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@microsoft-github-policy-service[bot] commented on GitHub (Aug 20, 2023): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20256