I can't access other computers on the network after the windows 11 24H2 update

so i had to do some work on my old Win 10 surface pro 5. i am plugged to the same way that my win 11 surface pro is, and on the win 10 i see everything including the NAS drive. but not on the Win 11. Surface Pro for business 10.

OUTSTANDING! This worked perfectly, and I understand what you did there. I am more in the hardware world, was pretty sure something was going on with the SMB area, but don't have the skills to come up with this solution. Many thanks!

that did not solve it for me. i am not even seeing my own surface pro. it appears and then is gone the next time.

Wow!!! Steve D, You have made my day...or more accurately my 2 weeks since this dreaded patch messed up my system'

You either work for Microsoft or are brilliant as that patch has wasted a lot of my last 2 weeks time trying every recommendation that's been given on here with no success,

   I had started plans to make a major move of equipment  as the o/p of security cameras goes to a win10Home laptop via wifi and hence  via lan cable to a win11pro  that is out of range of the cameras.

After a few drinks I will now start putting pc's back where they are convenient.

Be good if Microsoft can update/fix that patch as many others must b getting the problems we've had.

Thanks again Steve

I can see other computers on my network but I have no access. I've checked all of the network settings. This all happened right after the windows 11 24H2 completed. I updated all the computers on the network and still no access.

Thanks,

Steve D.

problem solved for the Windows 11 24H2 update.

to allow access to your folders, the following works (after I tried every other thing that doesn't)

go to Start, type Powershell, Right click on Windows Powershell, and Run as Administrator.

Enter these commands one at a time, and Enter.

Set-SmbClientConfiguration -EnableInsecureGuestLogons $true -Force

Set-SmbClientConfiguration -RequireSecuritySignature $false -Force

Set-SmbServerConfiguration -RequireSecuritySignature $false -Force

These worked on a brand new install, and after the update.