ConEmu: Unable to launch Bash on Ubuntu on Windows on Windows Insider Build 15002
Versions
ConEmu build: 161206 x64 OS version: Windows 10 Pro x64 Insider Preview 15002.rs_prerelease.170102-1700 Used shell version (Far Manager, git-bash, cmd, powershell, cygwin, whatever): Bash on Ubuntu on Windows
Problem description
I updated my Windows Installation to Insider build 15002 this morning and now I’m unable to open bash with ConEmu. When I try to open bash I get the following error: Exception 0xC0000005 (Write x0000000001D26BEE) was occurred (ConEmu64.exe, PID=3944) ConEmu build 161206 64
I’m able to open Bash outside ConEmu just fine and I can open cmd, Powershell and git-bash (bundled with git from git-scm.com) in ConEmu just fine.
I tried to reinstall conemu and I tried to delete the conemu.xml file from AppDataRoaming but the issue persists.
Steps to reproduce
- Update to Windows Insider build 15002
- Open Bash on Ubuntu on Windows using ConEmu
Repro rate: 5/5
Actual results
An error popup appears (see screenshot “Capture”). When dismissing the popup ConEmu shuts down and Bash opens in a new non-ConEmu window (see screenshot “Capture2”)
Expected results
Bash should open normally inside ConEmu
Additional files
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 1
- Comments: 18 (9 by maintainers)
Commits related to this issue
- gh-1012: RegQueryValueEx crashed on Windows Insider Build 15002. — committed to Maximus5/ConEmu by Maximus5 7 years ago
- Internal. Ensure variables are initialized before RegQueryValueEx RegQueryValueEx crashed on Windows Insider Build 15002 while it's trying to acquire the performance counters. Seems like it's ... — committed to Maximus5/ConEmu by Maximus5 7 years ago
- gh-1012, gh-1121: Dirty workaround for AVDefender/Bitdefender bug raising a crash in the RegQueryValueEx. Warning! ConEmu physically can't fix 3rd-paty bugs! This commit just skips process bitnes... — committed to Maximus5/ConEmu by Maximus5 7 years ago
The bug doesn’t relate to BashOnWindows. It’s native Windows API bug.
I can confirm that the problem is indeed Bitdefender.
I am on 15019 Insider build. I had the same problem as the OP. Reading the posts here, I disabled BitDefender. And it just worked. I am able to reproduce the error every single time with Bitdefender turned on.
So, should we be reporting this to Bitdefender?
I should probably try replacing Bitdefender with another antivirus and check if the issue persists.
Perhaps it depends on BashOnWindows, but only MSDT devs may check that.
It works!