0x80070043_
Update Failed � Bad Net Name
Windows 10/11 just hit error 0x80070043, which corresponds to a fault called "Update Failed � Bad Net Name". This is one of the most searched error codes for this OS — you're not alone, and there's a clear fix.
What Actually Happened
Windows 10/11 tried to install an update and the specific system condition behind it was 'the network name cannot be found'. Clearing the update cache and retrying resolves the majority of cases.
Symptoms
A Windows Update install fails or rolls back with error 0x80070043, sometimes after a restart loop
Common Causes
- The underlying Win32 condition ERROR_BAD_NET_NAME (the network name cannot be found) was raised while staging or applying the update
- The Windows Update cache (SoftwareDistribution) holds a stale or corrupted entry
- Insufficient free disk space to stage the update package
- A third-party antivirus or a Group Policy restriction is blocking the installer
How to Fix It
-
01
Run the built-in Windows Update Troubleshooter (Settings > System > Troubleshoot)
-
02
Stop the Windows Update service:
net stop wuauserv && net stop bits -
03
Rename the cache folder:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old -
04
Restart services:
net start wuauserv && net start bits -
05
Run system repair:
sfc /scannow && DISM /Online /Cleanup-Image /RestoreHealth
System Administrator Emergency Kit
Stop searching for syntax under pressure. Get 100+ verified, battle-tested emergency recovery commands for Windows & Linux in one printable PDF guide.
Root Cause Breakdown
0x80070043 is the HRESULT wrapping of Win32 error 67 (ERROR_BAD_NET_NAME): the network name cannot be found. The servicing stack (CBS) failed to complete the staging phase.
Should You Worry?
Safe to keep using your PC normally while working through the fix.
Power-User Tip
Before running DISM, renaming C:\Windows\SoftwareDistribution to SoftwareDistribution.old clears 80% of 0x80070043 failures instantly.
DIY fix: $0; Paid remote tech support if DISM repair fails: $40�$90