Why does my S100 scanner say "check if sensor is connected" when I try to scan?

⚠️ The Styku S100 with Kinect camera is end-of-life. This article is preserved for existing S100 customers troubleshooting their current scanner. Styku no longer provides setup support for the S100, and new S100 deployments are not supported. To discuss upgrading to a current Styku scanner (X2L), submit a request through the Styku Business Portal at styku.com/portal — a sales representative will be assigned and reach out to you.

If your S100 scanner displays a "check if sensor is connected" message, the Styku software cannot communicate with the Kinect camera tower. This is usually caused by a loose cable, a USB port issue, a driver conflict, or antivirus software blocking the connection. Work through the steps below in order before contacting support.

Step 1: Check Your Cables and Power

Confirm the USB cable from the camera tower is firmly plugged into the computer.
Unplug the cable, wait 10 seconds, and plug it back in.
Try a different USB port on the computer.
Make sure the camera tower's power adapter is plugged into a working wall outlet.

Note on USB extension cables: If you are using a USB extension cable between the sensor tower and the computer, be aware that off-the-shelf extension cables can cause performance issues and unstable connections. Styku does not recommend using any extension cable other than the approved extension cable. The Styku-tested option is the Newnex FireNex active USB 3.1 extension cable, which works with both the S100 and S100X sensor towers. This cable can extend the distance between the sensor tower and the computer from 2.1 meters to 7.1 meters (about 23 feet). If you are using an unapproved extension cable, try connecting the sensor tower directly to the computer before continuing.

Step 2: Restart Everything

Close Styku Studio completely.
Unplug the USB cable from the camera tower.
Shut down the computer fully (do not just restart).
Power the computer back on.
Once Windows has fully loaded, plug the camera tower USB cable back in.
Open Styku Studio and attempt a scan.

Step 3: Check for Antivirus or Security Software Conflicts

Security software can block the Kinect sensor from communicating with Styku Studio.

Check whether antivirus software (such as AVG, Norton, or similar) is installed on the computer.
Temporarily disable it.
Attempt a scan again.

If the scan works with antivirus disabled, add Styku Studio as an exception in your antivirus settings, or contact your IT provider for help doing so.

Step 4: Disable Windows Audio Enhancements

In some cases, Windows audio settings interfere with sensor performance.

Open Settings → System → Sound.
Select your Microphone Array device.
Scroll down to Audio Enhancements.
Change the setting from Device Default Effects to Off.
Attempt a scan again.

Step 5: Run the Kinect Configuration Verifier

The Kinect Configuration Verifier is a diagnostic tool that confirms whether Windows can see and communicate with the Kinect sensor. It is usually located in your Downloads folder.

Open the Kinect Configuration Verifier from your Downloads folder (or download it from the Microsoft Kinect SDK page if you do not have it).
Wait for it to connect and display the sensor streams.
Check the frame rate shown for the Color and Depth streams. The sensor should run at 24 frames per second (FPS) or higher. A reading below 24 FPS means the sensor is running but underperforming, which causes degraded scans even if no red cross appears.
If the verifier shows a red cross next to the sensor, the sensor is not being recognized — continue to Step 6.
If the verifier shows a low FPS reading (below 24), try the following before continuing:
- Enable the Kinect microphone in Windows Privacy settings: Go to Settings → Privacy → Microphone, and make sure microphone access is turned On for apps. Restart Styku Studio and re-check FPS.
- Disable antivirus software temporarily: Antivirus tools (AVG, Norton, etc.) can throttle the Kinect USB data stream. Temporarily disable antivirus, re-run the verifier, and if FPS recovers, add Styku Studio as a permanent exception.
If the verifier shows a normal FPS (24+) and no red cross, open Styku Studio and attempt a scan.

Step 6: Reinstall the Kinect Drivers

Open Device Manager (search for it in the Windows Start menu).
Locate the Kinect sensor in the device list.
Right-click it and select Uninstall device. Also uninstall any associated USB drivers if prompted.
Unplug the camera tower USB cable.
Restart the computer.
After Windows reloads, plug the camera tower USB cable back in.
Reinstall the Kinect drivers. Your support agent can provide the correct driver package if needed.
Open Device Manager again and confirm the Kinect sensor appears without any warning icons.
Run the Kinect Configuration Verifier again to check the result.

If the Problem Persists

If the Kinect Configuration Verifier still shows a red cross after completing all steps above, the camera tower itself may have a hardware fault that cannot be resolved through software or driver fixes. Contact Styku Support to discuss next steps, which may include a hardware replacement.

If this resolves your issue, no further action is needed.

If the problem persists, contact support and include: your business location name or license key, a description of which steps you completed and the results of each, a screenshot of the Kinect Configuration Verifier showing the error, and any error messages displayed in Styku Studio.

Applies to: Styku S100 scanner with Kinect v2 sensor, Styku Studio all versions.

Related Resources

Can I use USB extension cables with my Styku scanner?

Why does my S100 scanner say \"check if sensor is connected\" when I try to scan?