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

Cannot use System File Checker #23023

New Issue
Closed
opened 2026-01-31 08:30:07 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 08:30:07 +00:00
Owner
Copy Link

Originally created by @l-l-l-l-l-l on GitHub (Mar 15, 2025).

Windows Terminal version

1.22.10352.0

Windows build number

10.0.22631.5039

Other Software

No response

Steps to reproduce

  1. Open Terminal as administrator.
  2. Type sfc /scannow
  3. It returns "Windows Resource Protection could not start the repair service"
  4. Click on the dropdown button besides the tabs and clic on "Command Prompt"
  5. Type sfc /scannow
  6. It returns "Windows Resource Protection could not start the repair service"
  7. Go to the search bar in windows and tipe "command prompt"
  8. Open Command Prompt as administrator
  9. It opens outside Windows Terminal (if not run as admin, it opens inside)
  10. Type sfc /scannow
  11. It works now

Expected Behavior

Step 11 should have happened instead of step 3 (preferrably) or step 6. Step 6 in conjunction with 11 prove that the issue lies with Windows Terminal

Actual Behavior

I needed to use an insecure trick to do the most basic troubleshooting.

Originally created by @l-l-l-l-l-l on GitHub (Mar 15, 2025). ### Windows Terminal version 1.22.10352.0 ### Windows build number 10.0.22631.5039 ### Other Software _No response_ ### Steps to reproduce 1. Open Terminal as administrator. 2. Type `sfc /scannow` 3. It returns "Windows Resource Protection could not start the repair service" 4. Click on the dropdown button besides the tabs and clic on "Command Prompt" 5. Type `sfc /scannow` 6. It returns "Windows Resource Protection could not start the repair service" 7. Go to the search bar in windows and tipe "command prompt" 8. Open Command Prompt as administrator 9. It opens outside Windows Terminal (if not run as admin, it opens inside) 10. Type `sfc /scannow` 11. It works now ### Expected Behavior Step 11 should have happened instead of step 3 (preferrably) or step 6. Step 6 in conjunction with 11 prove that the issue lies with Windows Terminal ### Actual Behavior I needed to use an insecure trick to do the most basic troubleshooting.
claunia commented 2026-01-31 08:30:10 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Mar 19, 2025):

Unfortunately, this issue didn't reproduce on my machine when I tried it. I'm not entirely sure how to otherwise help you with this issue. Is there any other weird behavior you noticed while testing this?

One possibility is that this occurs because Windows Terminal runs in an app container. Sometimes this can result in weird issues depending on security settings. You could try this with our portable version which runs outside of the app container that Microsoft Store applications use. You can find it here: https://learn.microsoft.com/en-us/windows/terminal/distributions

I needed to use an insecure trick to do the most basic troubleshooting.

For what it's worth, the old command prompt ("console") is not insecure. Please feel free to use it as needed. (We maintain it!)

@lhecker commented on GitHub (Mar 19, 2025): Unfortunately, this issue didn't reproduce on my machine when I tried it. I'm not entirely sure how to otherwise help you with this issue. Is there any other weird behavior you noticed while testing this? One possibility is that this occurs because Windows Terminal runs in an app container. Sometimes this can result in weird issues depending on security settings. You could try this with our portable version which runs outside of the app container that Microsoft Store applications use. You can find it here: https://learn.microsoft.com/en-us/windows/terminal/distributions > I needed to use an insecure trick to do the most basic troubleshooting. For what it's worth, the old command prompt ("console") is not insecure. Please feel free to use it as needed. (We maintain it!)
claunia commented 2026-01-31 08:30:11 +00:00
Author
Owner
Copy Link

@l-l-l-l-l-l commented on GitHub (Mar 21, 2025):

Downloaded the x64 zip of the latest release and run it as admin. Results:

Image

Image

