Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
In Windows, “extended error 53” refers to system error 53, which Microsoft’s Win32 error-code reference names ERROR_BAD_NETPATH (0x35) and defines as “The network path was not found.” The error means Windows could not reach the network path you requested. It is a symptom, not a diagnosis, so the useful work is finding which step in the chain failed: the path you typed, the name lookup, basic connectivity, or the share and service behind it.
Which “extended error 53” this article covers
The phrase “extended error 53” does not name an operating system or program, so it can mean different things in different software. This article covers the Windows system error. The definition and the troubleshooting guidance below come from Microsoft’s documentation for Windows. If your message comes from another application or platform, check that product’s own documentation before applying these steps, because the same number there may have a different meaning.
The code and the exact wording
- Error number: 53, which is 0x35 in hexadecimal.
- Win32 constant: ERROR_BAD_NETPATH.
- Microsoft definition: “The network path was not found.” (Microsoft’s Win32 system error-code reference)
- Message you may see: “System error 53 has occurred. The network path was not found.” (Microsoft’s guidance on accessing shared folders in Windows)
The code is a result returned by Windows. It does not carry a separate cause, so the same message can come from several different faults.
What the error does and does not tell you
Error 53 confirms that Windows failed to find the network path it was given. It does not, on its own, show that:
#1 Best Overall
- the remote computer is powered off;
- your user account lacks permission to the share;
- a specific device or network adapter has failed.
Microsoft’s TCP/IP guidance says error 53 can be returned when name resolution fails for a computer name used with net use. That is one documented cause, and the troubleshooting checks below are designed to tell it apart from the others.
Work through the checks in order
Run the checks in the sequence below. Each one isolates a different layer, so stop at the first check that fails and fix that layer before moving on.
Rank #2
- 15.6" diagonal, HD (1366 x 768), micro-edge, BrightView, 220 nits, 45% NTSC.
1. Confirm the complete UNC path
Check the computer name and share name for spelling and formatting. A path has the form \computernamesharename. For example, this command maps the share Reports on the computer FILESERVER:
Free tools Windows power users keep installed
One-click scans. No signup required.
net use \FILESERVERReports
Microsoft recommends verifying the name first whenever error 53 appears with net use. A missing backslash, a misspelled server name, or a share name that does not exist on that computer will all produce the same message.
Rank #3
- 10th Generation Intel Core i5-1035G1 processor
- 12GB system memory for full-power multitasking
- 256GB Solid State Drive
- 15.6" Micro-edge touchscreen display
2. Check that the computer name resolves to the intended address
Confirm that the name points to the address you expect. Microsoft’s guidance identifies failed name resolution as a cause. For a computer outside your local subnet, the name-to-IP mapping has to be available through the mapping source your network uses, such as DNS or WINS, so check that the entry exists and is correct.
3. Check basic connectivity to the target
Use ping against the computer name and then against its IP address:
Rank #4
- Latitude 7480 Laptop 14"
- Intel Core i7 6th Gen i7-6600U -Core Processor 2.6GHz (3.4GHz With Turbo Boost)
- 256 GB SSD Hard Drive & 16GB Memory
- 1920x1080 FHD resolution Non-Touch with Webcam and an integrated graphics chip
- Wireless Wifi & Bluetooth
ping FILESERVER
A reply shows that the target answers on the network, but it does not prove that the file share is reachable. Treat a successful ping as one signal, and continue to the share check even if it passes. If the name resolves to an address but ping fails, the problem is usually in the network path between the two machines rather than in the share itself.
4. Check the share and the SMB context
Confirm that the target computer is meant to expose the share and that the exact share path is valid. This is the layer where a missing or renamed share shows up. Microsoft has also documented a case in an older support article where error 53 appeared when File and Printer Sharing for Microsoft Networks was disabled or not installed. That article describes Windows 2000 and Windows Server 2003, so treat it as a historical example of how the layer can fail, not as a default setting to change on current Windows systems.
Best Value
5. Inspect the TCP/IP NetBIOS Helper service (specific SMB case)
Microsoft’s guidance on accessing shared folders documents one targeted remedy for error 53: the TCP/IP NetBIOS Helper service must run as Local Service. In the case Microsoft describes, the error occurs when that service is stopped or runs as Local System instead.
- Open the Services console by running
services.msc. - Find TCP/IP NetBIOS Helper and open its Properties.
- On the Log On tab, confirm the account is set to Local Service and that the service is running.
This remedy applies only to the case Microsoft describes. It is not a general fix for every network path error, so if the service is already running as Local Service, move on to the next check rather than changing it further.
6. When the name resolves but the share still fails
If the path is spelled correctly, the name resolves, the target responds, and the share exists, the remaining causes sit in the share’s network configuration or policy. At this point, involve the administrator who controls the server. Do not disable a firewall or weaken guest-access or other security settings to see whether the error changes. Change those controls only when you have evidence that they explain your specific case.
Where each check fails
The table below shows what each failing check points to. Use it to decide where to look next rather than trying every fix at once.
| Check that fails | What it points to | Next step |
|---|---|---|
| UNC path (spelling, slashes, share name) | A naming error in the path you typed | Correct the computer and share names, then retry net use |
| Name does not resolve to the expected address | Name-to-address mapping (for example, DNS or WINS entry) | Check the mapping source with your network administrator |
| Name resolves, but ping fails | Basic connectivity between the machines | Check the network path and the target’s availability |
| Ping succeeds, but the share still fails | Share availability or the SMB configuration on the target | Confirm the share exists and is meant to be exposed; escalate with the administrator |
| TCP/IP NetBIOS Helper stopped or running as Local System (in the case Microsoft documents) | The Windows service configuration on the client | Set the service to run as Local Service and confirm it is running |
Extended error 53 in other contexts
If the number 53 appears in a program that is not part of Windows networking, the Windows definition above does not transfer. Look up that application’s own error list. Only apply the Windows steps when the message names a network path or a shared folder.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
