Windows cannot access \\PC: error 0x80004005 Unspecified error
File Explorer shows a Network Error box: “Windows cannot access \\PC” (or \\PC\share). It adds “Check the spelling of the name. Otherwise, there might be a problem with your network.” and at the bottom Error code: 0x80004005 Unspecified error.
The short answer: 0x80004005 does not say what went wrong. Ask Windows again with net use, which gives you a real error number, and fix that.
What it means
Section titled “What it means”0x80004005 is E_FAIL. Microsoft’s list of common HRESULT values describes it as “Unspecified failure”. File Explorer shows it when the connection failed for a reason it does not name.
The same “Windows cannot access” box also appears with 0x80070035. That one is a clear error: system error 53, the network path was not found. This page is about 0x80004005.
Why it happens
Section titled “Why it happens”Because the code is general, there are several causes. Microsoft’s pages and Q&A answers point to these:
- The other side only offers guest access. Windows blocks guest sign-in to shares by default, and Windows 11 24H2 Pro, Enterprise and Education also require SMB signing, which guest sign-in cannot use. See guest access blocked.
- An old device only speaks SMB 1.0. SMB 1.0 is not installed by default on current Windows. An old NAS or router that only has SMB 1.0 cannot talk to a PC without it.
- Old saved sign-ins. Your PC still holds a connection or saved password for that PC from before.
- Sharing is not allowed on the other PC, or its firewall blocks file sharing.
- Permissions. The account you use may not read that folder. See you do not have permission to access.
How Devpit fixes or avoids it
Section titled “How Devpit fixes or avoids it”Share Files does not go through File Explorer, so you do not get its general “Unspecified error”. It reads the Windows error number behind a failure and, for the errors it knows, shows a plain sentence and a next step, in any Windows language. For example error 53 becomes “Cannot find that PC”, 1326 becomes “The user name or password is wrong”, 1219 becomes “Already signed in to that PC as someone else”, and 1272 becomes “Windows blocked the sign-in”. For a number it does not know, it shows the Windows text.
It also avoids the usual causes on the sharing side: it creates a temporary login with a password (no guest access), shares the folder read-only to that login only, gives that login read access to the folder, and turns on the firewall rule for file sharing if it is off.
The manual fix
Section titled “The manual fix”1. Get the real error number
Section titled “1. Get the real error number”Microsoft’s own advice for a share that File Explorer cannot open is to try it from Command Prompt with net use. Open Command Prompt and run:
net use \\192.168.1.20\shareUse the other PC’s IP address or name and the real share name. If it asks, type the user name and password. When it fails, net use prints “System error N has occurred” with a real number. Then:
| Number | Meaning | Go to |
|---|---|---|
| 53 | The network path was not found | System error 53 |
| 5 | Access is denied | No permission |
| 1326 | The user name or password is incorrect | System error 1326 |
| 1219 | Multiple connections by the same user | System error 1219 |
| 1272 | Guest sign-in was blocked | Guest access blocked |
If net use works, File Explorer will usually open the share after that too.
2. Clear old connections and saved passwords
Section titled “2. Clear old connections and saved passwords”- In Command Prompt, run
net use * /delete. If it asks to continue, answerY. It disconnects your PC’s shared-folder connections. It deletes no files. - Open Control Panel, Credential Manager, Windows Credentials. Remove saved entries that start with the other PC’s name or IP.
- Try the share again.
3. Check the sharing PC
Section titled “3. Check the sharing PC”- Its network should be Private: Settings, Network & internet, Wi-Fi or Ethernet, the network, Network profile type.
- File and printer sharing should be on under Private networks: Settings, Network & internet, Advanced network settings, Advanced sharing settings.
- The share should use a real account with a password, not guest access.
4. For an old NAS or router
Section titled “4. For an old NAS or router”Check the device maker’s site for a firmware update that supports SMB 2 or 3. Microsoft’s File Explorer guide lists turning on the SMB 1.0/CIFS Client feature, but Microsoft also says SMB 1.0 is not installed by default and should not be used. Use it only for a device that can never be updated, and turn it off again when you are done.
Microsoft’s page also lists one fix for this exact code: give the PC a fixed IP address instead of an automatic one. That helps when two devices got the same address. Most home networks do not need it.
Sources
Section titled “Sources”- Microsoft: Common HRESULT values (E_FAIL, 0x80004005)
- Microsoft: Can’t access shared folders from File Explorer (net use, SMB 1.0 client, 0x80004005)
- Microsoft: SMBv1 is not installed by default
- Microsoft: Troubleshoot SMB (net use * /delete)
- Microsoft: net use
- Microsoft Q&A: the “Check the spelling of the name” dialog with 0x80004005
- Microsoft support: Accessing Credential Manager
Common questions
What does 0x80004005 mean?
It is E_FAIL, which Microsoft lists as Unspecified failure. It is a general code. It says something went wrong but not what, so you need a second step to find the real cause.
Is 0x80004005 the same as 0x80070035?
No. 0x80070035 is system error 53, The network path was not found, which means Windows could not reach the PC or the share. 0x80004005 does not name a cause at all.
Should I turn on SMB 1.0 to fix it?
Only as a last resort for an old device that cannot be updated. SMB 1.0 is not installed by default on current Windows and Microsoft recommends against using it. Update or replace the old device if you can.