@l-l-l-l-l-l commented on GitHub (Mar 21, 2025): Downloaded the x64 zip of the latest release and run it as admin. Results: ![Image](https://github.com/user-attachments/assets/ffdb7c48-a507-4a22-849b-d0809b5faa56) ![Image](https://github.com/user-attachments/assets/0b2cf763-1883-40eb-8926-a9a1595c87fd)
claunia commented 2026-01-31 08:30:11 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 26, 2025):

That's quite unexpected. Are there by chance any logs in the Event Viewer when you do this?

@DHowett commented on GitHub (Mar 26, 2025): That's quite unexpected. Are there by chance any logs in the Event Viewer when you do this?
claunia commented 2026-01-31 08:30:12 +00:00
Author
Owner
Copy Link

@l-l-l-l-l-l commented on GitHub (Mar 28, 2025):

Not that I can find.

@l-l-l-l-l-l commented on GitHub (Mar 28, 2025): Not that I can find.
claunia commented 2026-01-31 08:30:12 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 28, 2025):

Huh. I can't repro this here on 27788 (though, if this is an OS issue that's fixed between those builds I'll eat a jalapeno)

What's the output of sc query trustedinstaller/?

From an unelevated terminal, does sudo sfc /scannow work? (after enabling sudo)

@zadjii-msft commented on GitHub (Mar 28, 2025): Huh. I can't repro this here on `27788` (though, if this is an OS issue that's fixed between those builds I'll eat a jalapeno) What's the output of `sc query trustedinstaller`/? From an unelevated terminal, does `sudo sfc /scannow` work? (after enabling sudo)
claunia commented 2026-01-31 08:30:12 +00:00
Author
Owner
Copy Link

@l-l-l-l-l-l commented on GitHub (Mar 29, 2025):

sc query trustedinstaller

NOMBRE_DE_SERVICIO: trustedinstaller
TIPO : 10 WIN32_OWN_PROCESS
ESTADO : 1 STOPPED
CÓDIGO_DE_SALIDA_DE_WIN32 : 0 (0x0)
CÓDIGO_DE_SALIDA_DEL_SERVICIO: 0 (0x0)
PUNTO_DE_CONTROL : 0x0
ESPERA : 0x0

I don't find the option to enable sudo (it should be at Settings>System>For developers, but it's not there), but while Terminal was stuck on an update yesterday (quite usual for me, I have to finish the installation manually for most apps, including the Store) and the default console was temporarily changed to Windows Powershell (I have both Powershell 7 and Windows Powershell, don't know why), sfc also didn't work with that even when elevated.

@l-l-l-l-l-l commented on GitHub (Mar 29, 2025): `sc query trustedinstaller` > NOMBRE_DE_SERVICIO: trustedinstaller > TIPO : 10 WIN32_OWN_PROCESS > ESTADO : 1 STOPPED > CÓDIGO_DE_SALIDA_DE_WIN32 : 0 (0x0) > CÓDIGO_DE_SALIDA_DEL_SERVICIO: 0 (0x0) > PUNTO_DE_CONTROL : 0x0 > ESPERA : 0x0 I don't find the option to enable sudo (it should be at Settings>System>For developers, but it's not there), but while Terminal was stuck on an update yesterday (quite usual for me, I have to finish the installation manually for most apps, including the Store) and the default console was temporarily changed to Windows Powershell (I have both Powershell 7 and Windows Powershell, don't know why), sfc also didn't work with that even when elevated.
claunia commented 2026-01-31 08:30:12 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 2, 2025):

Thanks for confirming!

changed to Windows Powershell ... also didn't work with that even when elevated.

Unfortunately, I think that points to a deeper-rooted issue on your system. At this point, I would use the Media Creation Tool and reinstall Windows.

@DHowett commented on GitHub (Apr 2, 2025): Thanks for confirming! > changed to Windows Powershell ... also didn't work with that even when elevated. Unfortunately, I think that points to a deeper-rooted issue on your system. At this point, I would use the Media Creation Tool and reinstall Windows.
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-Repro Needs-Tag-Fix Priority-3 Product-Terminal
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#23023
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?