>Communication issue with com

Hardware Checks

:check_mark: Tested three different Arduino boards on multiple PCs → Sometimes detected, sometimes not. :check_mark: Changed USB cables → Verified if the issue was cable-related. :check_mark: Tried different USB ports → Avoided USB hubs, tested direct connections. :check_mark: Reset the bootloader → Pressed the reset button twice quickly. :check_mark: Checked soldering and connections → Verified the quality of the board assembly.

Software Checks

:check_mark: Checked Device Manager in Windows → Sometimes Arduino appeared under "Ports (COM & LPT)", sometimes it didn’t. :check_mark: Reinstalled drivers → Tested CH340 driver for clone boards. :check_mark: Selected the correct COM port in Arduino IDE → Ensured correct settings for communication. :check_mark: Temporarily disabled antivirus → Excluded Arduino IDE to prevent interference. :check_mark: Reinstalled the Arduino IDE → Clean installation of the latest version. :check_mark: Tried an older version of the IDE → Searched for more stable versions (2.3.5). :check_mark: Checked baud rate settings → Made sure Serial.begin(9600); matched the serial monitor.

Attempts with Bluetooth and BLE

:check_mark: Installed BLE library → To test wireless communication on Nano 33 IoT. :check_mark: Fixed coding errors → Replaced BLE.println() with setValue() to send data correctly. :check_mark: Tested with the Serial Bluetooth Terminal app → Checked if data was transmitted properly.

It might help if you told us which boards and if they are clones or originals. It would also help if you enable verbose output during upload, disable verbose output during compilation and post the result of an upload here (using code tags please).

So it works on some PCs with some boards and not on other PCs with the same boards? And the boards that don't work on the first PC work might work or might not work on the second PC?

Which operating systems are involved; Windows was mentioned, which versions. Any other OS?

What does that mean?

This is maybe a candidate for what can go wrong on a windows PC with regard to connecting via USB.

Thinks also go wrong on Linux or Mac.

Most things in post#1 are never needed.
Trying to fix things without knowing what's causing it is a good way to get into more trouble.

We like to check that (pictures). Are you using rosin-cored (electronics) solder, without added flux? Adding (the wrong) flux could also cause these problems.
Leo..

But windows device manager is orders of magnitude more troublesome than at least Mac's are, I am unsure about Linux, but since Macs are BSD Unix I would expect Linux to be more like a Mac than a Windows box.
I had dozens of Windows boxes and almost every OS on them, and spent a lot of time fighting the device manager.

I have troubles with Mac and Linux. I guess it's all about what you're used to.
I have clipped the wings of my Win11Pro setup as much as possible
I hate a second machine I have that uses win11Home. Too much "fun" stuff causing problems.
Leo..

I have no problems with Macs since I switched from win in 2016. I recently bought a $300CDN Win mini pc for the very rare win software I need. Parallels is nice but costs every year. I of course have a couple of different Linux boxes and a Pi or two but I almost never use the Pi's for any Arduino work.
Having worked in support roles off and on over 50+ years I learned a long time ago some people just naturally have trouble mostly because they are curious, bold, maybe careless while others never touch a setting. I suspect that explains why some have trouble with X and others with Y.
I still dont recall seeing a question in the OP's fancy post, maybe I missed it.

Exactly. People always want more.
The first thing I did when I saw Copilot appear after an update is delete/uninstall it.
Along with a dozen other useless apps.
Leo..