Forum Discussion
Windows 11 File Sharing on Home Network With Win 10 , & and Older Devices
After some months with Windows 11 Pro I am at my wits end with it. Nothing but trouble and problems.
The main issue I have is that unlike all my other PCs the Windows 11 Pro box refused to display the other devices on the home network so that I can map to the drives and folders that are shared. All except my old Server that seems to pop up, but that is NOT good enough when I want to pass files direct between machines as I've always done.
I am tired of trying to fathom the acronym ridden spoutings about the KB5065426 Windows update that was issued in September 2025 which stills seems to be the primary reason given for the rubbish performance of Windows 11 file sharing. Is this still really the case are MS so bad that they can't be bothered to fix the issue in a way that is comprehendible to the average user?
Already their Midi devices update that was dumped on people in March wrought havoc with many InMusic devices, what with this and the mess of the start menu and trying to find things, noting the latest update screwed that even further, is making me think that Windows 11 should be binned and revert to Windows 10 as the new stuff is too much hassle.
Any ideas that can do better than the many incomprehendible posts about SMB and more as hack to fudge the system would be gratefully received.
6 Replies
- QueenOfKeysReemaBrass Contributor
Hi Stratcat51,
Thank you so much for mentioning me — I’m genuinely happy to help and I appreciate your kind words.
From what you described, it does sound like the issue is related to SMB changes in Windows 11, but there are a few additional areas worth checking to avoid unnecessary hassle:
✔️ 1. Enable SMB1 (only if you have older devices)
Windows 11 disables SMB1 by default.
You can enable it temporarily from:
Control Panel → Programs & Features → Turn Windows features on/off → SMB 1.0/CIFS.
✔️ 2. Ensure SMB Direct & SMB Automatic Removal are enabled
These sometimes get disabled after updates.
✔️ 3. Check “Password Protected Sharing”
On some networks, Windows 11 forces credential-based access.
Go to:
Advanced sharing settings → All networks → Turn off password-protected sharing.
✔️ 4. Verify Function Discovery services
Make sure these two are running on all machines:
•
Function Discovery Provider Host
•
Function Discovery Resource Publication
✔️ 5. Try mapping the share manually
Sometimes the UI fails but mapping works:
\\PCNAME\SharedFolder
I completely understand the frustration — networking between mixed Windows versions can be messy, but I’m more than happy to help you get it working smoothly.
If you want, I can walk you step-by-step based on your exact setup.
Always glad to assist!
Just to add one more thing:
If you ever feel overwhelmed with the technical steps, I’d be more than happy to guide you through them in a simple, clear way. You’re not alone in this — I’m here to help.
- VamskerIron Contributor
The short answer to your question is: Yes, you are correct. The September 2025 update (KB5065426) is very likely the primary cause of your network file sharing nightmare. It's not you, and it's not your hardware.
- Stratcat51Copper Contributor
Thanks for the likely confirmation Vamsker I have been hunting for a fix and presume that MS couldn't give a heck about the hassle this update and others have caused.
I am deeply regretting buying a new PC with Windows 11 its just too much hassle that its incompatible with things.
I am wishing I could be sure where is safe to buy a Windows 10 licence then I could bin this garbage win 11 stuff.
- QueenOfKeysReemaBrass Contributor
Hello, I’m Reema. I’d be happy to help you fix the Windows 11 network discovery issue.
If the basic steps don’t solve it, I can guide you through advanced SMB and network repair methods.
- Stratcat51Copper Contributor
Hello Reema,
Sadly those fixes didn't solve the issue. In all my hunting for solutions and reading I had already read about SMB and as part of those efforts I had switched on SMB1.0 and verified that I had the settings as suggested. Truth be told, that solution was only recommended as a 'Temporary solution' as it opens other risks that the KB update allegedly fixed whilst causing havoc for others, mostly I am guessing home users with mixed hardware networks.
I had already found I could Map a drive by using \\devname-driveorfolder\ in file explorer but that wasn't a thing I wanted to do over the lost flexibility of navigating the network.
I think my solution will be to try and source a Windows 10 Pro licence and just bin the Windows 11 stuff as its just more bother than it is worth. MS did once say that Win 10 was going to be the last Windows and I think for me it will have been because I will never come back for more rubbish like Windows 11 has been,
Thank you for your kind suggestions.
- Stratcat51Copper Contributor
Thank you for the offer of ideas. Is it just an SMB thing or is it more than that? I have looked at user SID details on machines using command line who is and they aren't duplicated and its not like the pc ssd was cloned so that id's were replicated across machines on my home network. Forgive me but I am getting too old for dealing with hassles like this.
I don't think MS or any of these big corps really think of the impact and hassle. It was an old addage that got quoted so many times that '80% is good enough' in work, quality or what ever it drove me nuts then when some said it and it still does, it the harbinger of shoddy everything.
If you have ideas I'll gladly take a look and be appreciative of your aid.