Same issue here. All suggested solutions are useless. If any TWO computers have kb5065426, they are unable to connect to one another. Interestingly, If only ONE computer has kb5065426, and another computer does NOT, then network file sharing works between them. Hopefully Microsoft will fix this.

I'm on Microsoft Windows (Version 10.0.26100.1) on Samsung Galaxy laptop and today I had updates waiting and all I did was Update and Restart and ever since that my machine won't restart and ends up with blue screen of death of always with Code: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Whatever I try, all I can get to is "Cannot connect to network. We will retry after 30 mins".

I've trying to do all sorts of things with recovery, without any luck thus far. Attempting to remove the feature update is also not working since the update hasn't completely installed. Sigh what a pathetic situation to be. I don't want to reset the PC just yet because that will loose everything. When I check for system restore option, there is no prior known good configuration as well (I don't know how!!).

Using command prompt, when I run mic qfe list brief I can't seem to even find this, but I can only find the below,

1. Update - KB5063689 & KB5064485 - NT - AUTHORITY\SYSTEM 8/3/2025

How do I bring my machine back to life.. This is pathetic Microsoft.. Bricking everybody's machines.. This is very critical as I've an exam in the morning tomorrow... wow Microsoft.. You screwed me up!!!

i to have this problem of the 6 machines i have networked 4 got the update. 2 do not they can still access the other shares the same way as always for all the updated machines.

To RM this is a separate issue best resolved in a new thread. Look to see if there is a bios update from Samsung. If an update wasn't fully installed, it's not installed. Boot into safe mode and see if you can update the bios/video card driver as that's pointing to a driver mismatch.

Don't reset.

Susan, I got fed up and did a reset of my PC and now there is no network adapter and WiFi within Settings -> Bluetooth & Devices -> no WiFi. There is no network connectivity. Network & internet just has a VPN now, so nowhere to connect to the internet

That's why I say -- don't reset. It's not the answer. Go into device manager - does it see your wifi hardware?

The best thing everyone can do at this time while Microsoft gets their telemetry info is to uninstall the update and then go into windows update section and pause updates. But do not reset your PC. That's not the solution.

Facing this exact issue on two system at home, one was cloned from the SSD of the other and I just changed the name and Windows license etc and has been working fine for years until now...all file/printer sharing and RDP is dead, just keeps saying incorrect user/pass. All the normal stuff is verified, private network, sharing on, etc etc and certain it is due to the update plus same SID as follows:

I verified both machines do have the same SID.

I tried uninstalling KB5065426 from both systems but that did not resolve.

Next I removed KB5064081 from both systems and reboot and now SMB/RDP is working normally again.

In my process of troubleshooting I found that the Remote Desktop Classic Windows app actually still worked also but, the regular RDP would not, so the RDP Classic app must authenticate differently? I'm not sure if you can even get or install this still since the newer "Remote Desktop" app is depreciated and maybe not working at all.

I am considering trying SIDCHG on one of them as a long term solution since I assume Microsoft will not make any attempt to revert this dispite what will likely be millions of impacted systems. Please us know if you tries SIDCHG and any problems or side effects or other issues are encountered.

I don't understand what the appropriate settings for file sharing now should be.

I have windows 11 pro pc and a windows 11 home laptop and the user/password to access a share (from either one to other) results in "The specified network password is not correct!"

Both machines have the same user name and the same password. All shares are shared with user/password.

Both machines have smbv1 client support enabled to access an old printer.

Is this update just bugged? Or what settings for smb am I supposed to have to share a folder between two updated windows 11 pcs?

I spent 2 days and 3 hours with tech support and I cannot connect to my other computer (windows 10) to transfer data and files. So what is the point of having this new Windows 11 computer if I can't use my data on it??? Connecting to the other computers on a private network has always been a freeking NIGHTMARE! FIX IT MICROSOFT!!! This windows 11 computer is totally useless to me without being able to transfer data and files. FIX IT!

I'm with you Mattias. I've given up. I'm now using sftp (which works????) for my workflow. Should those shares start working again, that would be nice. Somebody at Microsoft said go ahead and ship this, people using old samba servers be damned. Susan, pause updates? That doesn't seem viable to me.

that is very likely a separate problem. you will likely have to either enable guest access or use workgroup-spcific user ids.

