Netsh usage in WinPE environment - The supplied kernel information is invalid

Anonymous
2025-01-22T16:28:11+00:00

Hi,

we're trying to configure network inside a WinPE environment and in particular after injecting successfully via netsh the network configuration we need to restart network adapters, in order to enable the vlan id that we set.

The problem is that we are getting a generic error:

"The Supplied kernel information version is invalid"

The command we've issued to get this error is

netsh interface set interface "Nic name" DISABLED

all the other netsh commands are working correctly, we can even successfully rename the network interface, the only commands that are not working are enable/disable, which unfortunately are the ones that we need.

What could be causing this issue? How can we troubleshoot and solve this or is there any alternative method to disable/re-enable a nic interface in a preboot environment ?

Thanks

Windows Server Networking Network connectivity and file sharing

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Anonymous
    2025-01-23T14:52:02+00:00

    Hello.

    Based on the information you have provided, I recommend that you try to run the following command to see if it succeeds:

    netsh interface set interface "Nic name" admin=enable

    Best Regards

    ZUnhui

    0 comments No comments
  2. Anonymous
    2025-01-24T09:24:05+00:00

    Hello,

    thanks for the suggestion, I think those are exactly the commands that we are trying to use, but without luck:

    command and nic name seems to be correct, as we can successfully rename the nic for example.

    Any suggestion about how to troubleshoot this? Error seems to be pretty generic.

    Thanks

    0 comments No comments
  3. Anonymous
    2025-01-27T09:07:58+00:00

    Hello,

    Thanks for your reply. Based on the information you provided, I suspect that this may be a problem with the WMI repository. I suggest that you open cmd as an administrator and run the following command:

    winmgmt /verifyrepository

    If the result returned shows "WMI repository is inconsistent"

    Run the following command to reset the WMI repository:

    winmgmt /resetrepository

    Best Regards

    Zunhui

    0 comments No comments