How to fix ‘Windows cannot access computer’ Error Code 0x80004005

Windows OS is positioned as an enterprise-friendly operating system with various features to support workgroups and the sharing of files and physical resources. Despite this focus, however, this flagship operating system seems to go out of its way to generate cryptic and user-hostile error messages for common problems.

How to fix ‘Windows cannot access computer’ Error Code 0x80004005

These error messages always make solving issues more complicated than it needs to be. Additionally, Microsoft tends to add a layer of confusion and frustration for intelligent but not computer-immersed users—people who could probably fix the problem if they knew something about its cause.

One of the more egregious offenders is Windows error code 0x80004005. This error generally happens during a failed attempt to use a shared resource over the network, such as a shared network hard drive. The usual syntax for this error is something along the lines of “Windows cannot access \Computer1, Check the spelling… Error code 0x80004005 Unspecified error.”

Of course, this super-helpful message on someone’s screen tells them nothing. As a result, it can be challenging to troubleshoot this error.

Don’t worry, though. Several methods get used to resolve this issue. This article discusses diagnosing and troubleshooting the underlying problems that error code 0x80004005 might represent.

What Causes Error code 0x80004005?

Unfortunately, diagnosing the cause isn’t as simple as we’d like. There are a few behaviors that can trigger the 0x80004005 error code. However, we’ve come up with this list to help narrow it down:

  • You are not signed in to the account with ownership of the file.
  • The program you’re using doesn’t support the file type.
  • A third-party program is blocking access to the files.
  • There is an error with the current version or latest update of Windows.

Other malfunctions can result in the error code. But fortunately, we’ve provided several fixes below.

Quick Fixes for the ‘Windows Cannot Access Computer’ Error 0x80004005

There are several “quick fixes” worth trying to resolve this error. These particular solutions often resolve the error code 0x80004005 issue.

While this isn’t a comprehensive list of all the possible solutions, there’s a good chance that one of these fixes will work for you.

Quick Fix 1: Update Windows

Microsoft releases updates to fix bugs and implement security patches. If you missed an update, let’s start there. Here’s what to do:

  1. Click on the Windows icon in the lower left corner. Then, click Settings.
  2. Click on Update & Security.
  3. Click Check for updates.

Perform any available updates. Then, check to see if the error disappears. If you continue having problems, keep reading.

Quick Fix 2: Disable IPv6

One fix to the 0x80004005 error code is to disable your computer’s IPv6 protocol. You don’t need IPv6 right now, anyway, unless you’re running an IPv6 network.

Just follow these four steps to try this fix:

  1. Right-click the Windows Start button and select “Network Connections.”
  2. Click “Change adapter options.”
  3. Right-click your network adapter and select “Properties.”
  4. Find “Internet Protocol Version 6 (TCP/IPv6)” in the center pane and uncheck the box.

Most network configurations still use IPv4 and will for the foreseeable future, so you won’t need IPv6 for a while unless you’re in an enterprise network already utilizing IPv6.

If this doesn’t resolve the error, then move on to the following suggested solution.

Quick Fix 3: Check NetBIOS

The next step to resolve error code 0x80004005 is ensuring the NetBIOS service is working. NetBIOS allows networked computers to share resources. If this isn’t working or isn’t enabled, it could cause the error to occur.

Follow these steps to check that the NetBIOS service is enabled:

  1. In the same window as above, highlight “IPv4” and click the “Properties” button underneath.
  2. Click “Advanced,” then select the “WINS” tab.
  3. Ensure the NetBIOS setting is at “Default.”

If NetBIOS is working as it should be, move on to the next possible solution.

Quick Fix 4: Check the Sharing Settings

If the NetBIOS settings weren’t the problem, look at the advanced sharing settings.

  1. Navigate to “Control Panel -> Network and Internet -> Network and Sharing Center -> Advanced sharing settings.”
  2. Click the “Private” network and ensure that “Turn on network discovery” is enabled and that the “Turn on automatic setup…” checkbox is enabled. Make sure “Turn on file and printer sharing” is also activated.
  3. Click “All Networks” and ensure the “Turn off password-protected network sharing” option is enabled.