Does anyone know if Microsoft is working on a patch to correct this problem?

Are these mapped shares? Help me understand. As I can get to a drive on my Win 10 from my Win11 just fine.

Are these Windows 11 with PIN set up and thus no password actually stored for the user in question?

What if you set up a new user with a password (thus enabling NTLM) and do it on both devices and share with those credentials?

I tried setting up new users with distinct PWs and problem persists. We always had users set up with PWs not Pins

What if you reshare with everyone full access. Do you have any other security software? I still don’t get why I can access shares.

Susan, everyone in my world has Full Access, and problem still exists

Have you run the command to determine what smb version is running? As with 11 they should be able to do v2 no prob

Susan, what is the command to determine what smb version is running ?

I am also having this problem with a network which has previously worked perfectly.

I reset my laptop but STILL have the issue.

Actually I ran it (Well was trying to get a help screen) and when the customer rebooted the computer the next day it acted like a fresh computer, asked for Microsoft account and password. Once he got in there were none of his files/ Went to One Drive and only about half of his stuff was there (because it was full).

I tell them about every 3 months "Backup".

So be careful I'm guessing this tool can hose a lot of things.

And someone said it's not the USER SID but the Computer SID.

I'm thinking about seeing how things work with a Linux Stores instead of Windows. And maybe later see if we can move off windows, almost everything they do is in the cloud and as Microsoft keeps pushing to subscription model ($$$ Monthly)..

Not sure why but I went to optionalfeatures and ran as administrator unchecked all smb 1.0/CIFS file sharing support and all my machines will now take a log in password. It worked for all 4 computers with the update and I still can access them with the 2 that dont have the patch without the log in.

Well, 5 machines (Beelink EQR6 Ryzen 9, Windows 11 Pro) connected to a share on a 6th locally. They were all setup with a common share folder and worked until this update. All had the issue but 1. Uninstalled KB5065426 and they all worked. Before the next day the update was re-installed. Removed it again, tried wushowhide utility but it never showed that update so I was forced to pause updates. Everything seemed fine.

Today I needed to add a share on the 'Server'. I added a local user and created the share. I cannot connect to that share but the other share is still functioning.

"Server" has the share with full rights to the new user. Remote system I "Map network drive", specify the \Server\share, use "Connect using different credentials" and used the user and password from the newly created user and "Remember my credentials".

"The network folder specified is currently mapped using a different user name and password."

All machines have SMB 1.0 disabled.

Any one else experience after multiple uninstalls of KB5065426 that you are getting "uninstalled failed" (error 0x800F0825)? Anyone find a work around for this?

Same here, could not access the CF card in my trusty old Canon MX 895 All-In-One where all my scanned documents are saved. Came from one day to the other and I tried lots of things, including reinstalling the driver, nothing helped. My wife on her PC had still access, I didn't.
After lots auf Google searches I landed here and uninstalled KB5065426, rebooted and now everything is working correctly again.
Microsoft, this is very bad!!! You cannot install such BS on Windows PCs killing functionalities and not even mentioning that there might be issues and how to fix them.

RULE THIS ONE OUT OR FIX IT!

There is an issue going around with cloned systems (image from the same base image)
Breaking SMB, print sharing, and RDP.

Dustin - Susan covers that elsewhere in this thread. Something about a disk ID that needs to be changed after cloning.

Open the Windows search bar and type “powershell”

Right-click on PowerShell and select “Run as administrator”

Execute the following commands:

PowerShell

Copy and paste

Set-SmbClientConfiguration -RequireSecuritySignature $false

click enter and say Y yes to it

Set-SmbClientConfiguration -EnableInsecureGuestLogons $true

click enter and say Y yes to it

This worked for me and a coworker, no need to uninstall updates or pause them.

This is absolute insanity, i setup a brand-new virtual machine with latest Windows 11 pro, i could not for 3 hours find a way to connect despite credential, asking copilot, and changing bunch of registries. All the time the problem was this insanely broken update, one uninstall was all the fix. God help me I am so behind schedule just because of one small useless update!

This did not work for me

