File Sharing Between Windows 10 and Windows 11 Not Working — How to Fix the Compatibility Issues

A Problem That Should Not Exist

Windows 10 and Windows 11 are both Microsoft operating systems. They run on the same hardware. They speak the same network protocols. And yet, file sharing between a Windows 10 and a Windows 11 machine on the same local network breaks far more often than it should.

This is not a user error. It is the result of Windows 11 changing several default settings that affect how SMB (Server Message Block) — the protocol underneath Windows file sharing — authenticates and negotiates connections.

This guide covers the most common causes of Windows 10 / Windows 11 sharing incompatibility and the steps to resolve each one.

The Most Likely Culprit: SMB Dialect Mismatch

Windows 11 disabled SMB 1.0 by default and requires SMB 2.0 or later. Windows 10 also has SMB 2.0 support, so this should not cause issues — except in older Windows 10 installations or when SMB settings have been manually changed.

Check which SMB versions are active on both machines:

Open PowerShell as administrator and run:

Get-SmbServerConfiguration | Select-Object EnableSMB1Protocol, EnableSMB2Protocol

Run this on both machines. Both should show EnableSMB2Protocol: True. If the Windows 10 machine shows SMB2 as False, run:

Set-SmbServerConfiguration -EnableSMB2Protocol $true -Confirm:$false

Do not re-enable SMB 1.0 to fix compatibility. It is a deprecated protocol with known security vulnerabilities, and no modern Windows version needs it.

Network Profile Mismatch

This is the single most overlooked cause. If the Windows 11 machine has its network classified as Public and the Windows 10 machine has it as Private (or vice versa), file sharing traffic will be blocked by one or both firewalls.

On Windows 11: Settings → Network and Internet → click your connection → Network profile type → set to Private

On Windows 10: Settings → Network and Internet → Status → Properties → set to Private

Both machines must be on Private. Check discovery settings after making this change.

Mismatched Workgroup Names

Windows 10 and Windows 11 both use a workgroup for legacy network browsing. By default this is WORKGROUP. If someone has changed the workgroup name on one machine without updating the other, they will be invisible to each other in the Network folder.

Check and align workgroup names:

On both machines: right-click This PC → Properties → Advanced system settings → Computer Name tab. The Workgroup field must be identical on both machines.

Authentication Failures: Credential Issues

When a Windows 11 machine connects to a Windows 10 share, or vice versa, Windows needs to authenticate the connection. When local accounts are used on one or both machines with different usernames, authentication silently fails and produces an unhelpful access denied error.

Fixes:

1. Create matching local accounts on both machines (same username and password). Windows will use these credentials automatically.

2. Alternatively, navigate to Control Panel → Credential Manager → Windows Credentials and manually add credentials for the target machine's hostname or IP address.

3. On the machine hosting the share: go to Advanced sharing settings and ensure Password protected sharing is set consistently with your authentication approach.

Windows Defender Firewall Blocking Cross-Version Traffic

Windows Firewall sometimes treats traffic from the other OS version as suspect, particularly if the machine it is coming from authenticates differently. The safest targeted fix:

1. Open Windows Defender Firewall with Advanced Security
2. In Inbound Rules, search for "File and Printer Sharing"
3. Enable all rules related to that group for Private networks
4. Do the same on the other machine

After enabling these rules, do a fresh restart of both machines before testing.

When None of the Above Works

In some configurations — particularly after aggressive Windows Updates — the above steps resolve the immediate issue but do not remain stable. Microsoft has acknowledged long-standing reliability issues with cross-version SMB authentication, particularly where local accounts are involved.

If your office runs a mix of Windows 10 and Windows 11, and maintaining consistent file access is important to your work, Oxolan is worth considering. It runs as a user-space application with its own transport layer, so it is completely unaffected by SMB dialect versions, workgroup names, or Windows authentication configurations. Windows 10 and Windows 11 machines participate equally and see each other immediately after installation.

Get Oxolan for Windows

Frequently Asked Questions

Is SMB 2 enabled on all versions of Windows 10? Yes, SMB 2.0 is present in all mainstream Windows 10 releases. The only cases where it may be disabled are heavily locked-down enterprise environments or machines where it was manually turned off.

My Windows 10 machine can access the Windows 11 share but not the other way around. Why? Asymmetric connectivity like this usually indicates a firewall rule on the Windows 10 machine is blocking incoming connections, while outgoing connections are permitted. Check inbound firewall rules on the Windows 10 machine.

Should I join both machines to a domain to fix this? Joining a domain does resolve most authentication issues, but requires a Windows Server acting as a domain controller. For small offices without a server, the steps in this guide are appropriate.

After all these fixes, files still transfer unreliably. What else could it be? Intermittent transfer failures, particularly on wireless connections, are often caused by network adapter power management. Disable power management on the adapter in Device Manager on both machines: Properties → Power Management → uncheck "Allow the computer to turn off this device to save power."