just updated windows 11 KB5065426 network shares no longer connect

Chris Johnson 535 Reputation points
2025-09-10T16:04:18.42+00:00

Version 10.0.26100 Build 26100

just updated windows 11 KB5065426 network shares no longer connect. the server is older but access is required and has been working for years.

net use

New connections will be remembered.

Status Local Remote Network

Unavailable N: \MSR\radio Microsoft Windows Network

Windows for home | Windows 11 | Internet and connectivity

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

35 answers

Sort by: Newest
Most helpful Newest Oldest
  1. David Gerner 0 Reputation points
    2025-10-10T05:52:29.6133333+00:00

    I had one of 8 Workstations not break when multiple updates were done on 10/02/2025. Rolling back/ unistalling KB5065426 on the client machines. Pause Win update for 4 weeks, then restarted computer.

    After restarting Goto Search & Enter Credential Manager

    Delete any shares in Credential Manager under Windows

    Checked to ensure on PRIVATE Not Public Network

    next:

    1.Open Run command by Pressing windows + R and type regedit and hit enter to open the registry editor.

    2.Navigate to the following path.

    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows

    3.Expand the Windows Registry Key and search for LanmanWorkstation registry key,

    If you are not able to find the registry key, then you need to create it.

    4.Right Click on the Windows Registry Key and Choose New > Key, Name the Key as LanmanWorkstation.

    Now Click on the LanmanWorkstation Registry key and from your right-hand side

    right click and choose New > DWORD 32 bit Value and name it as AllowInsecureGuestAuth.

    Double click on the AllowInsecureGuestAuth DWORD and set the value to 1 and give OK.

    ran following in Admin Privilege CMD Prompt:

    sfc/scannow

    dism /online /cleanup-image /scanhealth

    dism /online /cleanup-image /checkhealth

    dism /online /cleanup-image /restorehealth

    disable/ uncheck SMBv1 in Windows Features

    Enable/ check SMB direct in Windows Features

    Restart

    Next go into Group Policy (Pro Version Only) gpedit.msc

    Computer Configuration, Windows Settings, Security Settings, Local Policies, Security Options.

    Set both of these Below to "Disabled"

    Double click on Microsoft Network Client: Digitally sign communications (always)

    Double click on Microsoft Network Client: Digitally sign communications (if server agrees)

    Click on OK.

    Then find:

    Computer Configuration, Administrative Templates, Network, Lanman Workstation

    Double click on "Enable Insecure Guest Logons"

    Set this to "Enabled"

    Click on OK.

    Reboot

    Once rebooted & Signed in Map your shared Drive

    Of Note all computers Desktop are Windows 11 Pro, the same model Dell & specs, the big issue I saw was in reliability manager that the updates that failed at least one time then succeeded had the failure of mapped drives.

    Was this answer helpful?

    2 people found this answer helpful.
  2. Gerry 0 Reputation points
    2025-10-04T17:28:10.2133333+00:00

    Fix your problem

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Machina 10 Reputation points
    2025-10-02T22:49:18.07+00:00

    I lost access to the shares on my WD NAS after the KB5065426 update. I followed the usual advice to uninstall the update, but I failed to block its reinstallation, and now Win 11 will not allow me to uninstall it. So, here is what I did to regain access to my NAS shares, while leaving the KB5065426 update installed. (Leaving it installed is presumably better for security anyway.)

    Step 1: Insure that the NAS utilizes SMB2 or SMB3, and not SMB1. Do this by checking the settings on the NAS or its documentation.

    Step 2: Run powershell as an administrator and enter the command

    Get -SMBClientConfiguration

    Look at the results to ensure that "EnableInsecureGuestLogons" is set to "$true" and that "RequireSecuritySignature" is set to "$false". If needed, change these values, by entering the command

     Set -SMBClientConfiguration -EnableInsecureGuestLogons $true

    and the command

    Set -SMBClientConfiguration -RequireSecuritySignature $false

    Restart the machine if any settings were changed by powershell.

    Step 3: If you don't know the exact name by which your NAS is known to your machine, find it by looking under "Network" in Windows Explorer. Then, in Explorer right click on "This PC" to choose "Add a network location". Then click on "Choose a custom network location" to bring up a dialog where you can enter the exact name and location of the share you want to access, in the form

    \exact name of your NAS\exact name of the share

    Then, click "browse". That should bring up a system response in which it acknowledges that it has found the share. Assign a drive letter to it. You should now have stable access to the share, using the assigned drive letter.

    At least this worked for me on my personal machine. On my corporate laptop it did not work, since my organization does not allow me to choose a custom network location outside of the corporate network, and my NAS is not in the corporate network. So, for access to my NAS on my corporate machine, I have to set up cloud access to the NAS and get access to the share by browsing from the cloud.

    Yes, this is all annoying and time-consuming. I'm grateful to others on this thread for their help. Probably my strategy will not work for everyone, since there are lots of variables in play here. MS should not have released an update that would cause so much trouble with networking.

    Was this answer helpful?

    3 people found this answer helpful.
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  5. Chris Johnson 535 Reputation points
    2025-10-02T00:50:50.5333333+00:00

    GREAT NEWS! The old linux share now shows up again on my windows 11 system with a new update 2025-09 Cumulative Update Preview for Windows 11 Version 24H2 for x64-based Systems (KB5065789) (26100.6725)

    On the win 11 client I had to remove the shared drive, add it again, and supply credentials for the server.

    net use n: /d

    net use n: \msr\radio /user:username

    may have to re-do that to make it persistent. We'll see. Adding /persistent:yes would do the trick

    Update on Windows 10 worked even better:

    September 25, 2025—KB5066198 (OS Build 19045.6396) Preview

    NOTE!!! did not have to re-attach the shared drive. I think these two cases were different as far as guest vs. account access.

    This tidbit from the Windows 10 update history note:

    "[SMBv1 protocol connectivity (known issue)] Fixed: 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 KB5065429."

    "An issue"

    sure would like to know what it was. This resolves the original issue I reported on this comment.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments