0x80070043 ERROR_BAD_NET_NAME — Windows Error Code

Q: What does the Windows error code 0x80070043 mean?

It is the Win32 / NTSTATUS code ERROR_BAD_NET_NAME (decimal -2147024829). The network name cannot be found. Check the UNC path or DNS resolution.

Q: How do I decode 0x80070043 in PowerShell?

Run [ComponentModel.Win32Exception]::new(-2147024829).Message in any PowerShell session. For HRESULT-style codes, use err.exe from the Windows SDK or the WinDbg !error command.

Q: Where does Windows typically log this error?

It depends on the originating subsystem (Windows Update → %WinDir%\WindowsUpdate.log; AD/Kerberos → Security event log on the DC; BSOD → minidump under C:\Windows\Minidump; MSI → %TEMP%\msi*.log; WMI → Microsoft-Windows-WMI-Activity). Always cross-reference the timestamp and module name with the Application and System event logs.

Description

ERROR_BAD_NET_NAME (hex code 0x80070043, decimal -2147024829) is a Windows error-level error code in the RPC & Network family. Microsoft surfaces this code through the Win32 API, the Common Language Runtime, the kernel, the event log, PowerShell, command-line tools (sfc, dism, gpupdate, sc), and Windows-side applications such as Outlook, Teams, Office, and System Center.

The network name cannot be found. Check the UNC path or DNS resolution.

This page documents what triggers 0x80070043, the most common scenarios where it appears, the likely root causes, and a step-by-step troubleshooting workflow you can run against affected endpoints. It is intended for system administrators, MSP technicians, helpdesk engineers, and anyone diagnosing Windows behavior in a managed environment.

In-depth explanation

This is an error-severity code. Windows uses it to signal a failed operation that prevented the caller from completing its work. The underlying cause can range from a permissions or quota issue to a corrupted system component, missing dependency, or unreachable service.

It is part of the RPC / WinHTTP / WinINet error space and signals a failed remote call or HTTP/network operation. Most commonly seen with WMI, Group Policy, MMC consoles, and any tool relying on RPC.

The code can be looked up programmatically in PowerShell with [ComponentModel.Win32Exception]::new(-2147024829).Message (for Win32 / NTSTATUS codes that map cleanly), or with net helpmsg <decimal> for the legacy decimal range. For HRESULT-style codes, decode the facility and code with err.exe from the SDK or via the WinDbg !error command.

Common causes

Target service not running or listening on the expected port.
Windows Firewall blocking the dynamic RPC range (49152-65535) or the named pipe.
Network path obstruction (NAT, ACL, segmentation) between client and server.
RPC endpoint mapper (port 135) unreachable on the target.
DNS resolving the target to the wrong IP / IPv4 vs IPv6 mismatch.

Troubleshooting steps

From the client, run Test-NetConnection -ComputerName <target> -Port 135 to verify Endpoint Mapper reachability.
Check that the target service is running: sc \\<target> query <service>.
Verify Windows Firewall on the target allows the dynamic RPC range (49152-65535) and the named pipe used by the service.
Inspect Microsoft-Windows-RPC-Events log on both ends for the matching RPC error code.
If the client is multi-homed or behind a proxy, confirm correct binding order, IP, and absence of TLS / WAF interception.

Decode in PowerShell

# Decode 0x80070043 (-2147024829) in PowerShell
[ComponentModel.Win32Exception]::new(-2147024829).Message

# Or via WinDbg / err.exe (Windows SDK)
# err 0x80070043

# Or net helpmsg (legacy decimal range only)
# net helpmsg <decimal>

Frequently asked questions

What does the Windows error code 0x80070043 mean?

It is the Win32 / NTSTATUS code ERROR_BAD_NET_NAME (decimal -2147024829). The network name cannot be found. Check the UNC path or DNS resolution.

How do I decode 0x80070043 in PowerShell?

Run [ComponentModel.Win32Exception]::new(-2147024829).Message in any PowerShell session. For HRESULT-style codes, use err.exe from the Windows SDK or the WinDbg !error command.

Where does Windows typically log this error?

It depends on the originating subsystem (Windows Update → %WinDir%\WindowsUpdate.log; AD/Kerberos → Security event log on the DC; BSOD → minidump under C:\Windows\Minidump; MSI → %TEMP%\msi*.log; WMI → Microsoft-Windows-WMI-Activity). Always cross-reference the timestamp and module name with the Application and System event logs.

Is this code recoverable?

Critical-severity codes usually require kernel-level investigation (driver, hardware, system file repair). Error and warning codes are typically recoverable through the troubleshooting workflow on this page — start with the elevated-shell + log review steps.

Should I open a Microsoft support case for this?

Open a case if the error reproduces after applying the troubleshooting steps, particularly if it blocks production workloads, occurs across multiple endpoints, or is associated with a security boundary (BitLocker recovery, Kerberos failure, DCOM hardening, SmartScreen / WDAC). Have a fresh CBS log, minidump, or Get-WinEvent export ready before opening the case.