If you changed the sharing settings, retest your share to see if it fixed the 0x80004005 error. If the changes did not fix the error code, move on to checking permissions.

Quick Fix 5: Check Permissions

  1. Right-click on the folder or drive you want to share, then select “Properties.”
  2. Click on the “Sharing” tab, then select “Advanced sharing.”
  3. Ensure the box found next to “Share this folder” appears checked, then click “Permissions.”
  4. Highlight the “Everyone” group, which should be in the top panel, and allow “Full Control.” If there isn’t an “Everyone” group, click “Add” and type “Everyone” in the bottom panel, then select it.

If permissions didn’t work for you, move on to re-downloading Windows 10 updates.

Quick Fix 6: Re-download Windows 10 Update

If you receive the error message with error code 0x80004005 while attempting to update Windows 10, the problem could get caused by a corrupt installation file.

To fix this, try re-downloading the Windows 10 installer and starting over. Frustrating as it may be, it’s worth a shot if this is the source of the problem.

Quick Fix 7: Enable SMB 1.0/CIFS File Sharing Support

As suggested by TechJunkie reader TFI, several users have reported that enabling SMB 1.0/CIFS File Sharing Support does the trick.

  1. In the search box, type “control panel,” then select “Programs and Features.”
  2. In the left-hand task pane, click on “Turn Windows features on or off.”
  3. In the dialog that comes up, scroll down and find “SMB 1.0/CIFS File Sharing Support.”
  4. Ensure the checkbox next to “SMB 1.0/CIFS File Sharing Support displays as checked.
  5. Click “OK.”

In closing, it can be frustrating and difficult to troubleshoot Windows 10 errors, and the error messages rarely provide any useful information.

Hopefully, one of the above processes helped you get your Windows 10 machine working correctly again. Have any other suggestions on dealing with this issue? Please share them with us in the comment section below!

For other Windows error codes, check out fixing the 0x80042405 error, fixes for the 0x80044004 error, how to deal with 0xc000007b errors, and view our take on error code 0x80240034.

28 thoughts on “How to fix ‘Windows cannot access computer’ Error Code 0x80004005”

John says:
Quick Fix 7 fixed the problem for me.
Achim says:
In my case, an old windows 7 installation would not connect anymore to my WD MyCloudEx2Ultra NAS, after I made a firmware update on the NAS. I tried all the registry hacks above, no success. But the I noticed that the NAS had its settings to SMB3 (only). I don’t know what it was set to before the firmware upgrade, but as soon as I switched that to support “SMB2 + 3”, my Win7 connected to it immediately. Could it be that Win7 never supported SMB3 in the first place?
Mineirinho says:
QUICK FIX 6 worked for me too! Thanks a lot….Bom bisurdo….
Ionuz says:
If you try accessing the share from another VLAN, please check the firewall.
Bobby McLean says:
Kudos to TechJunkie reader TFI…. Quick Fix 6 resolved the issue occurring when attempting to share access to a NAS Drive!
K says:
This worked for me:
HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\AllowInsecureGuestAuth set to 1
ray hope says:
Thank you – Thank you – Thank you – you are a superstar – after 3 days and no sleep this fixed it 🙂

(SOLVED) How to fix ‘Windows cannot access computer’ error code 0x80004005 – Ubuntu file server access from windows 10

