This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 99%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERC%3C/text%3E%3C/svg%3E)
The preview:
__[Networking (known issue)]__ Fixed: This update addresses an issue where you might not be able to connect to shared files and folders if you're using the Server Message Block (SMB) v1 protocol on NetBIOS over TCP/IP NetBIOS (NetBT). This can happen after installing update KB5065426.
After installing KB5065789, the same problem persisted. Are there any prerequisites be reinstalled before this preview?
The problem of sharing of local drives seems not a SMB v1 related. Windows 11 Home with no SMB v1 support could share local drives if KB5065789 were not installed.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(208, 2%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELV%3C/text%3E%3C/svg%3E)
Hi Ryan C,
Welcome to Microsoft Q&A forum. I'm happy to help.
The KB5065789 update releases with SMB v1 fix caused by KB5065426. If you are limited by SMB v1 as some of your devices do not support SMB v2/v3, then you need to install KB5065789 after KB5065426. Otherwise, Windows 11 supports SMB v2 and v3 that are newer, better optimization and more secure.
If you have any difficulties in sharing your files by SMB, please feel free to let me know.
KB5065426 is a security update that I would install but it caused local drives sharing problem amoung Windows. KB5065426 was then uninstalled and the problem disappeared. It seems to be the problem of SMB v1 from other discussions. KB5065789 is to address SMB v1 problem but could not fix the local drives sharing.
The local drives sharing keep on asking the credential of the share access which are proven without KB5065426 or KB5065789.
Hi Ryan C,
To make it clear, KB5065426 does not cause SMB sharing problem, it only enhances the SMB protocol security so some systems may be affected. In those systems, they can choose to follow the security enhancement or disable it to make sharing functional as before. In those cases, KB5065789 does not related due to it only fix the SMB v1 (and v1 only) problem. Windows uses SMB v2 and v3 from long time ago, so if your systems are able to install KB5065426, it's nothing to do with SMB v1 and KB5065789. Once again, if you have any problem with sharing, please feel free to post. I will investigate and provide you necessary support.
I am able to install KB5065426. After that, I am unable to share local drives amoung my Windows 11 Home PC's. The sharing works prior to KB5065426 installation.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 80%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELG%3C/text%3E%3C/svg%3E)
lauter Murxer
Hi Ryan C, Thank you for asking this question on Microsoft Q&A forum. I'm happy to help.
From Windows 11 24H2, as a security enhancement, you cannot access SMB shared that has been configured to not require a password.
Since then, if your shared PC has no password, and other PCs using Windows 11 from 24H2, you cannot access.
If this is your case, you have 2 choices: Set password for user on shared PC / or Enable Insecure Guest Auth on other PCs.
regedit into type box then click OK. A Registry Editor window will openHKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\ParametersAllowInsecureGuestAuth entry does not exist, add it as a DWORD (32-bit) ValueAllowInsecureGuestAuth to 1You may take a look at reference screenshot bellow.
If this is not your case, please don't worry. Give me more information about your Windows 11 PC, your other PCs and more detail about where you stuck on accessing shared files. I will investigate and give you further support.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi Lucus-V,
I am using user and password for the sharing of local drives amoug Windows 11 Home PC's. They are working without any problems.
The problem occurred with the preview KB5064081. The sharing is not granted and kept on asking the credential of the access. Disconnected and reconnected the local drives did not solve the problem. KB5064081 was then uninstalled.
KB5065426 has the same problem and was uninstalled.
KB5065789 did not solve the problem and was uninstalled.
Hi Lucus-V,
I did attempt to Enable Insecure Guest Auth. The system kept asking for the share access credential as KB5065789 was installed. The sharing of local drives were not established. Once KB5065789 was removed, all the local drives sharing are reconnected successfully.
Hi Ryan C,
Thank you for keeping me informed.
Please try this additional method on both of your PCs.
Set-SmbClientConfiguration -RequireSecuritySignature $false
Set-SmbServerConfiguration -RequireSecuritySignature $false
If above method does not solve your issue, may I ask that did you clone your PCs or did you clean install each of them?
I'm ready to cooperate till we solve the issue, so please keep me informed.
Hi Lucus-V,
I removed SMB credential and entered the powershell commands as mentioned above. However, the problem persisted.
When I remapped the shares (local drives), the error message below displayed after providing access credential.
I did not clone my PCs and they are newly purchased identical MSI PC's earlier this year. They came with Windows 11 Home OEM. I did setup both PC's with different Microsoft accounts and machine names. There is also an old PC running Windows 10 PRO retail.
The Windows 10 PRO is always be able to access all the shared drives from both of the Windows 11 Home PCs with the access credential regardless of KB5065426 is in place or not.
I did try to Enable Insecure Guest Auth on all Windows 11 PCs. They kept on asking the credential for the share access. Windows 10 PRO was able to access the shared drives as it always does.
Hi Ryan C,
Please open Command Prompt then enter this command: net use
Then paste in here the response or give me the screenshot.
Also, please make sure these services are running, you may change their Startup type to Automatic
This issue could be caused by various reasons, so please be patient. Thank you.
Hi Ryan C,
Your screenshot above about mapping error means that shared drive is already mapped, and in your situation, it may be mapped under another user on your system.
In case you have mapped user another user, login to that user to unmount first. Or if you have not, it could be cached. Please open Credential Manager and remove every credential related to the network share.
After that, open Command Prompt as Administrator and run this command: net use * /del
To make sure, reboot your computer then try to map again.
I hope that this time it would be successful. Please keep me informed.
Hi Lucus-V,
All my PCs have 3 users at most. Windows 11 Home PCs have a Microsoft account for Windows, adminstrator (default), and local account for sharing access. The mapping is on Microsoft account. The adminstrator and local account for sharing access have not been logged on as I can remember. Windows 10 Pro PC have a Microsoft account and adminstrator (default) currently. I logged on Windows 10 Pro PC with other Microsoft accounts but they were deleted. I have no idea on how to disconnect the sharing with them. Further, Windows 10 Pro PC works fine all the time no matter what happened on Windows 11 Home PCs. These network shares are not working since the recent Windows 11 updates. Today, Windows 11 Home PCs are updated to 25H2 and I am still stuck with the same problem.
I did remove the credential to the network shares on Windows 11 Home PCs, run net use * /del command, reboot them. I could not solve the issue.
Hi Ryan C,
Thank you for your information.
To better understand your circumstances, how many PCs do you have? And you only share from a Windows 11 Home PC, is that right?
I see that you share from Windows account, so what credentials did you enter to access shared from Windows 10 Pro PC? And do you also use the same credentials on another Windows 11 PC?
I'm using SMB shared between my PCs also, I feel that we can solve the problem. Please be patient. Thank you for your time.
Hi Lucus-V,
Thanks for the help.
I have 2 Windows 11 Home PCs with a bunch of external USB drives and internal hard drives. The third PCs is running Windows 10 Pro on SSD. Before I have the 2 new Windows 11 Home PCs, my Windows 10 Pro PC were sharing the same set of local drives with the retired Windows 10 Home PC with no password protection during the era of Windows 10.
After the 2 Windows 11 Home PCs come into play, I have created a local account "share" on each PCs as enforeced by Windows 11. The sharing works in good order before the recent Windows 11 security updates. Then, the sharing is working partially from the Windows 10 Pro PC to access network shares on the other 2 PCs.
Each PC have the same local "share" account and credential to easy the management of share accesses. Microsoft accounts are to logon Windows and Outlook. I find difficulty to use them other than that. One of Windows 11 PCs and the Windows 10 Pro PC use the same Microsoft account to logon. The Windows 10 Pro PC will retire probably a year later for other use.
I know very little about SMB as a Windows user....
Hi Ryan C,
Thank you for very detailed explanation.
The reason I ask you about "what credentials did you enter to access shared from Windows 10 Pro PC" because I assume that Windows 11 may tie to use domain user instead of local user if you just simple type "share" for username part of credentials.
I have 2 more things you may try this time.
Ryan-PC2\share\\IP\share — example: \\192.168.1.10\Moviesshare or Ryan-PC2\shareI hope this method can solve your issue. Please keep me informed.
Hi Ryan C,
Thank you for keeping me informed.
Your case is very interesting, I get excited. Please do me a favor, we may have to do sharing almost from scratch.
share user and all unnecessary users from all your PCsI know these steps is annoying and bothering you, I'm very sorry for any inconvenience. I just want to narrow down the issue and try to find the root cause.
I hope that you don't mind and willing to do so. Please keep me in touch with the result. For the best analysis, you may provide some screenshots.
Thank you for your time.
Hi Lucus-V,
I am relunctant to do step 3 as suggested and would like to take a break at the moment. I believe I am not alone to have this issuse. The network share is proven before the recent updates. 25H2 could not resolve the problem as well. I am seeking solution from Microsoft technical support and will keep you posted.
Thank you for the help.
Ryan
Hi Ryan C,
It's good you are back.
You are now very close to complete those steps. If you have inconvenience, you can forget about disabling PIN. Just simple set a login password right in Sign-in options then continue to next step.
Hi Lucus-V,
My Microsoft accounts are passwordless. In step 6, Windows 11 did not granted the network share access whether I entered the PIN or one-time password code from Authenticator. It seems Windows 11 does not reject my credential instead display the message below.
I did attempt the user name of different formats:
username before @ (as sugguested)
the first five characters of username
the complete Microsoft account name
They all came back with the same error message.
Hi Ryan C,
Since you login to your PC using Microsoft Account passwordless, the local share account may be necessary as you did before.
May I ask does the error message "The network folder specified is currently mapped" appeared after you remove share user?
If you don't know what user is using that map, please check with this.
Disclaimer: Generally, modifying registry subkeys or work group is intended for advanced users, administrators, and IT Professionals. It can help fix some problems, however, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For further protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click How to back up and restore the registry in Windows - Microsoft Support to view the article.
Another workaround is using alternative server name. If you often use IP address of shared PC as server name, you may try to use its hostname. With Windows, it's the PC name (like Ryan-Windows11 or Ryan-Laptop or a random name given by Windows).
There's one more thing you should check if you have permission error message is permission of your files. Please make sure that share account can access your files on its Properties > Security.
In case issue still persists, please follow these steps.
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation Please notice that you should always try to access shared location by Explorer to test the result before you map it as drive.
I hope that those steps above will help you solve the problem. If you ever face any difficulty, remember that I'm here and happy to help. Just keep me in touch.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi Lucus-V,
Further, I see online discussion regarding SID and do find my two identical Windows 11 PCs (newly purchased this year) have the identical SID. I will see if I were able to make them unique in order to solve this problem. Microsoft should have the problem resolved instead of letting users to find their solution. Before the recent preview and/or security updates, the network shares are working in good order. We are unable to remove those problematic updates as we are at 25H2.
My last resort is moving all local drives for sharing to Windows 10 Pro PC. The network shares work fine between Windows 10 Pro and Windows 11 Home at the moment.
Hi Ryan C,
The issue is caused by identical SIDs—that’s why I asked if you cloned your PC.
You may choose to change your SID by using 3rd party tool. However please notice that Microsoft provides no assurances and/or warranties, implied or otherwise, and is not responsible for the information you receive from the third-party linked sites or any support related to technology.
Changing the SID is risky and should be done with great care. If it fails, you may need to reinstall Windows.
My suggestion is to back up your data and perform a clean install with a full format of your Windows drive. This method is safer and more reliable.
I hope this helps resolve your issue. Please keep me informed.
Thank you for your time.
Hi Lucus-V,
I did not clone my PCs and they are as they are from the manufacturer. I am sorry that I have no knowledge of what the manufacturer did.
If I am going to perform a clean install as you suggested, I assume a new SID will be generated and that will resolve the network sharing issues.
Hi Ryan C,
You don’t need to be sorry — it’s on me. Regarding the SID, I shouldn’t have asked a simple question. Instead, I should have guided you to check the SID on both PCs. That was my responsibility.
Since your PCs came directly from the manufacturer, it's unusual that they have the same SID. Anyway, let’s set that aside and focus on resolving your issue.
When performing a clean install, please delete all partitions and let Windows handle the rest — this will generate a new SID. Don’t forget to back up your data beforehand.
I’ll be waiting for good news from you.
Thank you for your time.