I found this script (save as a batch file) somewhere. It worked for one clients home network after the update to 24H2. I haven't used it since and I claim NO responsiblity, ownership, or authorship of it's contents: Spoiler: 24H2 Network Fix - Use at your own risk Code: @echo off :: Check for Administrator privileges net session >nul 2>&1 if %errorLevel% neq 0 ( echo This script requires Administrator privileges. Please right-click and select "Run as administrator." pause exit /b ) :: Enable Insecure Guest Logins echo Enabling Insecure Guest Logins in the Registry... reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters" /v AllowInsecureGuestAuth /t REG_DWORD /d 1 /f :: Check if the registry modification was successful if %errorLevel% equ 0 ( echo Insecure Guest Logins enabled successfully. ) else ( echo Failed to modify the registry. pause exit /b ) :: Enable SMBv1 echo Enabling SMBv1... dism /online /enable-feature /featurename:SMB1Protocol -NoRestart :: Check if SMBv1 was enabled successfully if %errorLevel% equ 0 ( echo SMBv1 enabled successfully. ) else ( echo Failed to enable SMBv1. SMBv1 might already be enabled. ) :: Adjust Local Security Policy for Guest Access echo Configuring Local Security Policy for Guest Access... reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa" /v forceguest /t REG_DWORD /d 1 /f :: Disable SMB Signing Requirement on Client echo Disabling SMB Signing Requirement on the Client... reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters" /v RequireSecuritySignature /t REG_DWORD /d 0 /f :: Prompt to restart the computer echo Configuration complete. A restart is required for changes to take effect. pause shutdown /r /t 5
Did you do Windows Updates on Windows 11 24H2?? I had no trouble connecting any network or anything.. SO.. best of luck. ATGPUD2003
btw, network computers browsers isn't reliable. access remote computer directly with "Run" dialog (keyboard Windows + R) then : \\remote-computer\shared-folder
It didn't work for me. Instead my network computers were no longer able to see the host computer as an additional issue. I had to restore the registry as the batch file did some registry changes to get it back to the way it was before. But with the same issue, problem not solved. To me this has to do with the computer category being absent from network window. Something is preventing it from appearing even if just the host computer is displayed. But not even the host computer appears. After examining the batch closely, it appears that it included some of the same ideas floating in the internet but put togather.
go into your network setting and make sure your network discovery is turn on....also go into windows tools click on services scroll down to .... Function Discovery Provider Host and click it to automatic Function Discovery Resource Publication and click to automatic SSDP Discovery and click it to automatic UPnP Device Host and click it to automatic see if that works for you.....also reset your router and refresh the routing table....see if that helps.
As for the Services hacks that you mentioned I had already configured those, and things still didn't workout. With regards to the router reset and refreshing the routing table, I have my main router already configured to handle all the network devices in my home network seamlessly and I didn't want to go to the trouble of re configuring everything from scratch again. What I did instead was to power off my main router and took out a 2nd router with factory setting and created a brand new network and made my computers connect to it which they all did successfully. All my computers could see each other, except for the computer that I upgraded to Windows 11 24H2 which didn't display any computers in the network window just like before. Problem not fixed. I'm seriously considering reverting to Windows 11 23H2 if don't find a solution to this anytime soon.
I have does same network issues for a while , what i have found out if i leave my computers on after 3-4 days the network refreshes and i can see my share computers again....i agree 24H2 does have issues with network sharing.
I had never had issues Network sharing on base Windows Server 2022, TrueNAS, Any hardware NAS box.. Never had trouble.. Soundly your driver my have issues?? ATGPUD2003
I was forced to upgrade to 24H2 two days ago. I lost all my network. 4 Computers, 2 Nas, 2 Printers, DLNA server all disappear. Also the computer itself did not show in Networks. After hours of 'fixing' settings, I did a roll-back to 23H2 and added a block on 24H2 with Gibson's InControl reg patcher. I had planned to do Rufus unsupported hardware upgrades to 24H2 on two of the computers. But, after dealing with this, I did 23H2 instead and added the 24H2 blocker. I can wait
it is not a connecting problem, it is network/sharing problem. All the devices in your Network folder disappear. Some of us actually have home networks.
That pretty odd because I tested Windows 11 (Pro 24H2 and all way up editions to IoT 24H2) and I see all my network no problems with Windows Server 2022 and rest my NAS on base 4 - TrueNAS 24.xx and 3 - ASUSTOR NAS and rest of PC ! Seem strange some of you had issues... ATGPUD2003
If you install SMB1 in win 11 you may need to run a cmd window and paste the following: sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi sc.exe config mrxsmb10 start= auto Also check Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters Should have a dword: SMB1 with a value of 1 (0 is disabled, 1 is enabled)
Even though I have SMB1 installed, I have no dword in that registry location called "SMB1" so could this be the problem? If so, how do I fix it?
SMB1 has many security vulnerabilities, including information disclosure and remote code execution. Hence it's disabled and no longer used in modern Windows. You would only enable it if you were sharing files to an old device, like an old android media player with SMB1 support...
MS has added to the feature SMB1 and automatic removal as SMB can pose a security threat, in Windows features check if "automatic Removal" is checked, uncheck it. Open regedit, navigate to the parameters key in LanmanServer, right click in a blank area on right side, select "new" slide out select "DWORD(32bit)", (don't use 64 bit regardless of windows architecture). The value is created waiting for you to rename it "SMB1", Press enter to commit the new value, then hit enter again to open and verify the value is set to "0", close by selecting ok. Close regedit and reboot. When Windows comes up go into the network, devices and pc's should start to populate. Check your firewall too. Could be blocking file and print services ports. After all that, if still cant see PC's try running sc commands from above.
You said to set the DWORD value to 0, but earlier you said this means disabled while the value 1 means enable. So which one is it? I'm a bit confused.