After trying most of these suggestions, I found a work-around for my situation. I run a PC with a single local admin account and lost access to my NAS following the update. Working on my wife's win 10 laptop to do some prep work for the unwanted upgrade to win 11, I found that I couldn't see the network from my old win 10 local admin account on her laptop. But, switching to her local user account I could see the network. So, back in my win 11 PC as an admin I created a standard user account and tried again but this time used the "use a different account" option when the connect to network dialog appeared - the network was now visible and the NAS disks could be mapped and still work after a reboot back into my admin account. This makes no sense to me but see if it works for you!

Yes, there's another local networking feature that was "improved". Certain privs used to work across shares on the same cilent machine and don't now. That was not "fixed" by Microsoft. This shows up in a variety of ways. In my case with multiple shares across different PCs in the house, it means that my "persistent" shares, even with saved credentials, always require a password to be entered on first connect after boot. You're fine unless or until you somehow do these multiple shares.

We are having this same issue since the first time 24H2 installed earlier this year. Our shares are on devices running Windows CE. So they've killed access to their own operating system. Thanks Microsoft!

Will there ever be a fix? Everyone has a solution that requires a cost. Is Microsoft going to eat that cost for everyone they've effected?

We can access the Windows CE Remote Management Tool through a browser. When adding the share as a network location, it goes through all of the steps and even adds it to the list in explorer but refuses to actually open directory. Doesn't matter if I use the ip address or the share name.

Anyone been able to get around this? The only suggestion I've found that doesn't cost too much was to create a vm with Windows 10. The issue is that even some version of Windows 10 are having the issue also. Would have to make sure it's an older version and make sure it doesn't have internet access so it can't update itself.

Thanks,

Jessica

Hi Jessica -

This thread has identified at least 3 different problems, all related to that update. One has to do with systems cloned (I think using SSDs) where the SSID needs to be changed on the cloned drive. The sharing problem, as far as I can tell has two parts. One has to do with the update and older SMB servers that use an outdated cipher. Support was removed without warning and broke a lot of small networks. In addition, they seem to have plugged another "security" hole having to do with shares to multiple targets with more than one "admin" account (and/or/maybe) guest access in use. My original problem with the shares (SMBv1 deprecation) is better with the later updates (see my answer elsewhere on the thread). But I also have the second problem, and even with "persistent" shares to my old reliable server I have to type a password every time my windows 11 system restarts. The windows 10 system worked fine (after they reverted the change) but I've since upgraded it to windows 11, it (magically) keeps that same share persistent! No idea why. What a mess.

Hi Chris,

I have no problem entering credentials. It accepts them every time. I'm not using cloned drives either. It seems to only be an issue with the 24H2 update, that I have found. I can connect to those shares with no issue on a Windows 10 computer. For the people that need to access the information on those devices I have given them each a Windows 10 laptop, for now and told them to not let it update. I just wish Microsoft would realize what they are doing when they do things like this. It is a complete mess.

I have done everything getting my network share to work. I spent 9 Hrs. using Microsoft Tech Base Used all the commands as well asking AI for Support. Still not working, personally "AI" was more stupid getting it to work. Everything was fine in 24H2. Microsoft Software is a joke and going downhill into the trash can and laying off good programmers and replacing them with "AI". I am guessing Microsoft has stopped buying Bannas for the Monkeys but that's a subject for another time. As of today, I stop using Microsoft OS and Just Moved to Linux, and everything is working. The End of Microsoft is coming soon because the only Money Microsoft is making is from Cloud base services

If your sharing problem is based on the update mentioned in my summary, there has been a subsequent update that "fixes" it. It now should be as easy as catching up the updates. If that isn't working, you have a different problem. There was also a windows 10 update with the problem and a later update to restore the SMBv1 support. The specific updates are in my report on this thread. I can't test windows 10 further down the line any longer because mine are all upgraded to 11. They absolutely knew what they were doing, because they put out a justification for the issue I reported.

I never got that update - 2025-09 Cumulative Update Preview for Windows 11 Version 24H2 for x64-based Systems (KB5065789) (26100.6725). It's not even available in my updates or optional updates. Right now I have 25H2 available and KB5066131 and KB5066835 available. Do you know if I have to specifically install that update or is it combined in one of these?

Thanks,

Jessica

I just let it install the latest cumulative updates for October but no difference.

I am hesitant to install the 25H2 update.

Thanks,

Jessica

