wsl: Failed to configure network (networkingMode Mirrored), falling back to networkingMode None.

[mlevis]

Windows Version

Microsoft Windows [Version 10.0.26100.8246]

WSL Version

24.04.3 LTS

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

No response

Distro Version

Ubuntu 24.04.3 LTS

Other Software

None error on startup

Repro Steps

Reboot and try to login. Happens more often then not

Expected Behavior

Networking works

Actual Behavior

No network access

Diagnostic Logs

z

Logs are 220mb. can't attach

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use .\collect-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues

Once completed please upload the output files to this GitHub issue.

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.

[hoshiizumiya]

Same as #11154

[chemwolf6922]

@mlevis Could you please share the log with a OneDrive share? Thanks.

[hoshiizumiya]

@chemwolf6922 It's 100% can be reproduced. Why not you just do it yourself. I can confirm it in the latest Windows server 2025.

[chemwolf6922]

@chemwolf6922 It's 100% can be reproduced. Why not you just do it yourself. I can conform it in the latest Windows server 2025.

This issue is not deterministic on all machines. If you can repro this on your machine, please help collect and share the log following instructions here: https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-detailed-logs

[mlevis]

@mlevis Could you please share the log with a OneDrive share? Thanks.

Uploading now

[mlevis]

https://1drv.ms/u/c/3fdadc879b5747b0/IQAJ7Fo5gUYgRIB-KOHqhpSDAWS1eNRW_2xi15KDFXKtUBM?e=qf7KgU

[chemwolf6922]

Hi @mlevis , Thanks for the log. However, the log does not seem to capture the start up of wsl. Could you please try do a system reboot, start the log collection script first, then start wsl? Thanks.

I noticed that Cisco AnyConnect was present in the hns log. Cisco AnyConnect is known to create troubles for WSL mirrored network mode. If possible, could you please try disable it and see if the problem persists? Thanks.

[mlevis]

No I can't uninstall Cisco anyconnect as it is required to connect t to my employers vpn. Which again is needed to connect to artifactory and our github repo. Without that I can't build our software or work.

…

On Thu, May 7, 2026, 23:37 Feng Wang ***@***.***> wrote: *chemwolf6922* left a comment (microsoft/WSL#40439) <#40439 (comment)> Hi @mlevis <https://github.com/mlevis> , Thanks for the log. However, the log does not seem to capture the start up of wsl. Could you please try do a system reboot, start the log collection script first, then start wsl? Thanks. I noticed that Cisco AnyConnect was present in the hns log. Cisco AnyConnect is known to create troubles for WSL mirrored network mode. If possible, could you please try uninstall it and see if the problem persists? Thanks. — Reply to this email directly, view it on GitHub <#40439 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAG3PMPUYGCNFV5USVWDAG34ZVI7JAVCNFSM6AAAAACYTAVRF6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIMBTGA4TENJYG4> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[chemwolf6922]

Hi @mlevis , Could you please try recollect the log with these steps so the log covers the start up of wsl? Thanks

• Reboot system.
• Don't run any wsl commands.
• Start the log collection script.
• Repro the issue.
• End the log collection script.

[hoshiizumiya]

@chemwolf6922 @benhillis

WslLogs-2026-05-10_22-30-29_2.zip

WslLogs-2026-05-10_22-24-11_2.zip

[mlevis]

I will try it again on Monday

…

On Sun, May 10, 2026, 10:48 hoshiizumiya ***@***.***> wrote: *hoshiizumiya* left a comment (microsoft/WSL#40439) <#40439 (comment)> @chemwolf6922 <https://github.com/chemwolf6922> @benhillis <https://github.com/benhillis> WslLogs-2026-05-10_22-30-29_2.zip <https://github.com/user-attachments/files/27569159/WslLogs-2026-05-10_22-30-29_2.zip> WslLogs-2026-05-10_22-24-11_2.zip <https://github.com/user-attachments/files/27568903/WslLogs-2026-05-10_22-24-11_2.zip> — Reply to this email directly, view it on GitHub <#40439 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAG3PMOSCRWVGWO2KQVV7DL42CJDFAVCNFSM6AAAAACYTAVRF6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIMJVGU3DKNBYGI> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>