terminal: Terminal can't create pseudoconsoles when condrv isn't loaded [Error 0xd000003a]
Environment
Windows build number: 0.9.433.0
Windows Terminal version (if applicable): 0.9.433.0
Running within VirtualBox VM.
Steps to reproduce
Start Windows Terminal after reboot.
Expected behavior
Powershell starts.
Actual behavior
Powershell does not start. Following messaged displayed - Error 0xd000003a when launching ‘powershell.exe’. Starting Powershell directly, which opens without a problem, and then opening Powershell in Windows Terminal fixes the problem.
The following is my PATH:
C:\Windows\system32
C:\Windows
C:\Windows\System32\Wbem
C:\Windows\System32\WindowsPowerShell\v1.0\
C:\Windows\System32\OpenSSH\
C:\Users\Darren\AppData\Local\Microsoft\WindowsApps
C:\Python27\ArcGIS10.8
C:\Program Files\ArcGIS\Pro\bin\Python\Scripts
Similar issue with Command and similar resolution.
About this issue
- Original URL
- State: open
- Created 4 years ago
- Reactions: 14
- Comments: 32 (6 by maintainers)
Commits related to this issue
- When spawning a pseudoconsole, make sure the console driver is loaded Fixes #4750. — committed to microsoft/terminal by DHowett 4 years ago
Hi there,
I just installed the 21H1 version of Windows 10, and I was facing this issue in Windows Terminal latest release v1.8.1444.0 after restarting my computer.
I quickly came across this issue, and I tried to follow this suggestion from @vefatica:
After changing the value from 3 to 2 in hexadecimal, the issue was resolved.
I guess this change could help in resolving this issue for everyone who is facing this problem. I hope you would try it, and let me know what happens.
Thanks, @TheBinitGhimire
Same on my machine (not a VM, standard installation) - this happens very often and I can’t start any of my profiles (Bash, Powershell, CMD).
Does the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\condrv\Start affect this? What if it were changed from 3 (manual) to 2 (autoload)?
This change fixed the issue for me.
I am having an almost identical issue on my main machine. I am using Windows 10 2004 x64. When I launch Windows Terminal after a reboot I am faced with this. However if I then launch CMD and reopen Windows Terminal the issue is fixed. I have CMD set as my default profile just FYI.
Had this issue within a Hyper-V VM, guest running 11 21H2 22000.194 Changing the registry key as per post above from @TheBinitGhimire resolved the issue.
Same issue. NOT A VM INSTALLATION
“Sort of.” The official mechanism by which we would load our driver is effectively a private API. I’m working on making sure we can actually ship that ;P
I can also observe this exact behaviour on my system, which both has as little software installed as possible and on a virtual machine.