Well, unless you're a Microsoft installer MVP, I'd never recommend getting lost in the partial update jungle. Although now with w10's situation that's an open question. Did you enroll in the extended security updates yet? I'm betting you'll have to keep up sooner than later, and recommend sooner. gulp.

Have you installed the 25H2 update? I'm not familiar with enrolling in anything Microsoft related for updates. Just whatever comes in on their own.
But if that update didn't fix the SMB1 connection, what am I missing?

for Windows 10, right? No, I updated my two w10 systems to Windows 11. But before I did I got an update that "fixed" the SMBv1 share problem for me. Details are in my post on this thread.

No, for Windows 11. I've read through everything on here. Nothing fixes my issue with SMB1.

Thanks,

Jessica

My apologies, I looked back at your original question. Windows 11 clients trying to access shares created on Windows CE. I'm not sure I can be of help. If Windows 11 is up to date, you should have SMBv1 support back. Do you have access to the command prompt and the "net" command? My guess is that you are having permission problems now. I am too, but I can create the shares. I just can't get the password to stick (username yes, and computername too - with the correction update on w11).

Given the errors you see it is able to talk to the CE "server" share, so I think its some kind of credentials issue (as mine is). How are the shares setup on the client side? Is it guest access, user-based permissions or domain/workgroup based permissions? I think there could be a fix using guest-based, via some settings (two of them) described on this thread. Maybe. If you see the share in explorer, you're pretty close. Perhaps opening up full access on the sharing side to "Everyone"? Just guesses

The 25H2 update, CHANGED MY DEFAULT BROWSER TO MS! IT CHANGED MY VIEWING OF PDFS WITH ADOBE PDF READER IN WINDOWS EXPLORER. IT KEEPS ASKING ME TO HAVE THE ADMINISTRATOR TO CHANGE OR DO STUFF. CONTROL CONTROL CONTROL!! I STILL CAN'T SHARE ON A PRIVATE NETWORK WITH MY WIN 10 COMPUTERS! WINDOWS 11 IS A FREEKING NIGHTMARE!

You can get another year of Window's 10 security updates for FREE. First Log In to your Microsoft Account. Go to Settings, Update & Security, and click on Extended Security Updates. Follow the instructions. You may have to log in again, sometimes it asks when going through the process.

It is user based permissions on the CE side. The login is bladewerx\admin. Our domain is different and they won't connect to the domain.

What is your LAN Manager authentication level set for?

Local Computer Policy - Computer Configuration - Windows Settings - Security Settings - Local Policies - Security Options - Network Security: LAN Manager Authentication Level

Thanks,

Jessica

I just updated a different computer to 25H2 to see if anything was fixed and the answer is No.

We really need a solution. This has been going on for months. This began way before September. At first we thought it was something with new switches and firewall that we installed but can still get to the shares on Windows 10 that hasn't been updated and Windows 11 prior to 24H2.

Did you try the commands to enable guest access?

Made an account just to thank Héctor J. Jiménez González. Solved my problem right away. Shame on M$ for this ridiculousness!

Could you please provide any updates regarding this issue? This is a fundamental out-of-the-box functionality provided by Microsoft, and it is concerning that a suggested KB patch by Microsoft would potentially disrupt their primary functionality. We have invested considerable time and effort in troubleshooting this problem, and it has already caused us significant frustration.

Yes. I've tried everything. We've been having this issue since spring.

