Not able to install kernel object using `insmod`

[bvbasavaraju]

Windows Version

10.0.26100.4652

WSL Version

2.5.9.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.6.87.2

Distro Version

Ubuntu 20.04 and Ubuntu 24.04

Other Software

No response

Repro Steps

1. To clone the repo:

git clone https://github.com/microsoft/WSL2-Linux-Kernel.git .
git checkout linux-msft-wsl-${KERNEL_VERSION}

2. To configure and build the kernel:

cp Microsoft/config-wsl .config
make olddefconfig
make modules_prepare
make -j$(nproc) modules

3. Insert any kernel object or build any custom kernel object and try inserting it
   Ex: sudo insmod drivers/i2c/i2c-smbus.ko

Results in the error:
insmod: ERROR: could not insert module drivers/i2c/i2c-smbus.ko: Invalid module format

Expected Behavior

Successful installation of kernel object same has to be listed in the /dev/

Actual Behavior

Insmod result in following error:
insmod: ERROR: could not insert module drivers/i2c/i2c-smbus.ko: Invalid module format

in dmesg log says: disagrees about version of symbol module_layout

Diagnostic Logs

No response

[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-networking-logs.ps1, following the instructions here

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

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

[bvbasavaraju]

Please find the attached WSL logs as requested

WslLogs-2025-07-16_11-59-22.zip

[github-actions]

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information

Detected appx version: 2.5.9.0
Found no WSL traces in the logs

[bvbasavaraju]

Sure. I hope I have captured it correctly this time. Please find the attached. Please le me know if I need to do it again

WslLogs-2025-07-16_12-14-16.zip

[github-actions]

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information

Detected appx version: 2.5.9.0
Found no WSL traces in the logs

[bvbasavaraju]

I have reproduced and collected logs again.

Actually, it can be easily reproducible with the commands I have provided. It will hardly take 20 mins to reproduce the issue

WslLogs-2025-07-16_12-25-13.zip

[github-actions]

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information

Detected appx version: 2.5.9.0
Found no WSL traces in the logs

[bvbasavaraju]

I have done multiple times now. Could you please reproduce the steps?

Please follow below steps:

git clone https://github.com/microsoft/WSL2-Linux-Kernel.git .
git checkout linux-msft-wsl-${KERNEL_VERSION}

cp Microsoft/config-wsl .config
make olddefconfig
make modules_prepare
make -j$(nproc) modules

sudo insmod drivers/i2c/i2c-smbus.ko