wsl crashes windows!

[Klystron]

Microsoft Windows [Version 10.0.17134.81]
What I did: typed 'windows key wsl enter' OR clicked bash.exe in c:\Windows\System32
Result: windows crashes, blue screen, microsoft says it's not their problem, baloney. Also cmd dir can't see bash.exe

c:\Windows\System32>dir bash.exe
Volume in drive C has no label.
Volume Serial Number is 025D-C2D0

Directory of c:\Windows\System32

File Not Found

Blue screen says 'STOP CODE: BAD_POOL_HEADER

I turned off wsl check box in control panel - windows rebooted. Re-checked it, rebooted. Installed Ubuntu. Same problem.
I can't run any linux programs 'cause it crashes before that.

[Klystron]

Problem fixed by disabling Avira antivirus 'real time protection'

[benhillis]

I suspect the issue is with their driver. I would suggest following with them to see if they are aware.

[sunilmut]

Problem is outside of WSL.

[exceptionalnull]

I contacted Avira about this and the suggested fix is to add the WSL files to the exception list in the real-time scanner options.

Hello,

thank you for your inquiry.

We would recommand to set the files of the WSL to the exceptions in the Antivirus-configuration.

File exceptions can be defined for both the “System Scanner” and the “Real-Time Protection”. A special feature of the “Real-Time Protection” is that processes may be excluded from the scan as well.

Exclude files or processes

1. Click the Avira icon in the taskbar to open Avira.
2. Search for Antivirus and click Open.
3. Click the settings symbol in the lower left corner.
4. Click PC Protection → Exceptions.

Since the exceptions for the “System Scanner” and “Real-Time Protection” must be configured separately, please select the corresponding module in the left panel. Search and add files or processes you want to be skipped by the Real-Time Protection or System Scanner and Real-Time Protection.

5. Click OK to save the configuration.

I haven't had the time to research exactly what folders and/or processes need to be added to the exception list yet. So I haven't tested their fix yet. I will try to remember to update this post when I figure it out.

[exceptionalnull]

UPDATE

This fix is more unstable than I originally thought. I just got another blue screen when I tried to use the ssh-copy-id command. I could successfully ssh into other servers and the ssh-keygen command worked fine. It is an improvement over not being able to run WSL at all but some commands could still trigger a crash. I don't know what the common thread is between root access and the ssh-copy-id command. I'd rather not randomly crash my computer so I can't recommend this fix.

Hopefully Avira will find a better fix for this problem. Otherwise I'll have to find a new AV.

---

So the fix is only partially successful very unstable. WSL will still crash on the initial setup and when you try to use sudo or su root. (Other commands are affected such as ssh-copy-id and ¿others?) Finding the directory is a bit of a pain as well.

These are the steps I used:

1. Installed the Debian package from the Microsoft Store but did not open it.
2. Executed this PowerShell command to find the install location: Get-AppxPackage -Name *debian* | select InstallLocation
3. Added that location to the Avira Files & Folders exception list as shown in my previous post.
4. Disabled Avira real-time protection.
5. Ran the Debian app for the initial setup which creates your non-admin user. Then closed the WSL window.
6. Re-enabled Avira real-time protection.

I also tested adding the Debian process (debian.exe) to the exception list along with the directory path. But it did not fix the crash on accessing root.

I can now run Debian with Avira real-time protection enabled. But if I try to su root or use sudo it causes the same blue screen crash as before. This procedure also worked for Kali Linux.

Also worth noting is that my initial WSL install was corrupt when I finally got into it. At least my resolv.conf file had been corrupted so I reinstalled the Debian app. I assume this is from the system crashing so many times. So it appears to be a damaging crash that can cause file corruption.

I've replied to Avira with this information and asked them if they can provide a better solution. I have a feeling if root access worked then the initial setup would also work.

Does someone know if I'm missing any locations that need to be added to the exception list?