Jessica, I can't use the group policy editor on windows 11 home. its not there and MS doesn't allow it to be installed :(

I do know they also changed something to prevent "floating admin credentials on shares". Since your share target appears to be an administrator user, I'm (totally) guessing that might be it. Can you enable guest logins on CE? and/or try a different account? In my case the targe share is on an ancient linux server, and its just a regular user account. it works, but I can't get the credentials to persist. Here's what the win 11 client credentials look like for me:

Internet or network address: foobar

User name: foobar\jimmy

Password: <lots of dots>

Persistence: Enterprise

Anybody know what Enterprise means? All I did was command line net use with /persistent:yes

Anyway, it works but I have to enter the password every time I reboot.

I have the solution here https://oriongeek.com/sabias-que-la-actualizacion-24h2-de-windows-11-bloquea-tu-nas-o-servidor-por-seguridad-asi-lo-solucionas/

I can't get them to not remember the credentials. LOL Everytime I try to change something I have to jump through hoops to get it to forget. I end up deleting all credentials and messing other things up. I have added another user name but am now fighting to get it to let me login under that name. LOL I will update as soon as I can get it to use the new username.

Had to connect to a different monitor to be able to test it. No difference. Same error.

Uninstalling KB5065426 appears to resolve the issue with the computers that are unable to RDP or map a network drive. However, by NO means should uninstalling a patch be the "answer", should it? I'm not sure what other "things" the patch included but uninstalling the entire KB could potentially be uninstall good "things". For now, since we can't uninstall just the parts that break RDP and network mapping, we'll uninstall the entire KB.

According to MS, KB5065426 is suppose to address an SMBv1 issue, but in my case, we ran cmdlet get-smbconnections and the results of column "dialect" show "3.1.1" which according to documentation, shows the SMB version. Also, there's no mention in the patch release notes that RDP is going to be impacted. Why did this KB, break RDP?

Also we attempted to apply patch KB5065789 since it was newer and there was mention that some issues were fixed in the patch. We tested/applied KB5065789 and the same issues specifically with RDP and network mapping were still there. So we had to uninstall both KB5065789 and KB5065426 to resolve the issue.

Microsoft team, is there any way to NOT include KB5065426 in any cumulative patch bundles? This will really REALLY help. Thank you for your help and attention to this matter.

Same problem for me even after I use Windows Credentials Manager to remove the creds for the share and re-enter them on next connection attempt, still get password error.

Bottom Line: Microsoft has disabled the ability to use a network operating system sold as such-for millions of people if not more- without an option to say no or roll back. The only recourse for local (affordable) file sharing at this time is Linux or the cloud. The USA allowing unlimited monopolies -is about to be forced 100% into the cloud because many if not all Linux OSes are now receiving funding from cloud companies. With Red Hat down, there are only a couple options left and then the USA is strategically weaker than the East in every way, manufacturing, technological innovation (the cloud-Such as OneDrive-actively deletes files with any code it does not understand unless you are on a business account- and even then , try doing crypto research and saving anything-even if it is encrypted- in the cloud, - the Cloud as it is will never be fully secure and will stifle all innovation outside established corporate academic partnerships. Not being able to fall back to on prem shares and infra to continue limited business not only means we cannot research in house easily or anything, it also means operations cease when the disaster strikes- from enemies external, internal, or natural, there will be no way to continue operations. If we go to war with a smart country, our clouds will become unusable. Business will stop. With our already paltry manufacturing capabilities, we will be vulnerable like never before. Microsoft is being controlled by foreign actors- this has to end. Nadella and all Indian influence has to go. We need an American with American interest leading our primary tech companies. India has openly chose Russia and China- and why not? We overplayed our hand.

I'm still able to use my Windows 11 so your statement is over-reacting. There are two things at play here. 1. SMBv1 and it's hardening. 2. The duplicate SID issue. Have you checked if your SIDs are identical in these impacted systems?

https://support.microsoft.com/en-us/topic/kerberos-and-ntlm-authentication-failures-due-to-duplicate-sids-76f7394d-c460-4882-9ed1-d27e0960f949 Let me see if I can get some folks to release the workaround more widely.

This is offensive- I have to stop taking calls for this because it bothers me that Microsoft- an Indian IT company- disabled network functions in an OS sold as a Network Operating system. I just cannot deal with MS anymore. They are becoming more and more like Quickbooks and Adobe every day. Soon you will need to let out of work Indians remotely access your PC and charge 3k to remove "malware" blocking you network connections - it is already happening-every time MS releases an update. So many scammers just came up- you have to wonder- did the Indian gov ask Satya Nadella to do this as retaliation for the 100k H1B visa fee that happened at around the same time? I wonder if we can directly correlate this to a rise in small business targeted scams in the last month?

This is a tech forum, not a political one. The issue is that vendors have not properly set up computers and we in the community have to deal with the side effects. Someone who set up your pc imaged it improperly. Be angry at the proper entity.

Too bad that's not the case for everyone. My computers are not imaged. We have the issue straight out of the box if the computer comes with Windows 11 24H2. So my anger is directed at Microsoft, no one else. Our only solution is to build a computer with an older version of 10 or 11 and isolate it from the internet so it can't update itself and can't be compromised then let users access that to be able to access the shared drives on the devices that can no longer be connected to. None of the solutions on here worked for us.

Again there are two issues. Check and make sure your systems are on private. Ensure that you have set up matching usernames and passwords in each system. I have new 24H2 systems and am not seeing this. So how exactly are you setting up your peer to peer network?

Susan that is patently false. It is a technical issue that happened at the same exact time political tensions turned hot. This is beyond fixable without shelling out $$$. Also, if I imaged thousands of machines using Microsoft guidance and Microsoft changes course years later and breaks something that worked for 10 years and would work for another 10- old hardware is way better than new for longevity and usability-why would Microsoft break it? If it is out of support leave it alone or disable it on new sold hardware. I literally got around this by pulling a rabbit out of my hat and installing a Windows 7 machine to host my file share in an isolated network but then gave up and now I am setting up my .venv on one Mint Desktop and three Ubuntu servers with the intention of running windows in isolated VMs going forward-in Linux. I am not trying to be political- but it is very dangerous to take so many small mom and pops down when the real world economy is imploding. This update should be rolled back completely by Microsoft and removed. I am obviously not the only one who had a problem and it is impossible not to be aware Trump put a 100k per person H1B fee in place right as this is happening-this is a devastating update for small business not in the cloud.

Timothy drop the politics. It doesn't belong here and is absolutely not what caused this. If the issue is duplicate SIDs you got stuck with a lame vendor who did something they never should have in the first place. This is a direct result of Microsoft trying to protect systems from ransomware. Did you use the tool as an alternative. https://www.stratesave.com/html/sidchg.html

And Susan- I appreciate you are trying to help -the only help is a patch undoing this. Also- I still have multiple PCs still running latest DEV channel updates and still no fix (I only switched to dev out of desperation). Do you really think i want to be up all night rebuilding an already working Redis Server I was about to demo runnig something I have worked on 3 years to build? Do You think I am EAGER to be rebuilding my complicated VScode Pycuda .venvs with dozens of packages now I have to retest all over again before THURSDAY? Does this sound like I am interested in anything political at this moment other than a solution? No I want Satya Nadella to order this fixed. I do not want old people ill equipped to pay me getting their accounts emptied trying to get it fixed with "overseas helpers". Is that political? Have you no empathy? I have 20+ years of Microsoft usage and held MS certs for the first 10 of those. I literally am forced to rebuild because I have no money to drop on this and the cloud will absolutely never again be an alternative for me. I cannot show my products to my customer with gaping holes when we literally agreed to immediate testing. I have been directly damaged from this- massively -and if I cannot fix it without opening myself to complete cyber takeover to anyone with access to a TV on my network, imagine what normies are going through? Also- my PC were all using this MS account- all licenses are linked to this account- and we used OneDrive for BS and fake stuff and used local for real files. Now only OneDrive works. Hmmm. I cannot share using the same account on two PCs right now- even if I completely turn off Window Defender firewall and Disable the firewall service via PS. How is that even a POSSIBILITY? I was sharing Password protected ENCRYPTED FOLDERS! They are encrypted with Bitlocker! I tried unencrypting them, re encrypting them, setting permissions to all- what is really happening? The only thing working happens to be OneDrive Shares!

Dev channel won't fix this. Did you check to see if you have the duplicate sid problem or the guest shares issue? If the PC is running, the folders are not encrypted. Bitlocker only protects you when the system is turned off. If the machine is running, your TPM chip has provided the key to unlock the drive. We have workarounds for both, I just need to know what is biting you.

I thought I was losing my mind. I had P2P networking running among 4 computers in an office, then all of a sudden it all broke, asking me for credentials. I scoured the web and did a myriad of networking things, adding special Admin users, enabling SMB, yaddy yadda. Nothing worked.

But I did get it all working again very simply. 1) Rip out all the MS P2P setups, and 2) Install Google Drive. Everyone is now properly networked with the benefit of cloud backup.

