USB Detect & Launch: Automate App Startup When a USB Device Connects

USB Detect & Launch: Automate App Startup When a USB Device Connects

What it does

• Detects when a USB device (flash drive, external HDD, phone in USB mass-storage mode, or other USB peripheral) is connected to your computer and automatically launches a specified application, script, or command.

Common uses

• Auto-open a file manager or backup tool when a drive is plugged in.
• Run a sync or backup script to copy new files from the USB device.
• Launch a media player when a USB containing music or video is connected.
• Trigger security scans or antivirus checks on newly attached drives.
• Start device-specific utilities (e.g., phone sync, camera import).

How it works (typical approaches)

• OS event hooks: The operating system emits events when USB devices connect; a background service or daemon listens for these events and triggers configured actions.
• Device-identification: Actions are usually tied to device attributes (vendor/product ID, serial number, or filesystem label) to avoid running on every USB connection.
• Rules and filters: Configurations often let you limit triggers by path, filesystem type, device ID, or user account.
• Safe execution: Good implementations run actions with appropriate permissions and sandboxing to prevent executing malicious autorun content.

Platform specifics

• Windows: Uses device arrival events (WM_DEVICECHANGE), Task Scheduler triggers, or third-party utilities. Modern Windows blocks legacy autorun for security, so explicit detector apps or scheduled tasks are used.
• macOS: Uses I/O Kit or launchd daemons, or filesystem monitoring (FSEvents) to detect mounts.
• Linux: Uses udev rules, systemd path/unit triggers, or dbus/udisks/udev-based daemons; scripts can be triggered on mount events.

Basic setup steps (generic)

1. Install or enable a background watcher/daemon for USB or mount events.
2. Specify the target action: executable, script, or command line.
3. Add filters: device IDs, volume label, mount path, filesystem type.
4. Test with the intended USB device and verify logs/output.
5. Add safeguards: confirm user approval, run in sandbox, or require a specific token file to reduce risk.

Security considerations

• Never auto-run untrusted executables from removable media. Restrict triggers to trusted device IDs or require a signed script.
• Scan drives before executing actions.
• Run actions with the least privilege necessary.
• Log events and failures for auditing.

Troubleshooting tips

• If trigger doesn’t run, check system event logs and watcher/daemon logs.
• Verify device identification values (VID/PID/serial) match your rule.
• Ensure the watcher has necessary permissions to execute the action.
• Test with simple commands (e.g., write a timestamp to a file) to confirm detection works.

Example simple use cases

• Backup: On mount of backup-drive with label BACKUP, run a sync script to copy specified folders.
• Media: When a drive labeled MUSIC is connected, launch your music player pointing at that mount.
• Import: When a camera memory card mounts, run an image-importer script and then eject.