Welcome to Microsoft Q&A!
Thank you for taking the time to provide such detailed diagnostic information. The distinction you have made between a successful empty enumeration and a failure to enumerate the NAT objects is important here.
Get-NetNat has not returned an empty NAT inventory on this computer. The command failed before it could enumerate the configured NAT objects.
Get-NetNat (NetNat) can be described as retrieving NAT objects from the system. In your environment, the installed NetNat CDXML ultimately depends on root/StandardCimv2:MSFT_NetNat. Because MSFT_NetNat cannot currently be resolved, the appropriate interpretation is:
NAT inventory: indeterminate because enumeration failed.
It would not be safe to interpret this failure as "zero configured NAT objects."
There is also an important point regarding the Windows version. The current public documentation identifies Windows 11 version 26H2 as a released Windows version, and Windows 11 Pro 26H2 as an in-support release. Therefore, build 26300.9711 by itself is not sufficient evidence that this computer is currently running an Insider build.
The useful OS identifiers in your collection are therefore:
-
EditionID = Professional -
DisplayVersion = 26H2 -
CurrentBuild = 26300 - UBR = 9711
The ProductName = "Windows 10 Pro" value should not, by itself, be used to reclassify this installation as Windows 10. Likewise, 10.0.26300.0 identifies the base OS build but does not contain the servicing revision represented by UBR 9711. However, that documentation does not establish that MSFT_NetNat must be available under every Windows edition, optional-feature state, and servicing combination.
For that reason, the remaining useful information is the computer's actual Windows Insider enrollment/channel, OS architecture, update history, and complete optional-feature state.
Furthermore, the two WMI errors are meaningful, but they do not establish the underlying root cause by themselves.
- 0x80041010 means the specified class is not valid.
- 0x80041002 means the requested object cannot be found.
Based on the evidence you collected, we can reasonably establish that:
-
root/StandardCimv2itself is accessible becauseMSFT_NetAdaptercan be queried successfully. -
MSFT_NetNatis not currently available through CIM on this installation, and the behavior is the same in both standard and elevated sessions. - The WinNat service being Running confirms the service state, but it does not demonstrate that the
MSFT_NetNatmanagement class is registered and usable. - The
NetNattransition classes are separate CIM classes and cannot be used as substitutes forMSFT_NetNat. - The filtered
Win32Providerresult is not sufficient evidence to conclude that every potentially related provider registration is absent.
The working diagnosis is therefore a system/component-state-specific failure or absence of the MSFT_NetNat management-class exposure. Optional-feature state, servicing state, or a product issue could be involved, but the information currently available is not sufficient to identify which one is responsible.
I would avoid describing a particular provider registration or Windows component as definitively broken until Microsoft can validate that state against the corresponding Windows build. The same caution applies to HNS.
The available documentation does not establish HNS enumeration as a complete, one-to-one replacement for every NAT object normally returned through MSFT_NetNat. Therefore, the WSL ICS network and classic ICS connections you found should not be used to conclude either that all NetNat objects have been identified or that none exist.
Given your requirement to keep the investigation read-only, I recommend one non-destructive diagnostic collection path before making any repair or configuration changes.
Until the underlying problem is identified, record the NAT state as:
Unknown / indeterminate: MSFT_NetNat enumeration failed.
I would not reset the WMI repository, re-register providers, enable or disable Windows features, restart networking services, or change NAT configuration merely to make the enumeration succeed.
First, capture screenshots of:
winver
- Settings > Windows Update > Windows Insider Program, including the selected channel or confirmation that the device is not enrolled.
Then, from an elevated 64-bit Windows PowerShell session, please run and collect the following:
$Out = Join-Path $env:USERPROFILE 'Desktop\NetNat-26300.9711'
New-Item -ItemType Directory -Path $Out -Force | Out-Null
Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' |
Select-Object ProductName, EditionID, DisplayVersion,
CurrentBuild, CurrentBuildNumber, UBR |
Format-List |
Out-File "$Out\WindowsVersion.txt"
Get-ComputerInfo |
Select-Object WindowsProductName, WindowsVersion,
OsName, OsVersion, OsBuildNumber, OsArchitecture |
Format-List |
Out-File "$Out\ComputerInfo.txt"
Get-WindowsOptionalFeature -Online |
Sort-Object FeatureName |
Select-Object FeatureName, State |
Export-Csv "$Out\OptionalFeatures.csv" -NoTypeInformation
Get-Module NetNat -ListAvailable |
Select-Object Name, Version, Path |
Format-List |
Out-File "$Out\NetNatModule.txt"
Get-Service WinNat |
Format-List * |
Out-File "$Out\WinNatService.txt"
& {
'=== Get-CimClass ==='
Get-CimClass -Namespace root/StandardCimv2 `
-ClassName MSFT_NetNat -ErrorAction Continue
'=== Get-NetNat ==='
Get-NetNat -ErrorAction Continue
} *>&1 | Out-File "$Out\NetNatReproduction.txt"
Get-WinEvent -FilterHashtable @{
LogName = 'Microsoft-Windows-WMI-Activity/Operational'
StartTime = (Get-Date).AddHours(-1)
} -MaxEvents 200 -ErrorAction SilentlyContinue |
Select-Object TimeCreated, Id, LevelDisplayName,
ProviderName, Message |
Export-Csv "$Out\WMI-Activity.csv" -NoTypeInformation
msinfo32 /nfo "$Out\SystemInformation.nfo"
Get-WindowsOptionalFeature (Dism) can be used to obtain Windows optional-feature state, while msinfo32 provides additional system, hardware, component, and software-environment information.
This keeps the troubleshooting non-destructive and preserves the current system state for further investigation.
At this point, I understand why you are looking for a definitive explanation of why MSFT_NetNat is unavailable on this particular system, especially because the result needs to be reliable enough to protect a later controlled validation.
However, that question goes beyond what can be conclusively established through a Microsoft Q&A thread.
Microsoft Q&A is a public technical community. I can help interpret the documented behavior, review the diagnostic evidence, identify inconsistencies, and recommend safe troubleshooting based on Microsoft's published documentation. What I cannot do from the forum is inspect the affected computer's internal component and servicing state, access Microsoft-internal diagnostic telemetry, compare its provider registrations against a known-good installation of the same build, or engage the owning Windows engineering team to determine why the management class is unavailable.
For that reason, I don't want to present an assumption about the missing MSFT_NetNat class as a confirmed Microsoft root cause.
If you require a definitive determination for this particular computer, the appropriate next step is to open a Microsoft Support case and provide the diagnostic collection above together with the screenshots and the exact time at which the failure was reproduced.
Specifically, you can ask Support to validate whether MSFT_NetNat should be exposed on the corresponding Windows 11 Pro 26H2 configuration and to investigate whether its absence is caused by feature state, servicing/component inconsistency, or a product defect.
This does not mean that further community troubleshooting is impossible. Rather, the key distinction is that Microsoft Q&A can help narrow and document the problem, while a Microsoft Support case provides the environment-specific investigation and escalation path needed to establish the root cause.
Given the careful diagnostics you have already performed, escalating at this point also avoids making potentially unnecessary WMI or networking changes before the current state has been properly examined.
References:
Get-WindowsOptionalFeature (Dism) | Microsoft Learn
Get-NetNat (NetNat) | Microsoft Learn
Set up a NAT network | Microsoft Learn
WMI Error Constants (WbemCli.h) - Win32 apps | Microsoft Learn
Host Compute Network (HCN) service API for VMs and containers | Microsoft Learn
Get-HnsNetwork (HostNetworkingService) | Microsoft Learn
Windows 11 Home and Pro - Microsoft Lifecycle | Microsoft Learn
Windows 11, version 26H2 known issues and notifications | Microsoft Learn
If you find it useful, please click Accept Answer.
Thank you for choosing Microsoft Q&A.