Why is my network messed up after update to windows 11 24H2

Anonymous
2024-10-28T10:48:56+00:00

Hello, after updating win 11 23H2 to 24H2 several "computers" are disappeared under the "network"pane in windows explorer.

The day before updating, all computers were attached to my network and visible in windows file explorer.

After update to 24H2 they were gone!

I did see that after updating the option for media streaming were turned off.

I put The media streaming option on again, but that was not the solution.

Windows for home | Windows 11 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

91 answers

Sort by: Newest
  1. Anonymous
    2025-01-03T00:07:49+00:00

    Meanwhile I could solve the issue with my Synology NAS and Win11 24H2.

    I had to chenge in group policies under Computer Configuration- Windows Settings- Local Policies- Security Options the setting

    Network security: Restrict NTLM outgoing  :allow all

    After that, access to shared folder was as before in 23H2, I even didn't need to allow the insecure guest login to see my NAS in the network neighbourhood.

    This worked for 3 PCs AMD and Intel installing 24H2.

    Surpisingly it worked without changing anything on a fourth PC which I upgraded on Friday to 24H2, maybe ther was a recent update of 24H2 which solved the issue?

    Thanks. I updated to 24H2 again and tried your suggestion but it made no difference, i.e. my 2 Conceptronic CH3HNAS drives did not appear in Windows file Explorer. Note that I have never had problem setting up a mapped network drive for either of my NAS drives under 24H2... it's just that they're not visible when using Windows Explorer. I've reverted back to Windows 11 Pro 23H2 again in order to easily brows the folders and files on my NAS drives via the Windows file explorer.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-12-31T18:54:28+00:00

    Network security: Restrict NTLM outgoing  :allow all

    Worked perfectly. Thank you very much sir.

    Cheers!

    Added: Well it worked for one boot up. I just mapped the Nas drive I wanted access to and left it at that. Will leave it to Synology or Microsoft to see if something can be done for network places with the Nas.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-12-22T12:50:26+00:00

    Buenas tardes

    Sigo sin poder ver mi red a 22-12-2024.

    He seguido todos los correos y no le he visto solución.

    ¿Para cuando una actualización para resolver estos problemas por parte de Microsoft?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-12-22T04:38:50+00:00

    I'm find the same ~ however if I specify the "Domain Name" of the local network it accepts it. eg \name.local

    Doesn't work on FIle Explorer stepping into the Network and discovered device

    Most of us are home users and not in a domain. Althou .local can always be used as FQDN. I gave my NAS a domain-name, althou I'm not in a domain.
    File explorer does respond to the format NASname.domainname and opens the directory list after I had to give in my credentials of the nas.
    You can also just use \NASname without the .domainname extension. Works too.

    I enabled NETBIOS over TCP/IP in the network connector (as also suggest in an answer another one gave on this thread).
    After you made a connection to the nas, you can add it to the list of "quick access" (less typing the name over-and-over again).

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-12-22T00:31:18+00:00

    I'm find the same ~ however if I specify the "Domain Name" of the local network it accepts it. eg \name.local

    Doesn't work on FIle Explorer stepping into the Network and discovered device

    Was this answer helpful?

    0 comments No comments