I wonder if anyone there has heard of "Regression Testing" - like BEFORE you unleash, I mean, release stuff to the public? I wasted 2 full days on this trying to find out what I did wrong, when all it was turned out to be a Microsoft update installed overnight when we were all asleep.

comment deleted by user

WHY HASN'T MICROSOFT FIXED THIS PROBLEM!!! WE NEED TO SHARE OUR FILES ON OUR OWN PRIVATE NETWORKS BETWEEN 10 AND 11!!! WE NEED AN UPDATE TO FIX THIS!!!!

There won't be an update to fix this. There are two issues. Follow the commands to enable guest access -- or if you have duplicate SIDs there is a workaround posted by Karen W. In which camp are you?

Well I'm in neither camp so am really hoping for an update. I can see the shares and enter credentials but then get an error. This started when our computers upgraded to 24H2.

So what's the solution for me???

Thanks,

Jessica

Are you positive you don't have duplicate SIDs? Were these computers purchased at the same time? Alternatively did you try the commands that were posted

Do this:

https://www.yourwindowsguide.com/2025/01/mapped-drives-24h2.html

1. Open the  Windows search bar and type “powershell”
2. Right-click on PowerShell and select “Run as administrator”
3. Execute the following commands:

PowerShellCopy

Set-SmbClientConfiguration -RequireSecuritySignature

