Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Couldn't initialize the scanner

See original GitHub issue

Etcher version: 1.1.1
Operating system and architecture: Windows 10 x64
Image flashed: none, not working
Do you see any meaningful error information in the DevTools? How do I do that on Windows

Issue Analytics

State:
Created 6 years ago
Comments:8 (5 by maintainers)

Top GitHub Comments

1reaction

mikaeljonssonhbgcommented, Aug 5, 2017

Hi,

Had the same issue and snapshot build from jviotti with fix above solved it for me! Thankxxx!

Running Windows 10 Home, build 10586

1reaction

jviotticommented, Aug 3, 2017

Can you try the following snapshot build that contains the fix: https://drive.google.com/file/d/0B7tkbonGU-RyTUNKaVpLb2VCZ1E/view?usp=sharing? If that still doesn’t work, can you set the DRIVELIST_DEBUG environment variable and execute the application from cmd.exe, so you can see the debug logs?

For example:

set DRIVELIST_DEBUG=1
cd C:\Program Files\Etcher
etcher.exe

Top Results From Across the Web

Couldn't initialize the scanner: An unknown error occurred ...

I am setting up a new instance of my nodejs app (today) and was receiving some strange errors with the drivelist module when...

4.7. Error: Unable to Initialize Scanner

Issue Summary: You receive the error message "Unable to Initialize Scanner" when attempting to scan in Kurzweil 3000 (K3000).

Tech Support Tip: TWAIN Error - Fortra

Try rebooting the scanner, or unplug the scanner from the workstation and plug it back in. Open the TWAIN driver you installed with...

HP Print and Scan Doctor for Windows

Download the free Official HP Print Scan Doctor software to automatically fix scanner issues, ... Scanner Unreachable; The scanner could not be initialized....

Couldn't initialize the plugin scheduler

Find the NVT in the scan config and disable it. This is a special case, and it should not have happened. Regards.