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

Error while running chkdsk c: /f command #21018

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

Originally created by @ghost on GitHub (Dec 25, 2023).

Windows Terminal version

1.18.3181.0

Windows build number

Win 10 22H2 19045.3693

Other Software

No response

Steps to reproduce

Open Terminal, type chkdsk c: /f command and press enter

I honestly don't know if it was a bug or not, I just wanted to report it here.

Expected Behavior

It should show the following warning as the Windows Command Prompt says.

Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts? (Y/N)

Actual Behavior

Terminal shows the following warning saying access is denied.

Access Denied as you do not have sufficient privileges or the disk may be locked by another process.
You have to invoke this utility running in elevated mode and make sure the disk is unlocked.

terminal-wcp

Originally created by @ghost on GitHub (Dec 25, 2023). ### Windows Terminal version 1.18.3181.0 ### Windows build number Win 10 22H2 19045.3693 ### Other Software _No response_ ### Steps to reproduce Open Terminal, type `chkdsk c: /f` command and press enter --- I honestly don't know if it was a bug or not, I just wanted to report it here. ### Expected Behavior It should show the following warning as the `Windows Command Prompt` says. `Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts? (Y/N)` ### Actual Behavior Terminal shows the following warning saying access is denied. ``` Access Denied as you do not have sufficient privileges or the disk may be locked by another process. You have to invoke this utility running in elevated mode and make sure the disk is unlocked. ``` ![terminal-wcp](https://github.com/microsoft/terminal/assets/153795294/d2369c96-b598-4ddc-b1ba-1392f57aee95)
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 07:30:48 +00:00
claunia commented 2026-01-31 07:30:49 +00:00
Author
Owner
Copy Link

@o-sdn-o commented on GitHub (Dec 25, 2023):

Have you tried running Windows Terminal as Administrator?

You have Command Prompt running as Administrator, and the terminal as a regular user.

@o-sdn-o commented on GitHub (Dec 25, 2023): Have you tried running Windows Terminal as Administrator? You have Command Prompt running as Administrator, and the terminal as a regular user.
claunia commented 2026-01-31 07:30:49 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 3, 2024):

Yea, despite your screenshot labeling the Terminal window as "Administrator", it doesn't have any of the hallmark signs of actually being launched as admin - the titlebar doesn't have a shield, the tab title is missing "Administrator", and CMD started in your user profile directory, instead of system32.

Does this work if you actually launch the Terminal as admin? Or moreover, how did you attempt to launch the Terminal as admin/?

@zadjii-msft commented on GitHub (Jan 3, 2024): Yea, despite your screenshot labeling the Terminal window as "Administrator", it doesn't have any of the hallmark signs of actually being launched as admin - the titlebar doesn't have a shield, the tab title is missing "Administrator", and CMD started in your user profile directory, instead of system32. Does this work if you actually launch the Terminal as admin? Or moreover, how did you attempt to launch the Terminal as admin/?
claunia commented 2026-01-31 07:30:49 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 6, 2024):

Or moreover, how did you attempt to launch the Terminal as admin/?

I enabled the "Run this profile as Administrator" setting. Because if I click on "Command Prompt (Admin)" in the Start menu, the old Command Prompt interface opens.

I could not find another option to start the Terminal as administrator.

prfl1

@ghost commented on GitHub (Jan 6, 2024): > Or moreover, how did you attempt to launch the Terminal as admin/? I enabled the "Run this profile as Administrator" setting. Because if I click on "Command Prompt (Admin)" in the Start menu, the old Command Prompt interface opens. I could not find another option to start the Terminal as administrator. ![prfl1](https://github.com/microsoft/terminal/assets/153795294/f757bf9c-7b5a-471a-bfaa-fd5e9548eb54)
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-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#21018
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?