Did you perform the driver rollback procedure I described in the other thread?:
Even if you install the working older version of the driver, Windows will automatically update the driver to the newer version that is incompatible with the bad CH340 chips. This is why you must perform the "roll back driver" procedure to force Windows to persistently use the old version of the driver.
It is difficult to survey because most of the affected users didn't report which version of Windows they are using, but there are definitely some Windows 11 users who have been able to solve the problem by using the older driver version. I found these reports after a quick search:
- https://forum.arduino.cc/t/avrdude-ser-open-cant-set-com-state-for-com7/1118832/13
- https://forum.arduino.cc/t/solution-to-avrdude-error-ser-open-cant-set-com-state-for-com3/1125991/4
- https://forum.arduino.cc/t/avrdude-stk500-getsync-cant-communicate-with-device-resp-0x00/1168515/12
- https://forum.arduino.cc/t/avrdude-ser-open-cant-set-com-state-for-com5/1163466
- https://forum.arduino.cc/t/avrdude-ser-open-cant-set-com-state-for-com3-isuse/1159546
And another even in the forum topic you originally posted in!:
https://forum.arduino.cc/t/windows-11-arduino-ide-version-2-1-1-com-port-problem/1148176
It is true that the symptom reported there is different (opening Serial Monitor fails with a "Port monitor error command ‘open’ failed: Invalid serial port." error instead of upload failing with a "can't set com-state" error), but both symptoms have the same cause and the same workaround.
There is another report of a Windows 11 user solving that symptom with the "roll back" technique here:
https://forum.arduino.cc/t/weird-issues-with-ide-2-2-1/1179568/6
Since you have verified that your board has a CH340 chip, it is a waste of time to try to install the FTDI drivers.
Do all of those boards have CH340 chips?
Does the upload to all of the boards fail with the "can't set com-state" error, or do you get a different error message?