SCSI Scanner Device has a Driver Problem: How to Fix

The Device Manager (devmgmt.msc) in Windows is the best place to check if a device such as printer, scanner, mouse, keyboard, DVD-ROM, network adapters and etc is installed and working properly. A device that is not working will show a yellow exclamation mark on the icon itself with the tree automatically expanded. You can find more information on the error by double clicking on the device to bring up the properties window. Here is an example of a common error message “Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)“.

Windows cannot start this hardware device because its configuration information in the registry is incomplete or damaged code 19

If you are getting the same code 19 error for your imaging devices such as scanner or even a multifunctional all-in-one printer, the good news is the device is not faulty and can be easily fixed by following the simple instructions below.

This code 19 error can appear on both wired and wireless connected scanner or multifunction all-in-one printer.

Check for code 19 error in imaging devices

1. The first thing that you need to do is to confirm that your scanner is detected and listed in device manager. Press WIN+R to bring up the Run window.

2. Type devmgmt.msc and click OK.

devmgmt.msc

3. The Device Manager should now run, check for yellow exclamation mark on the device listed under Imaging devices.

device manager exclamation mark

4. If your scanner is detected and has a yellow exclamation mark like the screenshot above, double click or right click and select Properties on the device.

5. Go to the Details tab and select “Class lower filters” from the Property drop down menu. If you see a value such as lvmvdrv, it would mean that you’ve previously installed and uninstalled a Logitech webcam and the uninstaller did a bad job in leaving a redundant entry in registry.

class lower filters

Before deleting the bad registry entry that is causing the code 19 error, it is best to make a backup first.

Backup registry

6. Press WIN+R, type regedit and click OK.

7. Navigate to the following registry path:

HKLM\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}

8. Right click on the registry folder at the left pane, select Export and save the registry file to your hard drive.

backup registry

Delete corrupted LowerFilters

9. At the same registry path, look for LowerFilters at the right pane, right click and select Delete. Click Yes to confirm deleting the LowerFilters registry value.

delete lowerfilters

Alternatively, you can download and run this registry file which will automatically clear out the LowerFilters reg value. If you’re experiencing additional problems after deleting the LowerFilters value in the registry, simply double click on the .reg file that you’ve exported from step 6-8 to restore back the changes.

Additional Notes: A redundant LowerFilters registry value that isn’t removed after uninstalling the software that puts it there in the first place can cause the hardware device not to function. Since this is a registry problem, we’ve tried using 10 well known registry cleaning software such as Auslogics Registry Cleaner, CCleaner, Glary Utilities, IObit Advanced SystemCare, iolo System Mechanic, jv16 PowerTools, Norton Utilities, TuneUp Utilities, TweakNow RegCleaner, and Wise Registry Cleaner but surprisingly none of them managed to detect and fix the bad lowerfilters registry key problem.

92 Comments - Write a Comment

  1. Leza 2 years ago
  2. Brenda 2 years ago
  3. Denis 3 years ago
  4. David 4 years ago
  5. John 5 years ago
  6. Kevin 5 years ago
  7. Watson 5 years ago
  8. CK 5 years ago
    • HAL9000 5 years ago
  9. FB 5 years ago
  10. ohdudeusa 5 years ago
  11. Chris 6 years ago
  12. Rob Pattison 7 years ago
  13. Logen 7 years ago
  14. ming 8 years ago
  15. John 8 years ago
  16. Mikko 8 years ago
  17. Stou 8 years ago
  18. coffent 8 years ago
  19. Joe 8 years ago
  20. Alexa 9 years ago
  21. Mindbank PC 9 years ago
  22. mike 9 years ago
  23. Jackie 9 years ago
  24. Ayn 9 years ago
  25. Ganesh 9 years ago
  26. rasmy 10 years ago
  27. Simon Dalby 11 years ago
  28. viksen 11 years ago
  29. Steve Pollock 12 years ago
  30. Billie 12 years ago
  31. John 12 years ago
  32. Nicolaspapiachvili 12 years ago
  33. Dirkhines 12 years ago
  34. KR 13 years ago
  35. bh 13 years ago
  36. JP 14 years ago
  37. italo 14 years ago
  38. Roger Scien 14 years ago
  39. Kamila 14 years ago
  40. Vikrant 14 years ago
  41. Suvi 14 years ago
  42. Ken 14 years ago
  43. henry 14 years ago
  44. catherine 14 years ago
  45. Gwion 14 years ago
  46. mikelinpa 14 years ago
  47. George 15 years ago
  48. Rae 15 years ago
  49. Dan 15 years ago
  50. Wowzers 15 years ago
  51. David Beneke 15 years ago
  52. Dean 15 years ago
  53. loclhero 15 years ago
  54. Johnson 15 years ago
  55. Mike 15 years ago
  56. Sirius 15 years ago
  57. GaltKid 15 years ago
  58. Prash 15 years ago
  59. Bob Pratt 15 years ago
  60. vince 15 years ago
  61. kiel 15 years ago
  62. Richard 15 years ago
  63. John 15 years ago
  64. balls 15 years ago
  65. Mark Yuri Stephens 15 years ago
  66. Uwe G. 15 years ago
  67. Abdo 15 years ago
  68. Sue 15 years ago
  69. Alex Martins 15 years ago
  70. Paul 16 years ago
  71. Russ 16 years ago
  72. Bill 16 years ago
  73. Lancy 16 years ago
  74. rusty fetterov 16 years ago
  75. Karsten 16 years ago
  76. Harry 16 years ago
  77. Pat 16 years ago
  78. Jason B 16 years ago
  79. Mister Jerk 16 years ago
  80. Shawn 16 years ago
  81. Christine 16 years ago
  82. Yuri 16 years ago
  83. Dave 16 years ago
  84. Eran 16 years ago
  85. Jennifer 16 years ago
  86. Hasso Krampen 16 years ago
  87. Martin Ross 16 years ago
  88. Suzette 16 years ago
  89. Mike S 16 years ago
  90. Uncle Gunk 16 years ago
  91. chunky 16 years ago

Leave a Reply

Your email address will not be published. Required fields are marked *

Note: Your comment is subject to approval. Read our Terms of Use. If you are seeking additional information on this article, please contact us directly.