Код ошибки 0x80041002

Also receiving this.

• Microsoft Windows 10 Pro, 19041.264
• I’ve uninstalled everything and even tried to re-install and having the same issue.
• Now i can’t even install an OS from MS Store :

Interesting, I suspect the error code is indicating something wrong with us trying to use hvsockets to communicate with the guest.

Could one of you please take a trace?

i have took trace while trying to load subsytem for issue #5340
logs.zip

I installed Windows 10 on a different driver in the hopes of fixing the issue, but now I am getting error 0x800706d9.

Here are mine.
logs1.zip.

ok. i have looked at logs and found error
Error, 3, 10420, onecorevmwsllxssservicelibutilityvmcontext.cpp, 1355, 0, 3, 10420, 0x80041002, HcnCreateNetwork failed (null), , , 1, 65,046756900
maybe it can be related to #4364 but i checked my 53 port and it is free

• Get-Process -Id (Get-NetUDPEndpoint -LocalPort 53).OwningProcess

•              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : ObjectNotFound: (53:UInt16) [Get-NetUDPEndpoint], CimJobException
  • FullyQualifiedErrorId : CmdletizationQuery_NotFound_LocalPort,Get-NetUDPEndpoint
    also i have no docker at my host or any custom dns service

Today!!! Before, more one week i use WSL2 fine! Today get a error:

Reinstall WSL; Virtual Machine Platform; All network drivers — nothing helped.

I found the issue. In my case, it was the COMODO Firewall. I disabled its components multiple times before converting the WSL, but it seems the only way to fix the issue, was to remove it completely.

Okey. Its problem in COMODO. WSL2 need a full access to WSL2 hosts(random)<->Loopback
IP 172.016.0.0 Mask 255.240.0.0 <-> IP 127.0.0.1 Mask 255.0.0.0
In comodo rules has repaired all my WSL

Update: Today error repeated again. Hyper-V Virtual adapter cannot be created.

cmd.exe (Admin)
net stop hns
net start hns

UPD: Comodo v12.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.

Issue on Comodo forum: https://forums.comodo.com/bug-reports-cis/ethernet-adapter-vethernet-wsl-cant-create-with-installed-comodo-t125940.0.html

on Windows build 19041.264 ,i dont have comodo or any antivirus apart from windows security center but i am still having this issue. and i dont also use docker on my PC. i only have vmware workstation 15.

Update

Get-Process -Id (Get-NetUDPEndpoint -LocalPort 53).OwningProcess
CCProxy was using that port so i stopped that service from windows service check the above command on powershell again install ubuntu wsl and start back my CCPoxy again.

Men Microsoft should just handled this error better than 0x80041002 Hexa Error

Hi,
I’m on Windows 10 ver.2004 (19041.329) and have exactly the same issue with WSL 2, I can install all following all steps from this Install WSL 2 on Windows 10.

All works good, the conversion to WSL 2 but when I reboot the system this error has shown all the time, uninstalling and reinstalling doesn’t work and uninstalling dnscrypt-proxy that was running on port 53 either.

Windows Events log shows this two errors:
1- SNP no pudo crear vmswitch con el error ‘0x80041002’ y el id. de adaptador = ‘4861B171-DCCF-4DFC-B11E-BDAA4D5FF7D9’.

2- HNS-Network-Create :-
Id. de red = ‘{b95d0c5e-57d4-412b-b571-18a81a16e005}’.
Tipo de red = ‘ICS’.
Código de resultado = ‘0x80041002’.

I have not been able to fix the error yet.

Okey. Its problem in COMODO. WSL2 need a full access to WSL2 hosts(random)<->Loopback
IP 172.016.0.0 Mask 255.240.0.0 <-> IP 127.0.0.1 Mask 255.0.0.0
In comodo rules has repaired all my WSL

Update: Today error repeated again. Hyper-V Virtual adapter cannot be created.

cmd.exe (Admin)
net stop hns
net start hns

UPD: Comodo v12.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.

Issue on Comodo forum: https://forums.comodo.com/bug-reports-cis/ethernet-adapter-vethernet-wsl-cant-create-with-installed-comodo-t125940.0.html

I’m having the issue too.
Can you share your COMODO settings (maybe your Firewall Zones and the order) ?
I disabled everything and then tried.. and I’m still getting issues.
Only works when I uninstall COMODO.

Comodo 12.0.0.6882 only work fine. Other versions NOT WORKING!
In this top Comodo MODERATOR post link for load this version:
https://forums.comodo.com/francais-french/comodo-internet-security-2019-v12006882-ndash-disponible-t124711.0.html;msg890652#msg890652

Add WSL zone: IP 172.016.0.0 Mask 255.240.0.0
Global rulles allow:
IP (IN&OUT): IN WSL zone (IP 172.016.0.0 Mask 255.240.0.0) -> OUT WSL zone (IP 172.016.0.0 Mask 255.240.0.0), IP-PROTO ANY;

AND (if really need)

