Shared folders between Windows 11 computers let devices on the same local network open files without emailing them or uploading them to cloud storage. A reliable setup requires more than selecting Share: the network must be trusted, discovery and file sharing must be enabled, and both sharing and file-system permissions must allow the intended access.
The secure default is to keep password-protected sharing enabled and grant access to a named Windows user. Use Everyone only for a low-risk folder on a trusted private network, never as a shortcut on public Wi-Fi.
Decide who should have access
Choose the permission before configuring the folder:
| Goal | User to add | Permission |
|---|---|---|
| Let one person view files | That Windows user | Read |
| Let one person add, edit, and delete files | That Windows user | Read/Write or Change |
| Let trusted household PCs view a non-sensitive folder | Everyone | Read |
| Share confidential or administrative data | Specific named users only | Minimum access required |
Read allows a person to open and copy files. Change or Read/Write also permits creating, editing, renaming, and deleting items. Do not grant write access when viewing is sufficient.
Prepare both computers
The two PCs must be connected to the same local network, but that network does not need internet access. Ethernet and Wi-Fi can work together when the router places both devices on the same local network and does not isolate wireless clients.
On each computer:
- Open Settings > Network & internet.
- Select the active Wi-Fi or Ethernet connection.
- Set Network profile type to Private network.
A Private profile tells Windows that device discovery and sharing may be appropriate. Do not change a hotel, airport, café, or other untrusted network to Private merely to make sharing work.
Next, open:
Settings > Network & internet > Advanced network settings > Advanced sharing settings
Under Private networks, turn on:
- Network discovery
- File and printer sharing
Enable automatic setup of network-connected devices when Windows displays that option. Leave password-protected sharing turned on under All networks for the named-user setup described below.
Microsoft’s current Windows network file-sharing guide confirms these discovery and sharing requirements.
Share the folder with a specific user
Create or identify an account on the computer that owns the files. The connecting user will need credentials accepted by that host computer. A Windows Hello PIN used to unlock a PC is not necessarily the password required for a network connection.
Then share the folder:
- Right-click the folder and select Show more options when needed.
- Choose Give access to > Specific people.
- Select a user from the list or enter the account name.
- Select Add.
- Choose Read or Read/Write.
- Select Share, then note the displayed network path.
The path normally follows this format:
\\ComputerName\ShareNameShare a dedicated folder rather than the root of the Windows drive or an entire user profile. This makes permissions easier to understand and limits accidental exposure.
Understand the two permission layers
Windows evaluates both share permissions and NTFS permissions from the folder’s Security tab. A user needs permission through both layers, and the more restrictive effective result wins for network access.
For example, granting Change under Advanced Sharing will not allow editing when the same user has only Read permission under Security.
To review the settings:
- Right-click the shared folder and select Properties.
- Open Sharing > Advanced Sharing > Permissions to inspect network-share permissions.
- Open the Security tab to inspect NTFS permissions.
Avoid adding Everyone with Full Control to both locations as a general fix. Correct the missing user or permission instead. Deny entries should be used cautiously because they can override permissions inherited through group membership.
Connect from the second Windows 11 computer
Direct path testing is more reliable than waiting for a computer to appear under Network in File Explorer.
Press Windows key + R, enter the UNC path, and select OK:
\\ComputerName\ShareNameYou can also enter that path in the File Explorer address bar. When name resolution fails, test the host’s local IPv4 address:
\\192.168.1.25\ShareNameFind the host address by running ipconfig and reading the IPv4 Address under the active network adapter. An IP path that works when the computer-name path fails points to discovery or name-resolution trouble, not folder permissions.
Windows may request credentials. Enter an account and password valid on the computer hosting the folder. For a local account, use this format when necessary:
ComputerName\UserNameFor a Microsoft-connected Windows account, the account email and Microsoft-account password may be required. Do not enter the Windows Hello PIN unless the credential prompt specifically supports it.
Map the folder as a drive
Map a frequently used share so it appears under This PC:
- Open File Explorer and select This PC.
- Select the three-dot menu, then Map network drive.
- Choose an unused drive letter.
- Enter
\\ComputerName\ShareName. - Select Reconnect at sign-in only when the host is normally available.
- Select Connect using different credentials when the remote account differs from the current Windows sign-in.
A red X after startup does not always mean the mapping is broken. Windows may display it before the host wakes or joins the network. Open the drive after both PCs are connected before recreating the mapping.
The other PC does not appear under Network
Test the direct UNC path first. When it works, the share and permissions are valid; only discovery needs attention.
On both PCs, confirm that the network profile is Private and that Network discovery is enabled. Then press Windows key + R, enter services.msc, and check these services:
- Function Discovery Provider Host
- Function Discovery Resource Publication
Start a service when it is stopped and set its startup behavior appropriately for a PC that should advertise shares. Restart both computers after changing discovery services.
Do not enable SMB 1.0 to connect two current Windows 11 computers. SMB1 is an obsolete protocol and is not required for normal Windows 11 file sharing. Older NAS devices that demand it should be updated, reconfigured, isolated, or replaced rather than weakening every PC on the network.
Windows says the network path was not found
Error 53, error 0x80070035, or “The network path was not found” usually means Windows cannot reach the host or resolve the path.
Check these details in order:
- Verify the computer name and share name.
- Confirm that the host is awake and connected.
- Test the IP-based UNC path.
- Confirm that both devices are on the same local network rather than a guest network.
- Check whether a VPN has redirected local traffic.
- Allow File and Printer Sharing through Windows Defender Firewall for Private networks.
The System Error 53 troubleshooting guide covers name resolution, SMB connectivity, services, and command-line checks for a path that cannot be reached.
Do not disable the firewall completely. A successful test with the firewall off only proves that a rule or network profile needs correction; it is not a safe permanent configuration.
Access is denied or Windows keeps requesting credentials
An Access denied message means the host was reached but the supplied identity lacks effective permission. Recheck both the Sharing permissions and the Security tab for that user.
Repeated credential prompts often come from an outdated entry saved in Credential Manager:
- Open Control Panel > Credential Manager.
- Select Windows Credentials.
- Remove only the saved credential matching the host computer.
- Connect again and enter the correct host account and password.
Windows can also reject guest access when password-protected sharing is off. Instead of weakening guest-access policies, create a named local user on the host and grant that account only the folder permissions it requires.
Error 0x80004005 is less specific and can involve credentials, SMB configuration, permissions, or system issues. Use the Windows error 0x80004005 guide when the path is reachable but Windows returns that exact code.
Stop sharing the folder
Right-click the folder, select Show more options > Give access to > Remove access. You can also open Properties > Sharing > Advanced Sharing and clear Share this folder.
Removing the share stops network access through that share name. It does not delete the local folder or its files. Review the Security tab separately when you also want to remove permissions previously granted to a user.
A good shared-folder setup should survive a restart, require known credentials, expose only the intended folder, and give each user no more access than necessary. Direct UNC testing, followed by permission and credential checks, resolves most failures without disabling security controls or enabling obsolete Windows features.
