Why Windows File Sharing Has Gotten Worse Over Time

It Actually Did Work Better

If you have been using Windows since the XP or Windows 7 era, you are not imagining it. Network file sharing genuinely worked more reliably then than it does on Windows 11 for most small office configurations. Understanding why requires a quick look at the history of Windows networking.

The Windows XP Era: Simple and Mostly Reliable

Windows XP used NetBIOS over TCP/IP for network discovery and SMB version 1 for file sharing. The combination was simple: machines announced their presence via NetBIOS broadcasts, the Network Neighbourhood folder showed every machine on the subnet, and SMB1 handled file transfer.

SMB1 had no encryption, no signing requirements, and minimal authentication complexity. It was easy to configure and easy to maintain because there was almost nothing to configure. Connecting to a shared folder was a matter of typing the UNC path or browsing the Network Neighbourhood.

Why it was reliable: The protocols were simple, discovery was handled by simple broadcasts, and there were no competing services to go out of sync.

Windows 7: Still Reliable, But More Complex

Windows 7 introduced HomeGroup (a simplified peer-to-peer sharing UI), promoted SMB 2.0 (faster, more efficient, still relatively straightforward), and began phasing out reliance on NetBIOS broadcasts for discovery, replacing them with WS-Discovery (Web Services for Devices) and SSDP (Simple Service Discovery Protocol).

For most users, Windows 7 sharing still worked. The HomeGroup abstraction made it accessible to non-technical users, and SMB 2.0's improvements were largely transparent.

The Windows 10 Turning Point

Windows 10 introduced changes that began fragmenting the reliability of file sharing for non-expert users:

SMB1 was turned off by default (version 1803 and later). This was necessary — SMB1 had severe security vulnerabilities (EternalBlue, used in the WannaCry ransomware) — but it broke compatibility with older devices and NAS units that only spoke SMB1.

Network profile classification became stricter. Sharing only functions on "Private" networks. If Windows classifies a network as "Public" — which it does by default for new network connections — sharing is disabled. Users connecting to a new router or after a network card replacement often found this silently broke.

HomeGroup was deprecated (removed in Windows 10 version 1803). The simplified sharing experience was gone; the more complex underlying SMB configuration was now exposed directly.

WS-Discovery became the primary discovery mechanism, but the four services it depends on (Function Discovery Resource Publication, SSDP Discovery, UPnP Device Host, DNS Client) are individually configured by startup type, and their dependencies are not always maintained correctly across updates.

Windows 11: The Reliability Low Point

Windows 11 made things worse in specific ways:

Windows Updates reset service startup types. Cumulative updates occasionally set discovery-related services back to Manual startup type, silently breaking network visibility for computers that were perfectly discoverable before the update.

SMB signing became required by default (introduced in Windows 11 22621.2361 onwards). If connecting to a system that does not support SMB signing, connections fail silently or with obscure error messages. This broke connections to older NAS devices, printers, and other SMB servers that had worked fine previously.

The Network folder became unreliable as a primary UI. Computers appear, disappear, and return at intervals that have no apparent relationship to whether they are actually reachable. Many machines that are perfectly accessible by UNC path or IP address simply do not appear in the Network folder at all.

Driver signing and Secure Boot interactions occasionally break network adapter advanced settings, disabling jumbo frames or link speed optimisations that were previously configured.

Why Microsoft Made These Changes

The security improvements were genuine and necessary. SMB1 was a catastrophic security vulnerability. SMB signing prevents man-in-the-middle attacks. Network profile separation limits exposure on untrusted networks.

The problem is that security improvements that protect enterprise environments with IT departments impose friction costs on small offices without them. An IT administrator can script and GPO-enforce all the correct settings. A 5-person design studio cannot.

Windows has simultaneously become more secure and harder to use for simple local networking — a trade-off that makes sense at enterprise scale and makes less sense for small offices.

How Mac Handles the Same Problem

macOS, for comparison, uses Bonjour (mDNS) for local discovery and AFP/SMB for file transfer. Discovery via Bonjour is significantly more reliable than Windows' WS-Discovery/SSDP stack because:

• Bonjour is a single, always-running service (not four separate services)
• macOS network updates do not routinely reset Bonjour configuration
• macOS treats the local network discovery service as core infrastructure

Mac-to-Mac file sharing under the Finder's Network sidebar works reliably in a way that equivalent Windows discovery simply does not match. When a Mac and Windows machine are on the same network, the Mac typically finds the Windows machine; Windows finding the Mac is less consistent.

This is not a Mac vs Windows verdict — it is a documentation of different architectural choices and their practical outcomes for small office users.

What This Means for Small Offices

The practical consequence: if you rely on Windows' built-in Network folder and mapped drives for file sharing, you should expect to troubleshoot it after major Windows updates. This is not a user error. It is an architectural issue with how Windows manages the dependencies of its discovery and sharing systems.

The practical responses:

1. Accept it and maintain a troubleshooting checklist — restart the four relevant services, ensure Private network profile, check firewall rules
2. Use direct UNC paths instead of the Network folder — less prone to discovery failures since you are bypassing discovery entirely
3. Use application-level file sharing tools — such as Oxolan (Windows) or LocalSend (cross-platform including Mac) — that manage their own discovery independently of Windows' SSDP stack

Get Oxolan for Windows

Frequently Asked Questions

Is Microsoft aware of these issues? Yes. Microsoft has acknowledged specific issues in Windows Update release notes when major regressions occur. The ongoing fragility is a structural issue, not a series of bugs with clear fixes.

Will Windows 12 or future versions fix this? There is no public commitment from Microsoft to redesign the discovery infrastructure for small-office reliability. Security improvements will continue, and some will continue to affect compatibility with non-enterprise configurations.

Should I enable SMB1 to get sharing working again? SMB1 has serious, unpatched security vulnerabilities. Do not enable it on any network connected to the internet. If you need backward compatibility with a specific device, investigate whether that device has a firmware update that adds SMB2 support.

Does switching to Windows 11 Pro fix these issues? No. The discovery reliability issues affect Pro and Home similarly. Pro adds Group Policy management which can enforce consistent settings — but only if someone configures it.