IP (IN&OUT): IN WSL zone (IP 172.016.0.0 Mask 255.240.0.0) -> OUT Loopback (127.0.0.1), IP-PROTO ANY;
IP (IN&OUT): IN Loopback (127.0.0.1) -> OUT WSL zone (IP 172.016.0.0 Mask 255.240.0.0), IP-PROTO ANY;

Same issue for me. Cannot install anything.

Environment

Windows build number: Microsoft Windows [Version 10.0.19041.329]
Your Distribution version: Kali and Ubuntu 20.04LTS
Whether the issue is on: WSL 2 (set as default), WSL 1 is not affected

Steps to reproduce

1, Install distributive in Windows Appstore.
2. Start it to install into WSL.

Expected behavior

It should install.

Actual behavior

It is not installed showing Error: 0x80041002 (WslRegisterDistribution failed with error: 0x80041002)

logs.zip

The installation with WSL 1 was OK, but I cannot move to WSL 2 having the same error during conversion.

Comodo user here. I managed to resolve by disabling two settings:

• Auto-Containment (This setting I sometimes have to do with WSL1); And
• VirusScope

I have managed to do the following with no issues:

sudo apt update
sudo apt upgrade

Comodo Product Version: 12.2.2.7036
Windows: Version 2004 (OS Build 19041.329)
Ubuntu: 20.04

I managed to resolve by disabling two settings:

• Auto-Containment (This setting I sometimes have to do with WSL1); And
• VirusScope

Nope, did not help. In fact all these were disabled already.

Nope, did not help.

Did you uninstall/re-install Ubuntu first?

I would suggest:

• Uninstall Ubuntu
• Disable the two settings above
• Re-install ubuntu
• Run commands

Nope, did not help.

Did you uninstall/re-install Ubuntu first?

I would suggest:

• Uninstall Ubuntu
• Disable the two settings above
• Re-install ubuntu
• Run commands

I have installed it already using WSL 1, now I can simply try to convert it to WSL 2 to observe the error.
And again: these two settings were disabled from the beginning.

Sorry. I retract my «fix«. It didn’t help. I likely ran the commands in WSL1 mode.

I would like to note the following though:

# Show Default
PS C:Usersuser> wsl --list
Windows Subsystem for Linux Distributions:
Ubuntu-20.04 (Default)

# Show version
PS C:Usersuser> wsl --list --verbose
  NAME            STATE           VERSION
* Ubuntu-20.04    Stopped         1

# No Error
PS C:Usersuser> wsl --set-default-version 2
For information on key differences with WSL 2 please visit https://aka.ms/wsl2

# Error
PS C:Usersuser> wsl --set-version Ubuntu-20.04 2
Conversion in progress, this may take a few minutes...
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
Error: 0x80041002

@kinekt4 I can even add more.
After creation of Linux in WSL 1 you cannot open it in //wsl$/kali-linux (or any name — it depends what distributive you have installed).
After execution of wsl —set-version kali-linux 2 you will get an error, but //wsl$/kali-linux appears.

Another COMODO user here, getting this error when attempting to install Ubuntu.

I had Debian WSL2 installed for good. It worked perfectly and I had already plenty experience with WSL1.

Yesterday, I installed Comodo Internet Security Premium. After the second PC restart I hit this error and WSL became unusable. I turned off most Comodo features, reset some settings in it, but after an additional restart the problem still appears.

What to do?

Even after disabling every feature in COMODO and restarting the PC several times, WSL2 still refused to work.

WSL2 is more important for me, so I uninstalled COMODO entirely, restarted and… here you go.
WSL (and Docker Desktop) works as great as it did before.

This is the first time, I am so disappointed in COMODO…

@gjf
I agree with the most part you wrote in that topic.

Confirming your concerns, I cannot revert to your workaround.

The sole purpose I even upgraded my Windows version to the most currernt one is only WSL2. I need the quasi native Docker support, etc. So uninstallation of COMODO was the only option for me, after all.

However, I have been using COMODO since years and I never was this disappointed. I think it is still way better than most competitors out there. Look at Avast and Norton for example. They block games and create unforeseen/unexpected errors since so many years. So, at least comparatively, COMODO is not that bad.

@theAkito
I was so happy with introduction WSL2 having possibility to test kernel modules — and what a surprise!
I remember Comodo when it was a really good solution with fast and intuitive interface.
And now…
Damned marketing…

I updated comodo to 7036 version which was supposed to work but still it doesn’t :/

So they didn’t add it basically? Well removed comodo for now because WSL2 is way too great.

I updated to the latest version of COMODO, still getting this error when trying to install Ubuntu on WSL2, so perhaps is not quite fixed after all…

I updated to the latest version of COMODO, still getting this error when trying to install Ubuntu on WSL2, so perhaps is not quite fixed after all…

Read the post. It will be fixed in an update. Version 12.2.2.7062 was already out when this was stated. There is yet no update out.

I updated to the latest version of COMODO, still getting this error when trying to install Ubuntu on WSL2, so perhaps is not quite fixed after all…

Read the post. It will be fixed in an update. Version 12.2.2.7062 was already out when this was stated. There is yet no update out.

