"Ethernet adapter vEthernet (WSL)" cant create with installed Comodo

Comodo Internet Security - CIS Resolved/Outdated Issues - CIS
1

New problem WSL2 & Comodo…
In Windows 2004 “Ethernet adapter vEthernet (WSL)” cannot create with installed Comodo. Without Comodo all fine. Turning off all the Comodo components not helped, full uninstall only.

WSL2:
Ubuntu\1804\2004
AlpineLinux

Windows 2004 (19041.264)

cmd.exe (Admin)


net stop hns
net start hns

In logs:


- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Microsoft-Windows-Host-Network-Service" Guid="{0c885e0d-6eb6-476c-a048-2457eed3a5c1}" /> 
  <EventID>1013</EventID> 
  <Version>0</Version> 
  <Level>2</Level> 
  <Task>0</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8000000000000000</Keywords> 
  <TimeCreated SystemTime="2020-06-07T04:06:35.4681956Z" /> 
  <EventRecordID>850</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="3044" ThreadID="4740" /> 
  <Channel>Microsoft-Windows-Host-Network-Service-Admin</Channel> 
  <Computer>LPWX-UWMS9QT</Computer> 
  <Security UserID="S-1-5-18" /> 
  </System>
- <EventData>
  <Data Name="Parameter0">HNS-Network-Create</Data> 
  <Data Name="Parameter1">{b95d0c5e-57d4-412b-b571-18a81a16e005}</Data> 
  <Data Name="Parameter2">7</Data> 
  <Data Name="Parameter3">0x80041002</Data> 
  </EventData>
  </Event>



- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Microsoft-Windows-Host-Network-Service" Guid="{0c885e0d-6eb6-476c-a048-2457eed3a5c1}" /> 
  <EventID>1002</EventID> 
  <Version>0</Version> 
  <Level>2</Level> 
  <Task>0</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8000000000000000</Keywords> 
  <TimeCreated SystemTime="2020-06-07T04:06:35.4600680Z" /> 
  <EventRecordID>849</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="3044" ThreadID="4740" /> 
  <Channel>Microsoft-Windows-Host-Network-Service-Admin</Channel> 
  <Computer>LPWX-UWMS9QT</Computer> 
  <Security UserID="S-1-5-18" /> 
  </System>
- <EventData>
  <Data Name="Parameter0">0x80041002</Data> 
  <Data Name="Parameter1">E7CF8A5F-9D8A-4934-9C37-96D688D8B9F0</Data> 
  <Data Name="Parameter2">WSL</Data> 
  </EventData>
  </Event>
2

Hello user0192,

Informed to Corresponding teams and they are checking in it.
Have a nice day!

Note : Please don’t create multiple posts for the same issue,it may create a redirection.

3

My COMODO version is 12.2.2.7036, but in %windir%\system32\guard64.dll version is 12.2.2.7032

Full uninstall Comodo 12.2.2.7036 by ciscleanuptool and then install last finded on my system Comodo installation package (12.1.0.6914):

Hyper-V Virtual Ethernet Adapter ( vEthernet (WSL) ) created automaticly when WSL2 is using.
Cannot install KillSwitch (Error:5) again, and my system sometimes freezes on 1-2 min. But… WSL2 is working!

upd: The system freezes often, many errors. I will be glad to any advice…

4

Same on my system Windows 7 64-bit, guard64.dll version is 12.2.2.7032

5

12.0.0.6882 working fine for me
no BSOD, no system freezing, no errors in logs. Creating vSwitch working fine, WSL2 too.
Winver: Windows 10, v2004 (19041.329) with installed all available updates on 6/10/2020.

UPD: Yeah! The best stability in Win10v2004! Workaround found. Fuf)
Next time I will test all previous versions of Comodo for 3 years first

6

Hello user0192,

Thank you for your response.For the v12.2.2.7036 - As per team fix will be included in the next release,teams are working in it.Once done let me notify you.
Have a nice day!

7

This is truly a huge issue. WSL2 is the most important application on my computer. I uninstalled COMODO Internet Security Premium, because I absolutely need WSL to work.

I hope there will be a huge announcement that will declare this issue fixed, so one can pick up this software again, once it is ready to be used.
Where can I stay up to date for this fixed release?

That said, for future readers of this topic, here the corresponding Github issue: WSL2 Converstion Failed with Error: 0x80041002 · Issue #5329 · microsoft/WSL · GitHub

8

You can use Comodo 12.0.0.6882. This works great!

Moderators posted a download link here:
https://forums.comodo.com/francais-french/comodo-internet-security-2019-v12006882-ndash-disponible-t124711.0.html;msg890652#msg890652

9

Chiming in also, longtime COMODO user, over 10 years now, and the latest version makes WSL2 unusable. Also waiting on a fix.

10

Hello Searinox,

Thank you for your reporting. As per team the WSL issue in v12.2.2.7036 is fixed and it will be reflecting in the upcoming release.
Have a nice day!

11

mmm… 8) how long we’ll wait new version? any preliminary dates, pls…

12

File guard64.dll seems to be freezing > https://forums.comodo.com/news-announcements-feedback-cis/comodo-internet-security-2020-v12227036-released-t125668.0.html;msg900006#msg900006

13

I unpacked the files from the CIS installer and 12.2.2.7032 is the version of the guard##.dll files. They were likely not updated in whatever changes .7036 contains.

14

Can we get some official confirmation which version now is absolutely confirmed to work?
I do not want another trial and error session. I want to download this software only, if I there is a certain confirmation, that this issue is fixed now.

15
  • i want more info too. No strength and no desire to reinstall several times…
16

Please check with 12.2.2.7062

17

Perfect! It works! WSL2 error message no longer appears. Linux subsystem starts now.

Thanks!

18

Can confirm, this seems to work. To double check, I restarted the computer after the successful installation and its initial scan. WSL2 still seems to work. Good job. Though, is there an offline installer for this version? I’d like to archive it myself instead of relying on it staying online, when it certainly will be taken down, at some point, anyway.

19

I guess, I needed to triple check! Double check wasn’t enough. After the second restart, my Docker Desktop did not want to start up. I tried everything (again) to get it running, including restarting the App, rebooting the computer again, disabling parts of Comodo, disabling all of Comodo. Nothing helped. After I uninstalled Comodo and rebooted the computer, Docker Desktop works fine again.

What a pitiful experience.

Comodo, please try to fix it actively, instead of trying to fix it as a random side effect.

You are a huge company and can afford some developer time and a Windows Pro license, on which installation you enable WSL2 and Docker Desktop. You need to test that it actually works with those 2 Apps. Comodo is nice, but the two mentioned applications are far more important, than Comodo.

20

Sorry but that sounds like a different issue not related at all to the original bug with WSLv2 not working due to the hyper-v virtual ethernet adapter not being created at startup. If you have an issue with docker then you need to make a separate bug report as this one appears to be fixed.