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

Windows terminal won't launch, and cmd launches extremely late without being in windows terminal #23028

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

Originally created by @Jaren8r on GitHub (Mar 17, 2025).

Windows Terminal version

1.21.10351.0

Windows build number

10.0.26100.3476

Other Software

(Potentially) NVIDIA GeForce Game Ready Driver (572.70)

Steps to reproduce

Attempt to launch windows terminal or cmd

Expected Behavior

Either windows terminal or cmd launches

Actual Behavior

Windows terminal never launches, and cmd takes a long time to start and isn't in windows terminal.

This log is created in event viewer:

Error 1000, Application Error

Faulting application name: WindowsTerminal.exe, version: 1.21.2502.4001, time stamp: 0x67a2980a
Faulting module name: nvwgf2umx.dll, version: 32.0.15.7270, time stamp: 0x67c62399
Exception code: 0xc0000005
Fault offset: 0x000000000028590e
Faulting process id: 0x427C
Faulting application start time: 0x1DB96D838FEA2D3
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.21.10351.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_0fb2df354c49e826\nvwgf2umx.dll
Report Id: 0ced57de-8a5b-4dcd-a034-8517e84b08cd
Faulting package full name: Microsoft.WindowsTerminal_1.21.10351.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Feedback Hub: https://aka.ms/AAv35zv

Originally created by @Jaren8r on GitHub (Mar 17, 2025). ### Windows Terminal version 1.21.10351.0 ### Windows build number 10.0.26100.3476 ### Other Software (Potentially) NVIDIA GeForce Game Ready Driver (572.70) ### Steps to reproduce Attempt to launch windows terminal or cmd ### Expected Behavior Either windows terminal or cmd launches ### Actual Behavior Windows terminal never launches, and cmd takes a long time to start and isn't in windows terminal. This log is created in event viewer: Error 1000, Application Error ``` Faulting application name: WindowsTerminal.exe, version: 1.21.2502.4001, time stamp: 0x67a2980a Faulting module name: nvwgf2umx.dll, version: 32.0.15.7270, time stamp: 0x67c62399 Exception code: 0xc0000005 Fault offset: 0x000000000028590e Faulting process id: 0x427C Faulting application start time: 0x1DB96D838FEA2D3 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.21.10351.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_0fb2df354c49e826\nvwgf2umx.dll Report Id: 0ced57de-8a5b-4dcd-a034-8517e84b08cd Faulting package full name: Microsoft.WindowsTerminal_1.21.10351.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ``` Feedback Hub: https://aka.ms/AAv35zv
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:30:17 +00:00
claunia commented 2026-01-31 08:30:18 +00:00
Author
Owner
Copy Link

@UKR555 commented on GitHub (Mar 17, 2025):

  1. Roll Back or Update NVIDIA Drivers
    Open Device Manager (Win + X → Device Manager).
    Expand Display Adapters and right-click NVIDIA GPU.
    Click Properties → Driver tab.
    If you recently updated the driver, click Roll Back Driver.
    Otherwise, update the driver:
    Download and install the latest NVIDIA driver from NVIDIA's website.
    Use GeForce Experience to update drivers.

  2. Use Microsoft Basic Display Driver
    In Device Manager, right-click NVIDIA GPU → Disable Device.
    Restart your PC and check if Windows Terminal launches.
    If it works, the issue is likely the NVIDIA driver. Try updating or reinstalling it.

  3. Reinstall Windows Terminal
    Open PowerShell (Admin) (Win + X → PowerShell (Admin)).
    Run the following command to uninstall and reinstall Windows Terminal:
    powershell
    Get-AppxPackage Microsoft.WindowsTerminal | Remove-AppxPackage
    Then reinstall from Microsoft Store.

  4. Disable GPU Acceleration for Windows Terminal
    Open PowerShell (Win + R, type powershell, and press Enter).
    Run:
    powershell
    notepad $env:LOCALAPPDATA\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json
    In Notepad, add or modify this setting inside the root JSON object:
    json
    "experimental.rendering.forceSoftware": true
    Save and close the file.
    Try launching Windows Terminal again.

  5. Perform a System File Check
    Run Command Prompt as Administrator.
    Execute:
    cmd
    sfc /scannow
    If issues are found, restart your PC.

@UKR555 commented on GitHub (Mar 17, 2025): 1. Roll Back or Update NVIDIA Drivers Open Device Manager (Win + X → Device Manager). Expand Display Adapters and right-click NVIDIA GPU. Click Properties → Driver tab. If you recently updated the driver, click Roll Back Driver. Otherwise, update the driver: Download and install the latest NVIDIA driver from [NVIDIA's website](https://www.nvidia.com/download/index.aspx). Use GeForce Experience to update drivers. 2. Use Microsoft Basic Display Driver In Device Manager, right-click NVIDIA GPU → Disable Device. Restart your PC and check if Windows Terminal launches. If it works, the issue is likely the NVIDIA driver. Try updating or reinstalling it. 3. Reinstall Windows Terminal Open PowerShell (Admin) (Win + X → PowerShell (Admin)). Run the following command to uninstall and reinstall Windows Terminal: powershell Get-AppxPackage Microsoft.WindowsTerminal | Remove-AppxPackage Then reinstall from [Microsoft Store](https://apps.microsoft.com/store/detail/windows-terminal/9N0DX20HK701). 4. Disable GPU Acceleration for Windows Terminal Open PowerShell (Win + R, type powershell, and press Enter). Run: powershell notepad $env:LOCALAPPDATA\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json In Notepad, add or modify this setting inside the root JSON object: json "experimental.rendering.forceSoftware": true Save and close the file. Try launching Windows Terminal again. 5. Perform a System File Check Run Command Prompt as Administrator. Execute: cmd sfc /scannow If issues are found, restart your PC.
claunia commented 2026-01-31 08:30:19 +00:00
Author
Owner
Copy Link

@Jaren8r commented on GitHub (Mar 18, 2025):

Disabling my GPU in display adapters fixed the issue, but it disabled my non-primary monitors. My GPU driver at the time was the latest, but a new update was published today (572.83). After installing the new update, I can say that this is fixed and was on NVIDIA's side.

@Jaren8r commented on GitHub (Mar 18, 2025): Disabling my GPU in display adapters fixed the issue, but it disabled my non-primary monitors. My GPU driver at the time was the latest, but a new update was published today (572.83). After installing the new update, I can say that this is fixed and was on NVIDIA's side.
claunia commented 2026-01-31 08:30:19 +00:00
Author
Owner
Copy Link

@Arcovion commented on GitHub (Mar 25, 2025):

For those coming from Google searching for nvwgf2umx.dll, I also experienced this even though I was already on 572.83. Including cmd.exe taking a long time to load. The fix was to go to Nvidia drivers > Reinstall > Custom installation > Clean installation. Reinstalling by itself wasn't enough, but doing a 'clean' reinstall of the graphics driver fixed it for me.

@Arcovion commented on GitHub (Mar 25, 2025): For those coming from Google searching for `nvwgf2umx.dll`, I also experienced this even though I was already on 572.83. Including `cmd.exe` taking a long time to load. The fix was to go to Nvidia drivers > Reinstall > Custom installation > Clean installation. Reinstalling by itself wasn't enough, but doing a 'clean' reinstall of the graphics driver fixed it for me.
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-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#23028
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?