My bad, I thought it referenced the latest update but it did not… guess I’ll have to wait

https://docs.microsoft.com/zh-cn/windows/wsl/install-win10
=======================================
wsl --set-version kali-linux 2
ERROR: 0x80041002
=======================================
wsl --list --online
My wsl has no commont of "--online"
=======================================
wsl product version: 10.0.19041.488
wsl file version: 6.2.190401.488 
winver: Vsersion 20H2 (19042.804)
=======================================
COMODO FIREWALL version: 12.2.2.7098

Interesting, I suspect the error code is indicating something wrong with us trying to use hvsockets to communicate with the guest.

Could one of you please take a trace?

Do you wanna follow my issue? I can give you more logs or remote desktop to find out the problem and resolve it.

comodo FINALLY released an update which specifically claims to solve the issue (And it does for me).

Fixed

• WSL 2 can not work when install CIS

comodo FINALLY released an update which specifically claims to solve the issue (And it does for me).

Fixed

• WSL 2 can not work when install CIS

If only it wasn’t nearly a year later, long after I stopped using Comodo because of this issue.

Confirmed that version CFW 12.2.2.8012 is working fine with WSL2

Hey so i found a workaround that worked for me. Please try it and give feedback if it works.

1. I disabled the wsl feature and virtual machine platform
2. restarted and cleaned the registry with ccleaner
3. Re-enable 2 features mentioned in point no 1 and restart

it did the work for me.

This worked for me too. I guess I had changed something in the registry earlier which might have caused this problem.

I had the same issue I had to downgrade wsl 2 to wsl 1 and then install ubuntu again.

• run wsl --set-default-version 1 to downgrade and try reinstalling your distro

worked for me

Use comodo firewall 12.2.2.8012
worked for me

I don’t use the comodo firewall and the WSL update to version 2 is still showing this error.

wsl --set-version Ubuntu-20.04 2

Shows WSL2 Converstion Failed with Error: 0x80041002

I don’t use the comodo firewall and the WSL update to version 2 is still showing this error.

wsl --set-version Ubuntu-20.04 2

Shows WSL2 Converstion Failed with Error: 0x80041002

Upgrade to comodo 12.2.2.7098

I had the same problem. I got it to work by setting the WSL version to 1 via PowerShell:

wsl —set-default-version 1

I did want to use version 2, but having version 1 is better than nothing.

I had the same problem. I got it to work by setting the WSL version to 1 via PowerShell:

wsl —set-default-version 1

I did want to use version 2, but having version 1 is better than nothing.

Comodo is meant to have fixed the issue in an update, this workaround shouldn’t be required anymore @hamzaelgannouni

That fix though took around a year as far as I know to come out. And I made the decision after trying to live with it for a while that software that interferes with the os in a way it’s not meant to isn’t worth using when the devs don’t really care to fix it. And giving the amount of time it took, I read it as they didn’t. So I haven’t been using Comodo for a long time now.

If the latest version is screwing things up again then it really didn’t last long.

I fixed it by doing this:

• Enable Vritualization in bios
• wsl —set-default-version 1
• Install ubuntu
• wsl —set-version ubuntu 2
• wsl —set-default-version 2

I fixed it by doing this:

• Enable Vritualization in bios
• wsl —set-default-version 1
• Install ubuntu
• wsl —set-version ubuntu 2
• wsl —set-default-version 2

not worked! mei luan yong!

Running current distro on machine that has been fine for a year, suddenly stopped working.
Uninstalling and reinstalling proved impossible.
Installed WSL on a brand new machine app store refuses to download.
Install via comandline Error: 0x80041002 (null)

Nothing I do on any windows machine right now can get me a working copy of WSL. I cant do my job thanks windows.

I don’t use COMODO but get the same error 0x80041002 (use only windows defender and windows firewall)

So I had the same issue with my wsl2 installation and I dig deep until I found what the error 0x80041002 means. It basically means that the wsl2 couldn’t create a Hyper-V Virtual Ethernet Adapter. This error doesn’t come from wsl2, it comes from Hyper-V as shown in the event viewer.

First you NEED Hyper-V enabled, and second check if you have another vm adapter such as Oracle or vmware. In my case what happened was that I installed vmware in a second hard drive and I removed the HD from my PC, since the vmware ethernet adapter couldn’t find the source and IT’S linked to my Realtek physical controller, it somehow was making it impossible for Hyper-V to create a link as well.

Let’s say that whatever virtual machine you use WILL use your physical controller as a link and if one of your virtual adapter is failing, it will block others from linking as well.

So check if a vmware, oracle, VPN or anything is interfering with your physical controller because that’s what the code 0x80041002 means. Once more: «It can’t create a virtual ethernet adapter from the physical controller because something is blocking it from doing»

I want wsl2 for docker desktop and I got this error for more than a week, I don’t have comodo and Ubunto is not allowing me to set it to 2

The answer from sillasbernardo led me to right clicking on the VMWare executable installer file and then repair, and then it worked.