Windows 10 network share experiencing significant delays once more...
Windows 10 network share experiencing significant delays once more...
Hello! Since I moved to Windows 10 Enterprise as a server OS in late 2017, I’m still facing issues with network shares. They sometimes function, other times they don’t. From what I understand, they only work partially. I can see my server on the network, log in, and view all my files, but opening folders is slow—often taking over 20 seconds—and read speeds are around 2 MB/s. The download speeds remain within the expected range of 100–110 MB/s. This problem first appeared about six months ago after a forced update on my PC. After updating the server, everything worked again. Now it’s happening again. I’ve updated the server myself and even changed my client OS to Linux, but the issue persists across different Windows versions, including my laptop. I’ve tried standard fixes like restarting, disabling/re-enabling shares, and registry adjustments, but nothing resolves it. I’m considering switching to Xpenology or Ubuntu because I want a solution that doesn’t require constant troubleshooting. Anyone have suggestions?
I faced issues with slow directory listings in XP. A registry entry resolved the issue at first. After many years we moved to Windows 10 again, but the problem returned. I searched for a fix but found nothing useful. Then I considered applying that XP workaround just to test. To my surprise, it improved performance—especially for copying files. Directory listing is now significantly faster. Try using the attached registry file and restart all affected computers to see if it helps. speedup_v1.reg
We should gather more details first. Possible issues include various factors. Let's begin with the fundamentals: network card type, RAM capacity, usage patterns, disk space, RAID configuration, storage utilization, server location, switch specifications, and uptime (note these may require restarts). CPU load, presence of Active Directory, file server role, whether the AD server is onsite or remote, if it's overloaded, VM status, network port sharing with other servers, and any changes to network adapter settings. Identifying bottlenecks is essential.
Network Card features an Intel I350-T4 RAM with 16 GB ECC. It operates under less than 2 Gigs of usage during runtime. The disk is a 6 TB Seagate Ironwolf, and the server is located on-site within a LAN environment. No Raid configuration is in use. Approximately 700 GB of space is occupied, though issues persist across all drives, including the SSD I rely on for Apache and MySQL. The switch is a Netgear ProSafe; a restart was attempted but didn’t resolve the problem. CPU utilization sits around 13%, with only 2% attributed to file transfers as shown in Task Manager. The server hosts Plex and Apache, and even though website content resides on this disk, I disabled all services to rule out anomalies. The hardware is physical, situated in my basement, so no shared components exist (except the switch). Previous adjustments to network settings were made but reverted to defaults as none provided a solution.
Your small registry file might not be providing enough information.
Open device manager, locate your network adapter, then select properties. Proceed to the advanced section. Turn off the listed configurations. IPv4 Checksum Offload Large Receive Offload Large Send Offload TCP Checksum Offload UDP Checksum Offload This adjustment increases CPU workload as the processor manages parts of the network stack.