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.

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.

88 Comments - Write a Comment

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