Windows Error code 0x80004005 – What to do if the access to a network share is acknowledged with the error code 0x80004005?
The hint from Windows about an “unknown error” doesn’t really help – who would have thought that? Here I show you three possible solutions for the problem.
0x80004005 – Network error
When accessing network drives via the SMB protocol, the following error may occur:
Network error – xxx could not be accessed.
Make sure that the name is spelled correctly. There may be a network error. Click on “Diagnostics” to identify and fix the network problems.
Error Code: 0x80004005 (Unknown Error)
In this case, Windows has a problem with logging on, or connecting to the network path. This may be due to the following reasons:
the SMB protocol has been disabled
there is already a connection to the network destination
local permissions are not passed over the network
According to the motto “Reboot is always good” you should first reboot your Windows PC. If the error still occurs, you can follow the tips below.
Re-enable SMB protocol
Especially older NAS systems still use the outdated SMBv1 protocol. When using newer operating systems and installing current updates, the SMBv1 protocol may be disabled on the client. This will cause you to get the network error 0x80004005 when accessing such a share. Even though it is a security risk (keyword: crypto trojans) the SMBv1 protocol can be enabled very easily. You just have to open the Windows PowerShell with administrative rights and enter the following command:
Enable-WindowsOptionalFeature -Online -FeatureName smb1protocol
Confirm the security prompt with “Yes” and restart Windows. The SMBv1 protocol and access to such shares is now enabled again. Existing network connections trigger 0x80004005 Another way to get rid of the network error 0x80004005 is to remove all existing connections and then reconnect them. To do this, you must use either the Windows Command Prompt (cmd.exe) or Windows PowerShell. The following command will disconnect all existing network connections:
Again, a restart of the operating system is necessary.