Error 0x80004005 is an unspecified Windows error, not a diagnosis. The correct fix depends on what you were doing when it appeared. If File Explorer cannot open a path such as \servershare, troubleshoot the SMB network connection, discovery, credentials, permissions and compatibility. If the code appeared during Windows Setup or an upgrade, use the Windows Update and installation branch instead; changing file-sharing security will not address that problem.
Work through the branch that matches the failure. Make the least disruptive checks first, and treat SMB1, guest access and disabled signing as temporary compatibility exceptions rather than normal fixes.
As an Amazon Associate I earn from qualifying purchases.
What error 0x80004005 means
Windows uses 0x80004005 for an “unspecified error.” The number alone does not identify a single fault. The same code can be raised by a failed network-share connection, an authentication refusal, an incompatible SMB protocol, or a Windows installation and upgrade problem.
The wording around the code is a useful clue. Messages such as “Windows cannot access \computer,” “I can see the computer but cannot open the shared folder,” or a failure when opening \servershare point to SMB networking. A message that appears while installing Windows, applying a feature update or rebooting into setup requires a different sequence.
#1 Best Overall
- Dual USB-A & USB-C Bootable Drive – compatible with nearly all Windows PCs, laptops, and tablets (UEFI & Legacy BIOS). Works with Surface devices and all major brands.
- Fully Customizable USB – easily Add, Replace, or Upgrade any compatible bootable ISO app, installer, or utility (clear step-by-step instructions included).
- Complete Windows Repair Toolkit – includes tools to remove viruses, reset passwords, recover lost files, and fix boot errors like BOOTMGR or NTLDR missing.
- Reinstall or Upgrade Windows – perform a clean reinstall of Windows 7 (32bit and 64bit), 10, or 11 (amd64 + arm64) to restore performance and stability. (Windows license not included.). Includes Full Driver Pack – ensures hardware compatibility after installation. Automatically detects and installs drivers for most PCs.
- Premium Hardware & Reliable Support – built with high-quality flash chips for speed and longevity. TECH STORE ON provides responsive customer support within 24 hours.
Identify the failure before changing settings
| What you were doing | Start with | Do not start with |
|---|---|---|
| Opening a shared folder or NAS path in File Explorer | Reachability, UNC path, discovery, permissions, credentials and SMB compatibility | Windows installation repairs |
| Connecting to a computer that appears under Network | Test the exact share and the account allowed to use it | Assuming that visibility means authorization |
| Installing Windows or applying an upgrade | Restart, Windows Update troubleshooting, update services and Safe Mode where appropriate | Changing SMB1, guest logons or signing policy |
Fix “Windows cannot access” when opening a shared folder
1. Test the scope and the exact path
First determine whether the problem is limited to one computer, one share or the whole network.
- From another computer on the same network, open the same share. If every client fails, investigate the server, NAS or network rather than only the affected Windows PC.
- On the affected PC, test the server name and the complete UNC path separately. For example, try
\server, then\servershare. A device can appear in Network while the particular share is unavailable or your account is not permitted to open it. - If you know the server’s address, test the path using the server name and, only as a diagnostic comparison, its IP address. A name that works while an IP address fails can indicate name resolution or authentication policy rather than a dead SMB service.
- Open Command Prompt and test a mapped connection with
net use. Microsoft documents the formnet use <DeviceName>: \<ServerName><ShareName>. The command can expose a more specific path, credential or connection error than File Explorer shows.
Record which of these tests succeeds. “The computer is visible” is a discovery result; “the authenticated account can open this share” is a permissions result. They are separate checks.
2. Confirm the network profile and sharing features
On a trusted home or office network, check the connection’s profile in Settings > Network & internet. The profile must match your organization’s policy. Do not switch an unknown or public network to Private merely to make discovery work.
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 errorsWhere policy permits, turn on Network discovery and File and printer sharing in Windows’ advanced sharing settings. These controls affect whether computers and shares are advertised and reachable; they do not grant access to a protected folder.
If the computer is still not discoverable, check these Windows services on the client and, where relevant, the server:
- Function Discovery Provider Host
- Function Discovery Resource Publication
- SSDP Discovery
- UPnP Device Host
Open Services, inspect each service and start it if your administrator allows it. A corporate policy, firewall rule or managed NAS configuration can intentionally disable discovery, so coordinate changes on managed networks.
3. Verify share permissions, NTFS permissions and credentials
Two permission layers can block a connection. The server’s share permission controls access through SMB, while the folder’s NTFS permission controls access to the files and subfolders. The effective permission is the more restrictive result. An account can therefore see a server but receive an access error when either layer excludes it.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall- On the server or NAS, identify the exact share name and the account or group that should have access.
- Check both the share ACL and the underlying folder’s NTFS ACL. Confirm that the intended account has at least the read or modify rights required for the task.
- Use a named account with a password when possible. Do not assume that a blank-password local account or an anonymous session will be accepted by current Windows security policy.
- If Windows is reusing an old mapping, disconnect it and remove only the stale credential for that server after you have a valid replacement. In Command Prompt,
net uselists existing connections;net use <drive>: /deleteremoves a selected mapping. Credential Manager can also contain saved Windows credentials. - Reconnect with the intended account. If several accounts are used on the same server, Windows may retain one authenticated session at a time; disconnect the old session before trying another identity.
Ask the server administrator to check its audit or authentication logs if the client receives a generic refusal. Those logs can distinguish a bad password, a disabled account, a denied share ACL and an unsupported protocol.
4. Prefer SMB2 or SMB3 and update an old NAS
Modern Windows and current NAS firmware should communicate with SMB2 or SMB3. An older NAS, media box or embedded device may still depend on SMB1/CIFS, which can explain why a share stopped working after a Windows update.
Before enabling a legacy protocol, update the NAS or server firmware and configuration so it can offer SMB2 or SMB3 with authenticated users. This change usually preserves stronger signing and authentication than falling back to SMB1.
If the device cannot yet be updated, Windows exposes SMB 1.0/CIFS File Sharing Support as an optional Windows feature. You can inspect it at Control Panel > Programs and Features > Turn Windows features on or off. Treat enabling SMB1 as a temporary, risk-reviewed bridge:
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Rank #2
- High-speed USB 3.0 performance of up to 150MB/s(1) [(1) Write to drive up to 15x faster than standard USB 2.0 drives (4MB/s); varies by drive capacity. Up to 150MB/s read speed. USB 3.0 port required. Based on internal testing; performance may be lower depending on host device, usage conditions, and other factors; 1MB=1,000,000 bytes]
- Transfer a full-length movie in less than 30 seconds(2) [(2) Based on 1.2GB MPEG-4 video transfer with USB 3.0 host device. Results may vary based on host device, file attributes and other factors]
- Transfer to drive up to 15 times faster than standard USB 2.0 drives(1)
- Sleek, durable metal casing
- Easy-to-use password protection for your private files(3) [(3)Password protection uses 128-bit AES encryption and is supported by Windows 7, Windows 8, Windows 10, and Mac OS X v10.9 plus; Software download required for Mac, visit the SanDisk SecureAccess support page]
- Confirm that the device owner accepts the security risk and that the device has no modern alternative.
- Enable only the SMB1 component required for the compatibility test, then restart if Windows requests it.
- Test the share and plan a server or NAS replacement, firmware update or protocol upgrade.
- Disable SMB1 again when the legacy dependency is removed.
SMB1 is deprecated and removed by default in current Windows configurations. It should not be the first or permanent answer to 0x80004005.
5. Account for Windows 11 24H2 SMB signing and guest changes
Starting with Windows 11 24H2 and Windows Server 2025, Microsoft requires SMB signing by default for inbound and outbound connections in the applicable Enterprise, Pro and Education editions. Unsigned traffic and guest fallback can therefore fail even when the same NAS worked before an update.
Signing requirements also affect guest access. Requiring signing disables guest access, and a third-party SMB server that cannot sign may reject the connection. The preferred remedy is on the server or NAS: update its software, enable SMB signing, and use authenticated accounts instead of guest sessions.
Disabling signing or enabling insecure guest logons weakens protection. Consider either change only as a controlled, temporary exception after the server owner accepts the risk, and document how to reverse it. Do not use a broad policy change merely because the device is visible in Network.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| Approach | Security posture | Where the change belongs | Best use |
|---|---|---|---|
| Enable authenticated SMB2/SMB3 with signing | Strongest of these options | Server or NAS, with matching client policy | Preferred long-term repair |
| Update or replace an SMB1-only device | Removes legacy exposure | Server or NAS | When an old device causes the failure |
| Temporarily enable SMB1 | Weaker; deprecated | Windows client and possibly server | Short diagnostic or migration bridge only |
| Temporarily allow guest or disable signing | Weakens authentication or integrity protection | Client and/or server policy | Exceptional, risk-accepted compatibility test |
6. Use a server name rather than an IP address for authenticated shares
For current authenticated environments, use a Kerberos-compatible server name whenever possible. Microsoft recommends names rather than IP-only paths because authentication can depend on name resolution and service principal names (SPNs).
If \servershare works but \192.0.2.10share fails, do not treat the IP result as proof that SMB is broken. Check DNS or local name resolution, the server’s SPN configuration and the authentication policy. If the name fails while the IP works, investigate discovery and DNS instead of permanently switching to an IP path.
Verification after each change
Change one factor at a time so you know what solved the problem. After each change:
- Disconnect any old mapping to the server.
- Close open File Explorer windows for the share.
- Reconnect using the intended server name, share name and account.
- Confirm that you can list the folder, open a small test file and create or modify a test file only if your account should have write access.
- Undo a temporary SMB1, guest or signing exception as soon as the server-side fix is available.
If another computer still connects while this PC does not, compare its network profile, saved credentials, Windows edition and SMB policy with the failing PC. If no client connects, inspect the NAS or server service, firmware, firewall and account logs.
Separate branch: 0x80004005 during Windows installation or upgrade
When the code appears in Windows Setup, Windows Update or an upgrade reboot, do not begin by changing SMB settings. This is a separate troubleshooting path.
- Restart the PC. A pending reboot can leave update components or setup operations in an incomplete state.
- Run the Windows Update Troubleshooter. In current Windows, open Settings > System > Troubleshoot > Other troubleshooters, select Windows Update and apply the recommended repairs.
- Check update services. Confirm that the Windows Update components required by your edition and organization are running and not disabled by policy. Managed PCs may require the administrator who controls update settings.
- Retry the update or installation. Record the exact stage and any accompanying message if the same code returns; the stage matters more than the generic number.
- Try Safe Mode where appropriate. Use Windows’ recovery options to enter Safe Mode, then retry the documented update or repair step if a startup program or driver is interfering. Safe Mode is not appropriate for every installation workflow, so follow the recovery screen’s supported option.
If setup fails repeatedly, preserve the exact edition, build, update identifier and setup log details before making broader changes. A network-share repair cannot correct an installer transaction that fails before Windows starts normally.
Quick Recap
When to escalate
- The share is unavailable from every computer, suggesting a server, NAS, firewall or network outage.
- The server rejects every authenticated account, indicating an account, ACL or server policy problem.
- The failure started immediately after Windows 11 24H2 or another version update and the device is an older NAS; involve the device vendor or administrator before weakening security.
- Changing a managed Windows policy is required; obtain approval rather than overriding organizational settings.
- The installation branch fails in Safe Mode or after the Windows Update Troubleshooter; retain setup details for Microsoft or your administrator.
As an optional shortcut, Outbyte PC Repair can try fixes for common Windows issues, including broken system elements and some app-crash problems, while also checking settings and cleaning temporary files. It runs on Windows 11, 10, 8 and 7 and offers a free trial by category of at least two days before a paid subscription. It complements antivirus software rather than replacing it; results vary, and no tool repairs every crash or network-share incompatibility.
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.
Recommended Free Tools