I've done all of the suggestions in this post and others. I purchased and built all of the computers myself. It doesn't matter if it is a laptop or desktop, it doesn't work. I can go to a similar computer that has 23H2 or even just Windows 10 and it works fine, no errors. But anything that's on Windows 11 24H2 will not let me get to the shares.

I would go in and reshare/remap the location. I've had to do this in the past with a misbehaving share. Also double check and make sure that your internet profile is set to private. What's the OS of the machine that has the shared folders? What's the OS of the machines you are trying to access the shares from? Have you installed updates through October on all machines?

The devices that we used to be able to connect to are running Windows CE. There are no updates for them. I've run all updates on the computer that I am using to try to connect. It is on Windows 11 25H2 (26200.7019). No matter whether I "Add a network location" or "Map a network drive" I get the same error. "The specified sever cannot perform the operation." I've been searching for a solution since May 2025. Nothing works. I've even tried adding another user name and password so that I am not using admin. No luck.

Try this Using Control Panel

Open Control Panel and navigate to Programs and Features.

Click Turn Windows features on or off.

Scroll down and check the box for SMB 1.0/CIFS File Sharing Support.

Click OK and restart your system.

In the future is there a reason you are using an out of date operating system? Is there any plans to go to something newer? You are running into the problem I call "kids on the playground are not the same age and are fighting with each other". You have a really old operating system trying to talk with a brand new operating system.

The SMB checks in Windows features was the first thing we had to turn on when we first got these devices back in 2021. I am able to connect to the CE remote management tool using the IP address of the device. Just not the shared folders.

These are devices that we purchase from Ludlum. There is no update for them and they have no intentions of moving to another operating system. We have no control over that. This all worked until the 24H2 update hit. Like I said before, all systems that have a version prior to 24H2 work. All Windows 10 computers left in the office work. (There are only a few left though). Our only other solution has been to provide the users that need access a Windows 10 laptop and told them not to run updates. They can at least get the files they need that way but we would love to get it working again the way it was. Starting to think it's a lost cause.

This is the document we received with the devices.

https://ludlums.com/images/product_manuals/M334A.pdf

Page 43 is what we used to be able to do.

Thanks,

Jessica

Is SMBv1 enabled on the Windows 11 machines?

Yes it is

and registry key of

• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
• Create a DWORD named AllowInsecureGuestAuth and set its value to 1.

You can access it via IP address you said? What if you set up permanent mapped drives via IP address? Does that work?

Are these still devices that are supported by the vendor?

Yes, the registry setting is there and set to 1. Yes, I can access the Windows CE Remote Management Tool via the IP address.

I've set up permanent mapped drives. I get the same error.

We have 12 of these devices. Three of them we just bought last month. So, yes, they still support them but the instructions they supply, in the link I posted yesterday, doesn't work and they don't have a guaranteed solution to make it work. For the cost they quoted I could set up a VM with Windows 10 and run with it. Just wish Microsoft would stop breaking things.

Thanks,

Jessica

Got an idea. Are you willing to let me open a support case on your behalf? This vendor sounds like it's still building these devices. So it's still an actively developed product. email me at sb - at- askwoody.com and I can set up a support case on your behalf so we can get to the bottom of this. There's a setting somewhere that we are missing.

