Terminal: Terminal can't create pseudoconsoles when condrv isn't loaded [Error 0xd000003a]

[dkav]

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.

[DHowett-MSFT]

If you launch cmd, does powershell start working? I have a theory, but this will help me narrow it down.

[dkav]

Yes, launching the stand alone Command Prompt enables Powershell to start within Windows Terminal.

[DHowett-MSFT]

Okay, I bet condrv (our kernel driver) isn't being loaded. This is extremely rare, and only happens when no other console applications have been spawned on startup.

[dkav]

I have tried to keep the VM as spare as possible so I guess that would fit in with your hypothesis.

[DHowett-MSFT]

I've got an idea how to fix this, but the workaround is simple (launch a commandline app, or be on a non-stripped-out Windows); triaging into 1.x (not backlog), p2

[DIzFer]

I can also observe this exact behaviour on my system, which both has as little software installed as possible and on a virtual machine.

[revnode]

Seeing this on my laptop that's running Windows 10 ARM.

[cbrnr]

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

[ghost]

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.

[rfalanga]

@DHowett-MSFT the work around you gave on March 5th does work, but it is disconcerting. I had previously uninstalled FileZilla, which then required (so it said) me to reboot. As soon as my machine came back on the first thing I did was get into Windows Terminal, which launches a PowerShell 7.0.3 instance. Or tried, as I got that error. I thought that somehow uninstalling FileZilla had corrupted my machine. Until I came across this post. So, I thought brought up PowerShell, not Windows Terminal. That allowed me to bring up Windows Terminal.

Is this issue being worked on?

[DHowett]

"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

[AnthonyK213]

Same (not a VM). The error would be reproduced every time I restart the pc, which is really annoying. The windows is fresh installed (ver 1909), and the windows terminal is also newly installed (ver 1.2.2381.0).

[das-rob3rt]

Same. It's a Win10/KVM installation. Problem reproduces each time I boot up the guest OS. The workaround is to fire up a PowerShell console, and then close that. WT shall get functioning.