Drivers on Windows
Only the left-hand socket needs one, and the driver is a single download from the chip's maker. Five minutes, once per computer — and if you are on the right-hand socket you can skip this page entirely.
Only one of the two sockets needs anything
The right-hand socket is the ESP32-S3's own USB. Windows has spoken that language since Windows 7 and there is nothing to install, ever. If your cable is in that one and no port appears, a driver is not what is missing — the cable is.
The left-hand socket goes through a CH340K, and that chip needs the driver its maker publishes.
Installing it
- Download CH341SER from WCH, at wch-ic.com/downloads/CH341SER_ZIP.html. It is the official driver from the company that makes the chip; anything else you find is a repackage of it.
- Unplug the board and close the Arduino IDE. Both matter: Windows binds a driver when a device appears, and the IDE holds ports open.
- Right-click the installer and choose Run as administrator. Click Install, wait, close it.
- Plug the board into the left-hand socket.
Checking it worked
Press Windows + X and open Device Manager. Under Ports (COM & LPT)
you should see a new entry — USB-SERIAL CH340 (COM3) or similar. The number
is whatever Windows had spare.
The useful test is not reading the name, though. It is this: watch that list while you unplug the board. The entry that disappears is your board, and the entry that comes back when you plug it in is the one to pick in Tools ▸ Port. That habit is right on every machine, including one you have never seen belonging to someone you are helping over the phone.
If Device Manager shows a warning triangle
A device under Other devices with a yellow triangle is one Windows saw and could not match to a driver. Right-click it, choose Update driver, and point it at the folder the installer left behind — or run the installer again with the board unplugged, which is the same fix and less typing.
A device that does not appear in Device Manager at all is a different problem and this page cannot fix it. Windows did not see anything, which means the data lines never arrived: a charge-only cable, or a socket that is not passing data. The next-but-one article is about exactly that.
When it does not work
Unplug the board and plug it back in — Windows binds drivers at enumeration, so a device that was already attached when the installer ran keeps the driver it had. If it still does not appear, look in Device Manager for a yellow warning triangle under "Other devices"; a device sitting there is one Windows could not match.
Then Windows never saw a device, and no driver would have helped. That is a cable or a socket, not a driver — try a cable you have moved a file with, and try the other USB socket on the board.
It belongs to the driver, not to the board, so a different USB socket on your computer gives a different number. Never memorise it. Open Tools ▸ Port with the board unplugged, plug it in, and take the entry that appeared.
Something else has the port open. The Serial Monitor in another IDE window is the usual culprit; so is a terminal you left running. Close them and upload again.
The IDE, the board package, and the eight settings that make the memory on this board visible.
Arduino IDE, set up for N16R8 →Edit this page — content/boards/esp32-s3/drivers-on-windows.mdx
Questions about this product
See what other owners have asked, and read their solutions.
ESP32-S3 Gold Edition (N16R8)
Loading discussions…
Discuss this article
Ask about this page. The answer stays here, on the page it belongs to, for whoever hits the same wall next.