Does a support case cost anything?

I will be opening it up on your behalf. Normally they do ($499) but this is a bug created by a security update and thus it will be waived.

I emailed you, Susan. Thank you!!

Jessica - I read your manual, and I think the data transfer solution won't be solved via the share as described any longer. But I also think you could fairly easily use an alternative method to transfer the device data another way. The changes from Microsoft in part are intended to prevent a security issue caused precisely by the method that was chosen. From my research, that won't be reverted by them for that reason. They are choosing to address these issues over keeping compatibility with their older insecure methodology. It sounds like Susan is trying to help, although some of the suggestions here do not address the security problem.

just now I can't solve

Try with .\user name

THIS WORKED FOR ME

Hi Chris,

I'm Sumit, here to help with your query on the Microsoft Q&A forums.

Apologies for any inconvenience you are experiencing. I am happy to help you today.

Did you buy any chance try these commands given below? I believe with older Network shares, running these is necessary.

https://www.yourwindowsguide.com/2025/01/mapped-drives-24h2.html

1. Open the  Windows search bar and type “powershell”
2. Right-click on PowerShell and select “Run as administrator”
3. Execute the following commands:

once I executed the commands, the network drive connected as designed

I have the same problem but I'm running Windows 11 25H2.

This works.
Connect Win 11 computer to Win 10 on a private network.

1. Manually Access the PC by IP Address or Name

The most direct way to check connectivity is to bypass the automatic discovery process.

Find the target PC's IP address or name: On the PC you can't see, open Command Prompt and type ipconfig to find its IP address (e.g., 192.168.1.10) or type hostname to get its name.

Access it directly: On your PC, open File Explorer and type the IP address or name with double backslashes in the address bar:

\192.168.1.10

  \\W10ComputerName
  
  If this works, you have a connection, and the problem is purely with network discovery display issues, not file sharing itself. You can map a network drive for permanent access. 
  

Looks like Microsoft is just evolving it's efforts to get users to save to one drive instead of their own systems. Late stage capitalism strikes again.

I figured out this problem, at least for my situation. This is a little complicated to explain, but I will try here. There is more than one way to login to your PC. One way is a PIN, the other way is a password. (Look in Control Panel User Accounts). I have two PCs on my home network. I ran this Windows Update on PC#1. I made no changes to PC#2. Prior to this Update, on PC#1 in File Explorer I had mapped drives to shares on PC#2 and setup "Quick Access" folders pointing to shares/folders on PC#2. I had scripts setup to run nightly to copy everything from PC#1 to PC#2. After the Windows 11 Update KB5065426, I could no longer connect to the shares/drives/folders on PC#2. What happened was... prior to the Update, when I setup the connection to the shares/drives on PC#2 for the first time, I entered the PIN (because I had PC#2 setup to login with PIN). Forever after that, you don't have to enter the PC#2 PIN again on PC#1 to connect to the PC#2 shares. Apparently, the Windows Update changed the login requirements (from PC#1 to PC#2) to the actual password to PC#2. The PIN that I had previously entered (a long time ago) wasn't sufficient anymore. Now, after the Windows Update, it requires the actual password, not just the PIN. So after I re-mapped the drives/shares using the actual password (not the PIN) for PC#2, then all the shares started working.

it is very dufficult for me to go or upload files espeshially when appliying for jobs that dont use docx as another way to upload you could have made a new thing to replace it but now we have to deal with this bull

I'm glad to see this post resulted in solutions for many folks. I have no idea why, but for the second time I've heard from Microsoft that this "question thread is under moderation review for possibly violating community guidelines." As before, that's not even close to correct. Just a warning in case anyone wants to capture this information.

I just finished a new build, and had to apply these commands to get my MyCloud Duo to reconnect to Win11 Pro 25H2:

https://www.yourwindowsguide.com/2025/01/mapped-drives-24h2.html

1. Open the  Windows search bar and type “powershell”
2. Right-click on PowerShell and select “Run as administrator”
3. Execute the following commands:

PowerShell

Set-SmbClientConfiguration -RequireSecuritySignature $false
Set-SmbClientConfiguration -EnableInsecureGuestLogons $true