Problem in network Windows 11 24h2

I think the solution might be to disconnect all peripherals, try the upgrade, and then reconnect them one at a time. Let's see.

I found that I cannot access my network, including shared network drives and NAS, when I use IEEE b/n/ac/ax on 5G. I can use IEEE b/n/ac with no problems at all. Every once in a while I cannot use the network card at all, until I reset the PC. I'm using a Realtek 8852CE WiFi 6E PCI-E NIC, which is internal to my laptop (HP Envy).

All this started with version 24H2. Before 24H2 everything network wise was fine.

Thank you very much for the answer. We are currently trying to contact the software provider but we have not yet received a response. I believe that they are still experiencing the origin of the problem, just like I am.

The bad thing about this is that, without a temporary or definitive solution, if the computers in the bank branches were to be updated to 24H2, we would be in serious trouble.

We have already blocked this update, but in my SCCM console I can see that there are users applying this update manually.

And I am trying to validate which protocols, registry keys, configurations, etc. changed from 23H2 to 24H2. I even compared a complete registry dump between both versions, but I still haven't found the exact problem.

Some people blame the fact that in this 24H2 version the use of NT LAN Manager (NTLM) will be obsolete/disabled, but I am not really sure about this (I have already touched the configurations regarding the subject and at the moment nothing seems to work).

As an additional detail and something related, we use Crowdstrike in the organization, and in other articles they mention that said EDR suffers from Microsoft app blocks due to incompatibility with 24H2, but nothing confirmed.

I think you have two action items. First, block 24H2 until your banking application vendor updates their software. Second, get your CISO or CTO to go beat on the software vendor of the banking application. The banking application vendor must update their software. The problem has to do with how the application itself is making calls to the network stack. It is likely that the banking application has dependencies on deprecated software components as well. I would run Tenable One or Nessus full vulnerability scan against those endpoints.

Does anyone here know if there are any known issues with this version (24H2) regarding any network issues (apart from DHCP issues), any protocol changes, any protocol removals, or any partial modifications?

I have a serious problem in my organization. The problem is that when upgrading from Windows 23H2 to 24H2 the banking suite stops working due to network protocol blockages, the software tries to connect but is directly rejected, I used external tools to validate which processes are related to the software when used but I still do not have a clear indication of the cause of the error, the message of failure in the use of map32.ocx, I have already validated the registry keys, port blocking, firewall rules, re-registered each related .ocx and validated the .dll and compatibility of elements but I do not see anything clear, with the same files when rolling back to version 23H2 everything returns to normal (including the last system build that came out on November 12, but in 24H2 no build works).

My current Windows build is 24H2 26100.2314 (Nov 12) but I have been testing since the September version that is downloaded with the Windows ISO.