On certain AMD-powered Windows laptops, a Canon camera (most commonly the EOS R50, but other Canon mirrorless bodies are affected too) will successfully capture and download the first photo of a session and then fail on every photo after that. The shutter fires, the camera stays connected, but the image never transfers to the computer. After about 30 seconds, LumaBooth for Windows (dslrBooth) shows "Unable to Trigger Camera. Try again."
This is a host-side USB issue on the laptop, not a problem with the camera, the cable, or the software. The simplest and most reliable fix is to connect the camera through an inexpensive USB 2.0 hub instead of plugging it directly into the laptop.
Symptoms
The first photo of the session captures and downloads normally.
From the second photo onward, the shutter fires but the photo never appears in LumaBooth.
After about 30 seconds, you see "Unable to Trigger Camera. Try again."
The camera stays powered on and connected — it is not disconnecting.
Restarting the camera or the app allows exactly one more photo before the same thing happens again.
The same camera and cable work normally on a different computer.
Affected hardware
This has been confirmed on recent AMD Ryzen laptops, including the Lenovo IdeaPad 5 2-in-1 14AKP10 (AMD Ryzen AI 7 / Ryzen AI 9 platform). Any newer AMD ultraportable laptop should be considered a likely candidate when you see the symptom pattern above. Desktop PCs and Intel-based laptops are not known to be affected.
The fix: use a USB 2.0 hub
Connect the camera through a USB 2.0 hub between the camera and the laptop:
Camera → USB cable → USB 2.0 hub → laptop USB port
Any inexpensive USB 2.0 hub will work — it does not need to be powered, and it does not need to be USB 3.0. In fact, a plain USB 2.0 hub is what reliably resolves the issue. After adding the hub, multi-session captures work indefinitely without any other change.
What does not fix it
If you are troubleshooting this symptom, the following steps have all been tested and do not resolve it on the affected hardware. You can skip them:
Replacing the USB cable with a known-good short cable.
Resetting the camera firmware or restoring the camera to default settings.
Updating the laptop BIOS to the latest version.
Installing all current Windows updates.
Disabling USB selective suspend in Windows power options.
Reinstalling or updating LumaBooth for Windows (dslrBooth).
All of these are still worth doing as general good practice for a photo booth setup, but they will not resolve this specific symptom on AMD laptops on their own.
Why a USB 2.0 hub works
On the affected AMD laptops, the USB host controller drops the data transfer between consecutive photo captures. The camera and the software are both healthy — only the link between them fails. A USB 2.0 hub inserts a small piece of hardware (a "transaction translator") between the camera and the laptop, which masks the issue and allows photos to transfer normally for the rest of the session.
Still having trouble?
If adding a USB 2.0 hub does not resolve the issue, the cause is most likely something else. See Camera not connecting or disconnects for a broader troubleshooting checklist, or contact support with your logs attached.