Why won't DEXIS or Carestream imaging load?
Imaging that will not load is almost always one of three things: the sensor is not being detected (a USB, driver, or power issue), the bridge between your practice software and the imaging application has broken (a TWAIN or integration problem), or the imaging software's own service or driver is not running. The fastest way to split these apart is to ask one question first: does Windows even see the sensor?
First: does Windows see the sensor at all?
Open Device Manager and look for the sensor. If it appears (DEXIS, Carestream/CS, or the sensor's USB device by its vendor/product ID), the hardware is fine and the problem is software or the bridge. If it shows as an "Unknown device," has a warning icon, or is missing entirely, the problem is USB, the driver, or the cable - a hardware-layer issue. That one check decides which half of this list to work.
The common causes of imaging not loading
1. USB connection, port, or hub
Intraoral sensors are USB devices, and they are sensitive to the port. Plug the sensor directly into the computer rather than through a hub or a monitor's USB pass-through, try a different port, and reseat the cable. A surprising share of "sensor not detected" calls resolve at this step.
2. A missing or broken sensor driver
If Device Manager shows the sensor as an Unknown device or with a warning, the driver is missing or corrupt - common after a Windows update or a workstation reimage. Reinstall the vendor's current driver. A dental-fluent technician will recognize the sensor by its USB vendor/product ID (VID/PID) and match the exact driver, rather than guessing.
3. USB selective suspend is powering the sensor down
Windows power management can suspend USB devices to save power, and an intraoral sensor that gets suspended drops off until it is re-enumerated. Disabling USB selective suspend (and the "allow the computer to turn off this device" option on the USB hub) keeps the sensor present and ready.
4. The bridge between your PMS and the imaging software
Imaging usually opens from inside the practice-management software through a bridge or a TWAIN link. If the sensor works in the imaging app directly but not when launched from the PMS, the bridge or TWAIN configuration is the problem, not the sensor. This is the classic "it works over there but not from here" pattern.
5. The imaging software service or driver is not running
DEXIS and Carestream/CS Imaging rely on their own background components. If a service or capture driver did not start - again, common after an update or reboot - the image window opens but never acquires. Restart the service (or the workstation) and confirm the capture component is running.
6. A recent Windows update changed the USB or driver stack
Windows feature updates can replace drivers, reset USB power settings, or change device permissions. If imaging worked yesterday and broke "after an update," check the driver and the USB power settings first - the update likely reverted one of them.
7. Antivirus blocking the imaging service
As with the database engines, antivirus can block or quarantine an imaging component after an update. Confirm the imaging software's folders and services are excluded on the workstation.
The sensor works in one program but not another
When the sensor captures fine in the standalone imaging application but fails when opened from the practice-management software, the fault is the integration/bridge layer, not the sensor or its driver. Reconfiguring or repairing the bridge (or the TWAIN source selection) is the fix - replacing the sensor would change nothing.
What an autonomous RMM does about this
On the CyberCore early-access cohort, the agent tracks imaging endpoints: it notices when an imaging service stops, when a sensor's USB device disappears from the machine, and when a driver or USB power setting changed after an update. The well-understood cases - a stopped imaging service, a power-management setting that dropped the sensor - surface (and, inside the owner-authorized allowlist, can be corrected) quickly, with the device and action logged, instead of an operatory going dark mid-exam. (See Glass-box RMM and What is a Dental RMM?.)