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(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I manage a office network of computers with about 10 systems. This network of computers is connected via a ‘peer-to-peer’ configuration, without using a DOMAIN or Windows Server.
I had upgraded one of the computers on the network from Windows 11 Pro 23H2 to Windows 11 Pro 24H2 (latest version that was just released by Microsoft). After doing so, this computer was not able to connect to other previously mapped computers on the network. However, the system was still capable of printing to network printers.
This upgraded computer has 2 users/profiles. One is an Administrator and the other is a standard user.
After upgrading from 23H2 to 24H2 the STANDARD USER'S mapped network devices lost connectivity, even though the system still indicated the mapped network drives were still available in Windows Explorer. When selecting those drives within Explorer a loss of network connectivity error displayed (I can't remember the error code). On the displayed pop-up error message I attempted to perform a network diagnostic but it was unable to resolve the issue. I still had internet connectivity and still had the capability to print to network printers. I disconnected the mapped drives and attempted to remap but again received the network error message indicating the same error pop-up.
However, I logged into the ADMINISTRATOR PROFILE and it did not experience any issues. All mapped drives worked as they should.
I changed the standard user profile to be an Admin. This did not resolve the issue. The previous STANDARD USER profile (now an Admin) failed to be able to map other systems/drives.
I then created another user account/profile with Administrator Privs. This new Admin profile would not allow me to map any network drives.
Note: the system I had upgraded to from 23H2 to 24H2 was the only system upgraded on the peer-to-peer network. All of the other systems were still 23H2.
One other thing I noted. While troubleshooting to check for connectivity I was able to PING the upgraded 24H2 system from a 23H2 system. However I was not able to PING any other systems on the network from the 24H2 system.
Thus to reenable connectivity I rolled the 24H2 system back to 23H2 and connectivity restored.
***moved from Windows / Windows 11 / Accessibility***
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. To protect privacy, user profiles for migrated questions are anonymized.
Same issue with our computers. We also have a small office environment using peer to peer networking. Any computer that updated to 24H2 lost all connectivity to mapped drives or other network resources.
Rolling back to 23H2 resolved the issue.
I communicated with MS support late last night (2am) and they provided some steps to attempt. One being - changing some SMB settings as well as ensuring the computers being mapped from/to have 24H2 installed. I haven’t tried it yet. If you haven’t tried any of this and you attempt it… please let us know your results.
That won't be an option for us without replacing some of the machines. Most of the machines are still running Win10 and are not upgradable to Win11.
Had exactly the same problem so blocked further updates. Has Microsoft fixed this yet? Is it safe to update to 24H2 yet?
Not sure what fixed this issue but a couple days later the problem was resolved. I assume Microsoft pushed a fix but I couldn't tie it to another KB update.