Huib says:
Thanks for saving the day ! What a difference one tiny bit makes… NAS finally working (my fedora server already did). 😉
Mark says:
Eventually found a fix. 
I made sure the Smb1 was checked and then went to
and created a DWORD 
I found this on mt working PC and duplicated it. All working fine now.
Adam says:
You beautiful man. I just spent two hours to get to this.
kaox says:
yes! Quick Fix 6 did it for me. was trying to access a share on an older machine/os
Blake says:
quick Fix 6 was the answer! You are a lifesaver! I’ve been beating my head against the wall for days trying to get access to network folder. This did it! If you were near me I’d buy you a beer.
Sanya says:
You have saved me from installing a new windows just to solve this problem. I can also confirm that “Quick Fix 6: Enable SMB 1.0/CIFS File Sharing Support” can solve this problem but not the other option though. Thank you.
CrazyApple says:
Was getting frustrated while going through this list, but in the end Fix 6 resolved the issue. Thanks.
Ulrico Canzi says:
For me QUICK FIX 6 woks! Thanks a lot.
Nam says:
hehe # OK man. Thank you so much! I’m from VietNam.
ken says:
Quick Fix # 6 solved my issue, thanks a bunch.
Nikos says:
The only thing worked for me was to delete the following registry key:
Data Magician says:
Got it working with The “QUICK FIX 6: ENABLE SMB 1.0/CIFS FILE SHARING SUPPORT” solved my problem, that my computer could not connect to server.
David says:
Thank you very much for your help!
The “QUICK FIX 6: ENABLE SMB 1.0/CIFS FILE SHARING SUPPORT” solved my problem, that my computer could not connect to server.
Helgi says:
Installed all the components for SMB 1.0 and that fixed it. Was using Windows 10 Home. The other quick fixes did not fully solve the problem.
mahtab says:
thanks now it working
Martin says:
The Registry Entry has just solved my problem
Marin says:
Thanks for help guys!
Parameters\AllowInsecureGuestAuth set to 1 Worked!
Steve says:
I tried all of the above and nothing worked. On another thread I found this:

On thE wINDOWS 10 MACHINE Set the following registry value to 1


If its not there create the value as a DWORD

As soon as I did this it started working.

RWP says:
In my case (after no success with a lot of “try-this-try-that” posts) the problem turned out to be a Windows update that had broken the network file sharing connection. A Microsoft KB was issued later to fix the problem, but was not publicized to Windows users. I found out about it on an obscure geek website and got the KB myself. That fixed the problem.
cz says:
it is work for me – thanks
DesertSweeper says:
There is a much better way – wipe windows 10 and install windows 7
CurmudgeonlySignalVet says:
Don’t really see a benefit to installing an operating system that will no longer be supported or updated and will be considered a “dead” operating system as of July 2020 by Microsoft.
Tuan says:
Thank Steve.
” I tried all of the above and nothing worked. On another thread I found this:
On thE wINDOWS 10 MACHINE Set the following registry value to 1


If its not there create the value as a DWORD

It worked.

RWP says:
No such thing as “SMB 1.0/CIFS File Sharing Support” in my Windows features, and disabling IPv6 didn’t help either.
DonQuijote says:
Thank you man! You saved my day!
After I disabled the Internet Protocol Version 6 (TCP/IPv6), I can access to my folders 🙂
Top Fuel Racer says:
Thank you TFI….3 hours of troubleshooting this issue.
TFI says:
I had to re-enable Samba v1 on Windows to solve this problem. Simply go to control panel, “Programs and features”, click on the left on “Turn Windows features on or off”, then enable “SMB 1.0/CIFS File Sharing Support”
Mike says:
THANK YOU. THANK YOU THANK YOU. I had been fighting this for hours and the enabling smb1 did the trick.
Oli says:
Wow thank you so much, enabling SMB1 also fix my problem !!
A.S. says:
Thanks. Very straight forward and helpful. Might want to update the very beginning to add how to get to network connections with Win8 and Win10. But once you get there, very nice.
john says:
Thanks for the smbv 1 reference. That worked a peach

Leave a Reply

Your email address will not be published. Required fields are marked *

Disclaimer: Some pages on this site may include an affiliate link. This does not effect our editorial in any way.

Todays Highlights
How to See Google Search History
how to download photos from google photos