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

Newly installed Windows Terminal - error 0xd000003a when launching powershell.exe #7878

New Issue
Closed
opened 2026-01-31 01:14:51 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 01:14:51 +00:00
Owner
Copy Link

Originally created by @jozefizso on GitHub (May 2, 2020).

Environment

Windows build number: Windows 10.0.18363.778
Windows Terminal version: 0.11.1191.0

Any other software?
No, this is a clean installation of Windows 10

Steps to reproduce

  1. Install new Windows 10 Professional 1909 64-bit
  2. Open Microsoft Store, search fro Windows Terminal
  3. Install Windows Terminal
  4. Run Windows Terminal from Start menu

Expected behavior

Windows Terminal should run the first time correctly.

Actual behavior

Error message is displayed: [error 0xd000003a] when launching `powershell.exe']

image

Originally created by @jozefizso on GitHub (May 2, 2020). # Environment ```none Windows build number: Windows 10.0.18363.778 Windows Terminal version: 0.11.1191.0 Any other software? No, this is a clean installation of Windows 10 ``` # Steps to reproduce 1. Install new Windows 10 Professional 1909 64-bit 2. Open Microsoft Store, search fro Windows Terminal 3. Install Windows Terminal 4. Run Windows Terminal from Start menu # Expected behavior Windows Terminal should run the first time correctly. # Actual behavior Error message is displayed: **[error 0xd000003a] when launching `powershell.exe']** ![image](https://user-images.githubusercontent.com/287778/80860413-caca5800-8c67-11ea-9eeb-d6532cb74e53.png)
claunia added the Resolution-Duplicate label 2026-01-31 01:14:51 +00:00
claunia commented 2026-01-31 01:14:52 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 3, 2020):

/dup #4750

This seems to happen in virtual machines more often than on real ones. You can work around it by launching a normal console application before launching Terminal. This should only be necessary one time.

@DHowett-MSFT commented on GitHub (May 3, 2020): /dup #4750 This seems to happen in virtual machines more often than on real ones. You can work around it by launching a normal console application before launching Terminal. This should only be necessary one time.
claunia commented 2026-01-31 01:14:52 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 3, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (May 3, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
claunia commented 2026-01-31 01:14:53 +00:00
Author
Owner
Copy Link

@jozefizso commented on GitHub (May 3, 2020):

Yes, this was a VM.

@jozefizso commented on GitHub (May 3, 2020): Yes, this was a VM.
claunia commented 2026-01-31 01:14:53 +00:00
Author
Owner
Copy Link

@genteelmagpie commented on GitHub (Apr 27, 2021):

I am not using it in a virtual machine. Just installed a clean windows from microsoft.com and I am getting the same error. Any ideas how to fix it ?

@genteelmagpie commented on GitHub (Apr 27, 2021): I am not using it in a virtual machine. Just installed a clean windows from microsoft.com and I am getting the same error. Any ideas how to fix it ?
claunia commented 2026-01-31 01:14:53 +00:00
Author
Owner
Copy Link

@svovel commented on GitHub (May 3, 2021):

I just got this issue now. Pretty fresh win10 VM in HyperV.
All was working fine, but after a reboot I got the 0xd000003a error when starting windows terminal with powershell 7 or cmd.
Starting powershell directly works and I'm then able to start windows terminal, but if I reboot I gotta do it all over again.

@svovel commented on GitHub (May 3, 2021): I just got this issue now. Pretty fresh win10 VM in HyperV. All was working fine, but after a reboot I got the 0xd000003a error when starting windows terminal with powershell 7 or cmd. Starting powershell directly works and I'm then able to start windows terminal, but if I reboot I gotta do it all over again.
claunia commented 2026-01-31 01:14:53 +00:00
Author
Owner
Copy Link

@bolte-io commented on GitHub (May 9, 2021):

Same here on the preview, loading it manually before opening terminal works.
Not on a VM, on latest 21H1 build of W10.

@bolte-io commented on GitHub (May 9, 2021): Same here on the preview, loading it manually before opening terminal works. Not on a VM, on latest 21H1 build of W10.
claunia commented 2026-01-31 01:14:54 +00:00
Author
Owner
Copy Link

@teknoraver commented on GitHub (Jul 13, 2023):

I have the same on a fresh VM install, with latest terminal

@teknoraver commented on GitHub (Jul 13, 2023): I have the same on a fresh VM install, with latest terminal
claunia commented 2026-01-31 01:14:54 +00:00
Author
Owner
Copy Link

@rayleigh1990 commented on GitHub (Aug 6, 2023):

I have the same on a fresh physical machine install(windows 21H2), with latest terminal 1.17.11461.0
when startup windows , this problem appears
but after wait for about 5 minutes later , terminal works correctly.

the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\condrv\Start
change it from 3 (manual) to 2 (autoload) will resolve it.

@rayleigh1990 commented on GitHub (Aug 6, 2023): I have the same on a fresh physical machine install(windows 21H2), with latest terminal 1.17.11461.0 when startup windows , this problem appears but after wait for about 5 minutes later , terminal works correctly. ------------------------------------------------------------------------------------------ the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\condrv\Start change it from 3 (manual) to 2 (autoload) will resolve it.
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 Resolution-Duplicate
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#7878
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?