Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Unable to launch Bash on Ubuntu on Windows on Windows Insider Build 15002 #1012
ConEmu build: 161206 x64
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:
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
Repro rate: 5/5
An error popup appears (see screenshot "Capture").
Bash should open normally inside ConEmu
Try this link instead. https://drive.google.com/open?id=0B9uKIrTjhg2NcjE1Qm4yTF9IaVk
added a commit
Jan 11, 2017
Try this test build
I got this new error instead:
logs and memory dump: https://drive.google.com/open?id=0B9uKIrTjhg2NWXFYMmJ3UkJVSG8
Just to be clear this wasn't me doing something wrong. I just replaced the ConEmu64.exe in my installation with the one provided in the zip. Was this correct?
Things are worse that I can imagine. The crash occurs at
That means, the Insider build 15002 is broken completely. ConEmu can't do anything with that.
added a commit
Jan 18, 2017
@asser-dk I see BitDefender in the loaded modules. I'm almost sure it's not a problem, but can you run Bash/ConEmu without it to ensure?
@miniksa Can we do anything to troubleshoot or report the problem? At the moment it looks like a race in advapi32.dll (PerflibciSetObjectsValidityState). Two crash dump are available.
I looked again at the dump and it's very strange.
Having only 3 assembly instructions for this function (after looking at the source it is generated from) doesn't make any sense and makes me suspect something on @asser-dk's system has tampered with advapi32.
In comparison on my 15014 system, calling uf on the same function gives me 50+ assembly instructions, not 3. And it doesn't start with
Additionally, the exception itself...
The exception is a write access error to the memory at 1d26bee. But that's not where the heaps are with !heap and it's not inside any library or valid address space with !address. So if it's trying to write to invalid memory for no particularly good reason, that's why we hit an access violation.
But reading the source code for this function... there is no write operation that should be occurring immediately on entry to
So I further suspect something has tampered with advapi32.dll.
BitDefender could be a good suspect. AntiVirus applications commonly place hooks inside system DLLs and detour them. Perhaps this was a bad detouring of advapi32 or a hook/detour that can't compensate for some compiler/linker update that adjusted the layout of advapi32.dll.
So as of now, I don't really have anything to file unfortunately as it doesn't look like a race condition at all to me. It looks like some other piece of software on @asser-dk's system is tampering with system DLLs and that's not something we support. If it happens on a clean machine or another machine where we understand the full state of everything installed to reproduce it (so it can be proven that the system is at fault), I'm happy to file an internal bug and pass it along. @Maximus5, you're not seeing this at all on your machines, correct?
Sorry for the late reply. I've uninstalled the insider update and I'm currently on insider build 14986 where everything seems to work fine. I had a bunch of other applications that failed as well so it could be possible that the installation of the update was somehow flawed on my machine.
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.