How To Fix Unable to Install Scanner or Imaging Devices Due to Registry Incomplete or Damage Code 19

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.


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:


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.

90 Comments - Write a Comment

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

Leave a Reply

Your email address will not be published.

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.