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

[jozefizso]

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']

[DHowett-MSFT]

/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.

[ghost]

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!

[jozefizso]

Yes, this was a VM.

[genteelmagpie]

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 ?

[svovel]

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.

[bolte-io]

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

[teknoraver]

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

[rayleigh1990]

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.