I’m trying to modify the device name and serial number of a batch of B0203 cameras on Windows 10. When I run the Arducam UVC Serial Number Editor I keep hitting an error that just says “Unknown device”.
The weird part is the camera connects fine first and shows up in Device Manager as “USB Camera”. From the docs the B0203 should be listed as a supported UVC camera for serial number modification, so I’m not sure what I’m missing.
Hi, thanks for the detailed report and the screenshots.
I see what you’re describing - you’re trying to modify the device name and serial number of multiple B0203 cameras on Windows 10, the camera connects first and appears in Device Manager as “USB Camera”, and the editor throws “Unknown device”. The B0203 should indeed be in the supported UVC list for serial number modification.
Let me run a test on our side with the Arducam UVC Serial Number Editor against a B0203 on Windows 10 to reproduce this before I point you at anything.
In the meantime, a couple of quick questions so I can narrow it down:
Which version of the serial number editor are you running?
Does the tool detect any camera at all, or does it show “Unknown device” right away?
Any warning/yellow mark on the “USB Camera” entry in Device Manager?
Are you launching the editor as administrator, and is only one camera plugged in at a time when you try?
Please confirm and I’ll compare with my test results.
I ran a couple more checks and noticed something interesting. If I open the editor while the B0203 is NOT connected, I get a different message: “Can’t find video device!”. But as soon as the camera IS connected, it goes back to “Unknown device”.
Environment is the same:
Windows 10
multiple B0203 cameras
camera shows up in Device Manager as “USB Camera”
B0203 is listed as a supported UVC camera for serial number modification per the doc: Redirecting...
“Can’t find video device!” = the editor can’t find any UVC video device at all, which makes sense with nothing plugged in.
“Unknown device” = the editor found a video device but couldn’t read/recognize the identifier it needs (the serial/device info it uses to talk to the camera). So it’s seeing something, just not the B0203 the way it expects.
Now that it’s connected, can you check a few things:
In Device Manager, right-click the “USB Camera” entry > Properties > Details tab > select “Device instance path” and paste the value here.
Does the same “Unknown device” happen if you unplug every other camera and leave only ONE B0203 connected?
Try a different USB port (ideally a direct rear port, not a hub) and try launching the editor as administrator.
Does the camera open normally as a webcam (e.g. in the Windows Camera app) while this is happening?
That will help me tell whether it’s a driver/enumeration issue on your machine or something on the tool’s side. I’m still running my own test as well.
Device instance path looks like it enumerates under the standard USB camera class - I’ve included it in the screenshot set above, it doesn’t show a B0203-specific name, just the generic “USB Camera”.
Same “Unknown device” with only a single B0203 connected, no other cameras.
Tried a different USB port directly on the motherboard and ran the editor as admin - same result. No yellow warning marks in Device Manager.
Yes, the camera opens fine as a webcam in the Camera app, so the video itself works.
So video works, but the serial number editor still says “Unknown device” whenever it’s plugged in, and “Can’t find video device!” when it’s not. Still stuck.
Thanks, that rules out a few things. Summary of where we are:
The editor behaves consistently: “Can’t find video device!” with nothing connected, “Unknown device” with the B0203 connected.
Video capture works (camera opens in the Camera app), so the basic UVC connection is alive.
No driver warning in Device Manager, and it still fails on a single camera, different port, and as admin.
Your camera shows up as the generic “USB Camera”, which is expected here, but the editor still isn’t recognizing it as a modifiable B0203.
So this looks like the editor isn’t detecting/identifying the B0203 correctly on your Windows 10 setup rather than a cabling or webcam problem. I don’t have a confirmed fix or workaround for this yet - I’m still testing against a B0203 on Windows 10 on my end to reproduce the exact “Unknown device” state.
I’ll reply here as soon as I have results from that test. If it turns out to be a limitation or a specific condition, I’ll tell you what we find rather than guess. Thanks for your patience so far.
