No ESP8266/ESP32 communication with Win 11 on Lenovo IdeaPad-5

I have noticed that on Windows 11 there are problems with transmission to the ESP8266 and ESP32.
It looks like when I connect a new board, everything is OK, but after several connections, transmission becomes impossible and I can't do anything with this device. In the Device Manager, the USB port is visible, but neither the Arduino IDE nor ESP Flash Download Tools can establish a connection with the board.
When I connect this board to an old laptop with Win 10, it turns out that everything is OK and I can program it without any problems.
I wasn't sure whether the problem is on the hardware side (Lenovo IdeaPad-5) or on the OS side.
So I installed Windows 10, plugged in the non-working ESP8266 and after automatically installing the driver it turns out I can use it without any problem.
Then I put a new Win 11 on this laptop and after plugging in the non-working board it automatically installed the driver, but communication with this board is no longer established.
In both attempts I did not install the Arduino IDE, but used ESP Flash Download Tools to check connectivity. The boards use CH340 chips.
Has any colleagues encountered a similar problem and managed to solve it?

Check that the virtual com port you have installed does not have an exclamation mark, and that there is not something Code 10 style in the properties. This would mean that windows is downloading drivers that disable fake FTDI or Prolific chips, which are usually found on most development boards from the Chinese.
You should then manually install older drivers.

The port is installed correctly. The problem occurs after several connections of the same board. At first it works OK and then there is no connectivity. When I take another (new) board it also works fine, but until then. It's a good thing I still have an old laptop, so I can use these boards. Just why do I need to keep two laptops on my desk?

I got to the point that under the CH341-3-5-2019 driver (used in W10) everything works OK. But W11 updates this driver automatically to the version intended for it and then the problem comes back. Maybe someone can advise how to block the update of this driver?